privacy-data-flow-map
Skill0 starsChanged 5 months agoMITView on GitHub
Use when mapping product flows, event tracking, forms, integrations, or agent workflows into a privacy data-flow map covering collected data, purpose, retention, sharing, consent, and risk.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- database-migration-risk-reviewSkill
- dependency-upgrade-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- roadmap-to-release-planSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
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 14
Use when a product or agent workflow handles user, customer, employee, or sensitive operational data.
- Distinctive: line 15
Do not use when no data collection, storage, sharing, or retention decision is involved.
≈ “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
Privacy Data Flow Map
Purpose
Map what data a workflow collects, where it goes, and which privacy questions need review.
Fit
- Use when a product or agent workflow handles user, customer, employee, or sensitive operational data.
- Do not use when no data collection, storage, sharing, or retention decision is involved.
Inputs
- Product flow, form fields, event names, integration docs, or agent workflow.
- User roles, jurisdictions, retention requirements, and policy constraints if available.
- Known third-party processors or storage destinations.
Workflow
- Inventory data fields and classify sensitivity.
- Map collection, processing, storage, sharing, and deletion.
- Identify purpose, consent, retention, and access-control questions.
- Flag unnecessary collection or unclear data use.
- Recommend privacy review items and minimization options.
Output
Produce Markdown with:
- Data Inventory
- Flow Map
- Purpose And Retention
- Third Parties
- Privacy Risks
- Minimization Options
- Open Questions
Validation
- Data fields are specific, not vague categories.
- Sensitive data is marked clearly.
- Retention and deletion gaps are visible.
- Third-party sharing is not assumed safe.
- Recommendations reduce data where possible.
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.