gdpr-data-handling — Claude Code skill: what it does, install
Guides GDPR data handling with consent management, data subject rights, and privacy by design. Use it when a system processes EU personal data.
/plugin marketplace add wshobson/agents
/plugin install hr-legal-compliance@claude-code-workflowsWhat gdpr-data-handling does
This skill guides GDPR data processing work, from choosing a lawful basis to designing consent controls. It covers basic, sensitive, criminal, and children’s data, plus access, rectification, erasure, restriction, portability, and objection rights.
The package includes a practical guide, a data-category table, lawful-basis notes, and controls for data minimization, processing records, PII encryption, need-to-know access, and retention. Detailed implementation patterns live in references/details.md, which is the next file to read when the summary is not enough.
Use it while building consent management, handling DSRs, or reviewing a privacy-first architecture. Check opt-in behavior, separate consent purposes, and safeguards for transfers, such as SCCs or adequacy decisions. It fits systems that process EU personal data; projects outside that scope have little reason to add it.
What it helps with
- choose a lawful basis for processing personal data
- design consent flows without pre-checked boxes
- handle a data subject request for access or erasure
- classify personal data and its protection level
- review PII retention, encryption, and transfer controls
Example prompts for the agent
- Review the lawful basis for processing email and phone data in `src/consent.ts`.
- Design a DSR erasure flow and its response deadline.
- Run a GDPR compliance review using `references/details.md`.
How to install gdpr-data-handling
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install hr-legal-compliance@claude-code-workflowsThis installs the whole hr-legal-compliance plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill gdpr-data-handling -a claude-code3Manually: put the files in place
~/.claude/skills/gdpr-data-handling/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gdpr-data-handling/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill gdpr-data-handling -a codex2Manually: put the files in place
.agents/skills/gdpr-data-handling/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill gdpr-data-handling -a cursor2Manually: put the files in place
.cursor/skills/gdpr-data-handling/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents gdpr-data-handling2Manually: put the files in place
.github/skills/gdpr-data-handling/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/hr-legal-compliance/skills/gdpr-data-handlingManually: put the files in place
.devin/skills/gdpr-data-handling/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about gdpr-data-handling
How do I install gdpr-data-handling in Claude Code?
Add the marketplace with /plugin marketplace add wshobson/agents, install the plugin with /plugin install hr-legal-compliance@claude-code-workflows, or run npx skills add wshobson/agents --skill gdpr-data-handling -a claude-code. The skill file is placed at ~/.claude/skills/gdpr-data-handling/SKILL.md.
What does gdpr-data-handling do?
It guides GDPR data handling through consent management, data subject rights, and privacy by design. It also covers processing records, access controls, retention, encryption, and transfer safeguards.
Which platforms support gdpr-data-handling?
The skill is intended for Claude Code, Codex, and Cursor. Each platform uses its own npx skills add installation command.
Source text
SKILL.md · MIT
--- name: gdpr-data-handling description: Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews. --- # GDPR Data Handling Practical implementation guide for GDPR-compliant data processing, consent management, and privacy controls. ## When to Use This Skill - Building systems that process EU personal data - Implementing consent management - Handling data subject requests (DSRs) - Conducting GDPR compliance reviews - Designing privacy-first architectures - Creating data processing agreements ## Core Concepts ### 1. Personal Data Categories | Category | Examples | Protection Level | | ---------------------- | --------------------------- | ------------------ | | **Basic** | Name, email, phone | Standard | | **Sensitive (Art. 9)** | Health, religion, ethnicity | Explicit consent | | **Criminal (Art. 10)** | Convictions, offenses | Official authority | | **Children's** | Under 16 data | Parental consent | ### 2. Legal Bases for Processing ``` Article 6 - Lawful Bases: ├── Consent: Freely given, specific, informed ├── Contract: Necessary for contract performance ├── Legal Obligation: Required by law ├── Vital Interests: Protecting someone's life ├── Public Interest: Official functions └── Legitimate Interest: Balanced against rights ``` ### 3. Data Subject Rights ``` Right to Access (Art. 15) ─┐ Right to Rectification (Art. 16) │ Right to Erasure (Art. 17) │ Must respond Right to Restrict (Art. 18) │ within 1 month Right to Portability (Art. 20) │ Right to Object (Art. 21) ─┘ ``` ## Detailed worked examples and patterns Detailed sections (starting with `## Implementation Patterns`) live in `references/details.md`. Read that file when the navigation summary above is insufficient. ## Best Practices ### Do's - **Minimize data collection** - Only collect what's needed - **Document everything** - Processing activities, legal bases - **Encrypt PII** - At rest and in transit - **Implement access controls** - Need-to-know basis - **Regular audits** - Verify compliance continuously ### Don'ts - **Don't pre-check consent boxes** - Must be opt-in - **Don't bundle consent** - Separate purposes separately - **Don't retain indefinitely** - Define and enforce retention - **Don't ignore DSARs** - 30-day response required - **Don't transfer without safeguards** - SCCs or adequacy decisions
© Seth Hobson · MIT · wshobson/agents