mcpbeat

Gdpr Data Handling

dokhacgiakhoa/gdpr-data-handling

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.

5k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill gdpr-data-handling

What comes with it

19 874 bytes besides the instruction
sub-skills/implementation-playbook.md

The instruction itself

7 sections, as written by the author

GDPR Data Handling

Practical implementation guide for GDPR-compliant data processing, consent management, and privacy controls.

Use this skill when

  • 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

Do not use this skill when

  • The task is unrelated to gdpr data handling
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

🧠 Knowledge Modules (Fractal Skills)

1. implementation-playbook

How to use it

Copy the folder

Take dokhacgiakhoa/gdpr-data-handling from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.