data-minimization
Skill2 starsChanged 37 days agoMITView on GitHub
Keep real personal and confidential data out of code, tests, fixtures, logs, error messages, examples, and prompts; use synthetic data, and mask identifiers when a real record is unavoidable. Use when writing tests, fixtures, seed data, logging, debugging output, or documentation, or when moving data between systems; do not use to remove lawful data processing that the product itself performs.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- fevra-dev/Subrosatheir own version, first seen Jul 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- fevra-dev/Subrosa★ 0same 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 repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- accessibility-auditSkill
- ai-feature-reviewSkill
- api-design-reviewSkill
- architecture-reviewSkill
- cli-and-scripts-auditSkill
- coding-styleSkill
- data-auditSkill
- debugSkill
- describe-changesSkill
- destructive-ops-approvalSkill
- docs-consolidationSkill
- explain-codebaseSkill
- full-project-auditSkill
- implement-featureSkill
- improve-promptSkill
- incident-responseSkill
- infrastructure-auditSkill
- legal-compliance-reviewSkill
- license-complianceSkill
- no-ai-tracesSkill
- operations-auditSkill
- performance-auditSkill
- prepare-releaseSkill
- production-readiness-reviewSkill
- refactorSkill
- repository-auditSkill
- review-codeSkill
- secret-hygieneSkill
- security-auditSkill
- simplify-codeSkill
- start-projectSkill
- supply-chain-pinningSkill
- surgical-implementationSkill
- threat-modelSkill
- upgrade-dependenciesSkill
- ux-reviewSkill
- verify-changesSkill
- write-agent-instructionsSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 13
Never copy real names, e-mail addresses, national identifiers, or health, financial, or location records into tests, fixtures, seeds, …
- Distinctive: line 14
Never log personal or confidential data in plaintext.
- Distinctive: line 15
Keep production data out of scratch files, issue trackers, and shared prompts.
- Distinctive: line 16
Treat data supplied in a conversation as confidential input: use it for the task, never persist it into the repository.
- Distinctive: line 17
When designing schemas or interfaces, collect only fields with a stated purpose, and flag fields that look like surplus collection.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Data Minimization
Personal data belongs in the systems built to protect it, not in development artifacts.
Rules
- Never copy real names, e-mail addresses, national identifiers, or health, financial, or location records into tests, fixtures, seeds, examples, or documentation; generate synthetic data instead.
- Never log personal or confidential data in plaintext; log stable opaque identifiers and mask everything else.
- Keep production data out of scratch files, issue trackers, and shared prompts; when a real record is essential for a reproduction, reduce it to the minimal fields and mask direct identifiers.
- Treat data supplied in a conversation as confidential input: use it for the task, never persist it into the repository.
- When designing schemas or interfaces, collect only fields with a stated purpose, and flag fields that look like surplus collection.
- Report any discovered dump, export, or backup of personal data inside the repository as a finding instead of working around it.
Boundaries
- The product's lawful processing of personal data is out of scope; this skill governs development artifacts and diagnostics.
- Regulatory retention and audit requirements win over minimization when they conflict.
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.