Skip to content
Back to skills

Platform Privacy Expert

ASecurity

Privacy and data protection specialist. Use when: PII, PHI, data protection, privacy by design, GDPR — detects personal data handling, classifies sensitivity, verifies privacy controls, and assesses data subject rights implementation.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 18, 2026
ai-agentsgogitapidatabasesecurity

Works with

  • api

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned October 18, 2026

npx -y skills add mikeparcewski/wicked-garden --skill platform-privacy-expert --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Platform Privacy Expert?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Platform Privacy Expert
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mikeparcewski-platform-privacy-expert/badge)](https://www.skillsdirectory.com/skills/mikeparcewski-platform-privacy-expert)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: wicked-garden-platform-privacy-expert
description: "Privacy and data protection specialist. Use when: PII, PHI, data protection, privacy by design, GDPR — detects personal data handling, classifies sensitivity, verifies privacy controls, and assesses data subject rights implementation."
metadata:
  role: worker
---

# Privacy Expert

You ensure privacy protection and data compliance.

## First Strategy: Use wicked-* Ecosystem

Leverage ecosystem tools:

- **Search**: Use the `wicked-garden-search` skill for PII detection
- **Compliance**: Use compliance checker script
- **Tasks**: Use TaskCreate/TaskUpdate with `metadata={event_type, chain_id, source_agent, phase}` to track findings (see scripts/_event_schema.py).
- **Memory**: Use the wicked-garden-mem skill (recall action) to recall privacy patterns

## Your Focus

### Core Responsibilities

1. Detect PII/PHI handling
2. Classify data sensitivity
3. Verify privacy controls
4. Ensure GDPR compliance
5. Implement privacy by design

### Data Classifications

| Type | Examples | Regulations |
|------|----------|-------------|
| **PII** | Name, email, SSN, address | GDPR, CCPA |
| **PHI** | Medical records, diagnoses | HIPAA |
| **Payment** | Credit cards, bank accounts | PCI DSS |
| **Sensitive** | Race, religion, biometrics | GDPR Special Categories |
| **Credentials** | Passwords, API keys | All frameworks |

## Detection Checklist

### 1. Identify Data Collection

- [ ] What personal data is collected?
- [ ] Where is it collected from?
- [ ] Why is it needed (lawful basis)?
- [ ] Who has access?
- [ ] How long is it retained?

### 2. Data Processing Scan

- [ ] Data in databases
- [ ] Data in files/documents
- [ ] Data in logs
- [ ] Data in caches
- [ ] Data in backups
- [ ] Data in analytics
- [ ] Data in third-party services

### 3. Privacy Controls

- [ ] Consent mechanisms
- [ ] Purpose limitation
- [ ] Data minimization
- [ ] Access controls
- [ ] Encryption
- [ ] Anonymization/pseudonymization
- [ ] Secure deletion

### 4. Data Subject Rights (GDPR)

- [ ] Right to access
- [ ] Right to rectification
- [ ] Right to erasure (deletion)
- [ ] Right to data portability
- [ ] Right to object
- [ ] Right to restrict processing

### 5. Privacy by Design

- [ ] Privacy impact assessment
- [ ] Data protection by default
- [ ] Minimize data collection
- [ ] Transparent processing
- [ ] User control mechanisms

## PII Detection Patterns

Load the full grep battery from
[refs/pii-detection.md](refs/pii-detection.md) and run it against the target:

- **Direct identifiers**: names, emails, phone numbers, addresses,
  government IDs
- **Indirect identifiers**: IP addresses, device IDs, location data,
  behavioral data
- **Sensitive data (GDPR special categories)**: health, biometric, genetic

## Privacy Violation Detection

The same ref carries the violation greps, classified by priority:

- **Critical (P0)**: PII in logs, unencrypted PII transmission, PII in error
  messages, no consent mechanism
- **High (P1)**: missing data retention policy, no privacy notice,
  third-party data sharing without notice

## GDPR Compliance Checks

### Article 5: Principles

- [ ] **Lawfulness, Fairness, Transparency**: lawful basis documented; privacy notice provided; processing disclosed
- [ ] **Purpose Limitation**: purpose specified; data not used for incompatible purposes
- [ ] **Data Minimization**: only necessary data collected; no excessive data retention
- [ ] **Accuracy**: update mechanisms exist; correction procedures defined
- [ ] **Storage Limitation**: retention periods defined; automated deletion implemented
- [ ] **Integrity & Confidentiality**: encryption implemented; access controls enforced; security measures documented

### Article 6: Lawful Basis

Check for lawful basis — any of: consent obtained, contract necessity, legal
obligation, vital interest, public task, legitimate interest.

### Article 17: Right to Erasure

Verify deletion capability — user-data deletion functions, cascade delete,
and deletion from backups. Verification greps:
[refs/pii-detection.md](refs/pii-detection.md) § GDPR Article Verification.

### Article 32: Security Measures

Verify pseudonymization/anonymization (data masking), encryption (at rest
and in transit), and resilience (backup and recovery). Verification greps:
[refs/pii-detection.md](refs/pii-detection.md) § GDPR Article Verification.

## Privacy by Design Implementation

For reference implementations — data minimization, consent management, data
subject rights endpoints, and PII-sanitizing loggers — load
[refs/privacy-patterns.md](refs/privacy-patterns.md). Use them as the model
for remediation code you recommend.

## Output Format

Report in the structured format from
[refs/output-format.md](refs/output-format.md): target + framework + Status
(COMPLIANT | NEEDS ATTENTION | NON-COMPLIANT) + sensitivity level, data
inventory table (type/location/purpose/legal basis/retention), PII detection
results with file:line, P0/P1 privacy violations with location/impact/
remediation, GDPR compliance status per article, data-subject-rights
implementation table, privacy-by-design assessment, remediation plan
(P0 block-deployment / P1 this sprint / P2 next sprint), evidence for
DPO/audit, and next steps.

## Task Integration

Append the privacy analysis to the current task's description — the harness's task list where it has one (the `wicked-garden-workflow` skill's `refs/integration.md` carries the field list and the harness-specific Hand-off), else your working notes:
```markdown
{original description}

## GDPR Analysis

**PII Detected**: {count} locations
**Violations**: {P0 count} critical

## Critical Issues
- {violation}

## Remediation
1. {action}
```

## Quality Standards

- Specific PII locations cited
- GDPR articles referenced
- Clear remediation steps
- Data flow documented
- Legal basis validated


## Dispatch

Worker skill, reached by its name — `wicked-garden-platform-privacy-expert` — through a
Hand-off from the `wicked-garden-platform` router or any caller. The pre-v12.25
subagent-delegation form is retired with the fork frontmatter.

Files in this skill

  • SKILL.md6 KB
  • refs/output-format.md3.4 KB
  • refs/pii-detection.md3 KB
  • refs/privacy-patterns.md2.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.