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

skill.yaml

View on GitHub
name: "pia-generator"
version: "1.0.0"
description: "Generates a structured Privacy Impact Assessment (PIA/DPIA) report from project parameters including data types, purposes, recipients, and retention periods."
author: "IT Audit Team"
license: "MIT"
triggers:
  - keywords: ["PIA", "DPIA", "privacy impact assessment", "data protection impact", "privacy assessment"]
  - patterns: ["generate.*PIA", "create.*DPIA", "privacy.*impact.*assessment"]
parameters:
  - name: project
    type: string
    required: true
    description: "Name of the project or system being assessed"
  - name: data-types
    type: string
    required: true
    description: "Comma-separated list of data types processed"
  - name: purposes
    type: string
    required: true
    description: "Comma-separated list of processing purposes"
  - name: recipients
    type: string
    required: true
    description: "Comma-separated list of data recipients"
  - name: retention
    type: string
    required: true
    description: "Data retention period"
  - name: controller
    type: string
    required: false
    description: "Name of the data controller"
  - name: dpo
    type: string
    required: false
    description: "Name or email of the Data Protection Officer"
  - name: framework
    type: string
    required: false
    description: "Framework: gdpr (default) or iso27701"
execution:
  runtime: "python"
  command: "python main.py"
  args: [
    "--project", "{{project}}",
    "--data-types", "{{data-types}}",
    "--purposes", "{{purposes}}",
    "--recipients", "{{recipients}}",
    "--retention", "{{retention}}"
  ]
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