maxwellokumu/okaudit-claude-skills / data-privacy/pia-generator
pia-generator
VerifiedGenerate structured privacy impact assessments so Claude can organize project privacy risks, controls, and decision points into a review-ready report.
PIA Generator
Use this skill when the user needs a Privacy Impact Assessment or DPIA-style document for a project, system, or processing activity.
Goal
Help Claude turn project details into a structured privacy assessment that captures processing context, risks, mitigation considerations, and governance details.
Workflow
- Confirm the project name, processed data types, purposes, recipients, retention, and any optional governance details.
- Review the inputs for privacy risk indicators such as sensitive data, broad sharing, or unclear necessity.
- Organize the assessment into a coherent privacy narrative with practical risk observations.
- Highlight areas that may require stronger controls, legal review, or additional safeguards.
- Present a clear PIA or DPIA-style output that is ready for stakeholder review.
Inputs
Expected inputs from the bundled tool metadata:
- project: Name of the project or system.
- data-types: Comma-separated list of processed data types.
- purposes: Comma-separated list of processing purposes.
- recipients: Comma-separated list of data recipients.
- retention: Data retention period.
- controller: Optional data controller name.
- dpo: Optional DPO name or email.
- framework: Optional framework such as gdpr or iso27701.
Bundled Files
- main.py contains the executable PIA generation logic.
- README.md provides examples and usage notes.
- skill.yaml captures the repo-native metadata for this skill.
- sample_input may contain example project inputs.
Guidance
Keep the assessment structured and professional. Be explicit about risk factors, data sensitivity, and where additional review or safeguards may be needed.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |