agentleFS
OBaruchOBaruch/ai-native-sdlc-template/.agents/skills/compliance-policy/SKILL.md

compliance-policy

Skill4 starsChanged 32 days agoMITView on GitHub

Apply regulatory and compliance requirements (e.g. GDPR, SOC 2, PCI DSS, HIPAA, sector rules). Use when a change stores, moves, exports or deletes personal or regulated data, changes retention, adds a data processor or third party, or touches audit trails and consent.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Lawful basis and purpose: every new personal-data field states its purpose and basis.

    line 17
  2. Distinctive:

    Never mark a requirement "not applicable" without saying why.

    line 28

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compliance requirements

Owner: <compliance officer> · Source of truth: <link to the compliance register> · Version: <x.y>

<!-- TEMPLATE: keep only the regimes that apply to you and replace the placeholders. -->

Applicable regimes

  • <Regime A, e.g. GDPR> — scope: <which products / data>
  • <Regime B> — scope: <...>

Requirements to check

  1. Lawful basis and purpose: every new personal-data field states its purpose and basis.
  2. Data minimisation: collect only what the stated outcome needs.
  3. Retention: define how long the data lives and how it is deleted (<retention schedule>).
  4. Residency: data stays in <regions>; no new cross-border transfer without approval.
  5. Third parties: a new processor or SaaS needs a DPA / vendor review (<process link>).
  6. Audit trail: regulated actions are logged immutably with actor and timestamp.
  7. Data subject rights: the change keeps export and deletion working for <systems>.

Output

In spec.md, add a Compliance subsection listing each requirement touched and how it is met. Anything unclear or conflicting goes under Areas of concern, addressed to this policy's owner. Never mark a requirement "not applicable" without saying why.

Download now (ZIP)

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.