Skip to content

maxwellokumu/okaudit-claude-skills / data-privacy/pia-generator

pia-generator

Verified

Generate structured privacy impact assessments so Claude can organize project privacy risks, controls, and decision points into a review-ready report.

FileKindSize
README.mdmarkdown2.2 KB
SKILL.mdskill md1.8 KB
main.pyscript24.9 KB
skill.yamlconfig1.6 KB
# pia-generator

Generates a fully structured Privacy Impact Assessment (PIA / DPIA) in markdown from command-line parameters. Maps data types to risk levels, selects applicable risks from a 10-item library, and produces an 8-section document including data flows, legal basis assessment, risk scoring, data subject rights checklist, DPO recommendations, and a sign-off block.

## Requirements

```
python-dotenv
```

## Usage

### Basic GDPR PIA
```bash
python main.py \
  --project "Employee Health Portal" \
  --data-types "health,contact_details,employee_records" \
  --purposes "occupational health management,legal compliance" \
  --recipients "HR department,Occupational Health Provider,HMRC" \
  --retention "7 years" \
  --controller "Acme Solutions Ltd" \
  --dpo "dpo@acmesolutions.com"
```

### ISO 27701 assessment
```bash
python main.py \
  --project "Customer Analytics Platform" \
  --data-types "behavioral,contact,location" \
  --purposes "analytics,marketing,profiling" \
  --recipients "Marketing team,Analytics Provider" \
  --retention "2 years" \
  --framework iso27701
```

## Data Type Risk Levels

| Level | Examples |
|-------|---------|
| Very High | health, biometric, criminal_record, genetic, children_data |
| High | financial, location, behavioral, profiling |
| Medium | contact, email, employee, identifier |
| Low | public, aggregated, anonymised |

## PIA Sections Generated

1. PIA Header (project metadata, controller, DPO)
2. Project Overview
3. Data Flows (table per data type × purpose × recipient)
4. Legal Basis Assessment (per purpose)
5. Risk Assessment (10-item risk library, scored and mitigated)
6. Data Subject Rights Compliance Checklist
7. DPO Recommendations
8. Sign-off Block

## Sample Output

```markdown
# Privacy Impact Assessment
## Employee Health Portal

## 1. PIA Header

| Field | Value |
|-------|-------|
| Project / System Name | Employee Health Portal |
| Overall Risk Level | **Very High** |
...

## 5. Risk Assessment

| Risk ID | Risk | Likelihood | Impact | Risk Score |
|---------|------|------------|--------|------------|
| PR-01 | Unauthorised Access | Medium | High | **High** |
| PR-02 | Data Breach | Low | Very High | **High** |
```
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 implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall