ThomasMoreAI/legal-skills-open / au/data-protection/skills/assess-statutory-privacy-tort-l0cka
assess-statutory-privacy-tort-l0cka
VerifiedScreen facts and AI-system use cases against the legislation-only statutory tort for serious invasions of privacy in Schedule 2 to the Privacy Act 1988 (Cth), including scope, elements, public-interest balancing, defences, exemptions, remedies and limitation issues. Use for surveillance, recording, scraping, profiling, inference, deepfakes, publication, disclosure or handling of intimate, location, health or financial information. Do not use case law or treat APP-entity coverage as a prerequisite.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 3.6 KB |
| agents/openai.yaml | config | 286 B |
| references/statutory-tort-method.md | markdown | 1.4 KB |
SKILL.md
View on GitHub---
name: assess-statutory-privacy-tort-l0cka
title: Assess Statutory Privacy Tort
description: Screen facts and AI-system use cases against the legislation-only statutory tort for serious invasions of privacy in Schedule 2 to the Privacy Act 1988 (Cth), including scope, elements, public-interest balancing, defences, exemptions, remedies and limitation issues. Use for surveillance, recording, scraping, profiling, inference, deepfakes, publication, disclosure or handling of intimate, location, health or financial information. Do not use case law or treat APP-entity coverage as a prerequisite.
author: l0cka
author_url: https://github.com/l0cka/legal-skills/tree/main/plugins/australian-privacy-cybersecurity/skills/assess-statutory-privacy-tort
license: MIT
version: 0.1.0
execution_mode: open
jurisdiction: au
practice: data-protection
language: en
sources:
- title: Statutory Tort Method
path: references/statutory-tort-method.md
---
# Assess Statutory Privacy Tort
Conduct a legislation-only screen under Privacy Act Schedule 2. Read
[references/statutory-tort-method.md](references/statutory-tort-method.md) before
starting.
## Workflow
1. Record the conduct date, actor, affected person, information, place,
technology, purpose, audience, intent or recklessness facts, seriousness and
alleged harm. Separate evidence, allegations, inferences and unknowns.
2. Invoke `$check-commonwealth-legislation` for Privacy Act section 94A and
Schedule 2 at the relevant date. If the conduct or claim horizon crosses a
change, invoke `$trace-commonwealth-legislative-change`.
3. Assess the statutory pathways separately: intrusion upon seclusion, misuse
of information, or both. Test every statutory element without importing
case-derived gloss.
4. Test the statutory public-interest balance, defences, exemptions, remedies
and limitation provisions against verified text. State which party bears
each statutory burden only where the text was checked.
5. Keep the tort screen independent from APP coverage. An actor can be outside
the APP regime or within an APP exemption while Schedule 2 still requires
analysis.
## Result contract
Lead with `STATUTORY PRIVACY TORT SCREEN — HUMAN REVIEW REQUIRED`:
```text
Conduct and date: <bounded facts>
APP coverage: <separate and not determinative>
Pathway | Statutory element | Facts for | Facts against | Unknown |
Verified provision | Preliminary status
Public-interest balance: <privacy interest and countervailing interests>
Defences and exemptions: <candidate only unless verified and fact-supported>
Remedies and limitation: <issues and dates requiring lawyer decision>
Evidence required: <shortest path>
```
Use `POTENTIALLY ENGAGED`, `NOT ESTABLISHED ON CURRENT FACTS` or `INSUFFICIENT
INFORMATION`, not a final liability conclusion. State that case law was outside
scope and not considered.
<!-- generated:plugin-dependencies -->
## Other plugins
This skill names skills from other Legal Skills plugins. Install a required
plugin alongside this one; install a hand-off plugin when the matter needs
that depth.
- `australian-legal-research` (required): `check-commonwealth-legislation`,
`trace-commonwealth-legislative-change`. Verifies the Commonwealth, state
and territory legislation the privacy, breach and cyber workflows rely on.
If a named skill is not available in this session, say so and name the plugin
to install. Treat the step it would have performed as not done: record the
affected proposition as not verified, or the hand-off as not made. Never
perform that step from memory or substitute a different skill.
<!-- end:plugin-dependencies -->
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |