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
- ZenRows/clitheir own version, first seen Oct 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ZenRows/cli★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- brand-guidelinesSkill
- intent-templateSkill
- secure-api-reviewSkill
- security-policySkill
- ux-standardsSkill
- brand-guidelinesSkill
- compliance-policySkill
- intent-templateSkill
- secure-api-reviewSkill
- security-policySkill
- ux-standardsSkill
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
- Distinctive: line 17
Lawful basis and purpose: every new personal-data field states its purpose and basis.
- Distinctive: line 28
Never mark a requirement "not applicable" without saying why.
≈ “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.
Files
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
- Lawful basis and purpose: every new personal-data field states its purpose and basis.
- Data minimisation: collect only what the stated outcome needs.
- Retention: define how long the data lives and how it is deleted (
<retention schedule>). - Residency: data stays in
<regions>; no new cross-border transfer without approval. - Third parties: a new processor or SaaS needs a DPA / vendor review (
<process link>). - Audit trail: regulated actions are logged immutably with actor and timestamp.
- 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.
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
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.

