agentleFS
marianadacunhamarianadacunha/design-skills/skills/data-privacy-compliance/SKILL.md

data-privacy-compliance

Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub

Run a data privacy and compliance audit on products, codebases and company operations. Use this skill whenever the user mentions LGPD, ISO 27001, HIPAA, data protection, proteção de dados, auditoria de privacidade, compliance de dados pessoais, information security, or asks to check if their product/code/company is compliant with any privacy or security framework. Also trigger when the user asks about consent flows, data subject rights, bases legais, tratamento de dados pessoais, encarregado/DPO, ANPD, BAA, PHI, ePHI, ISO controls, or gap assessment. Even if the user just says "audit my app for privacy", "check if we're handling user data correctly", or "are we ISO ready" — this skill applies. Produces a structured report (docx) and a compliance checklist (md), both calibrated for Product/Design and Leadership audiences.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.