agentleFS
Sign inStart free
mtarcuremtarcure/claude-vibe-squad/.agents/skills/data-flow-trace/SKILL.md

data-flow-trace

Skill220 starsChanged 17 days agoMITView on GitHub

Use when reviewing how a system handles sensitive or personal data: trace each data class through collection, storage, processing, sharing, retention, and deletion to surface privacy gaps, over-retention, or undisclosed sharing. Triggers on privacy review, DPIA, data-handling audit, or a schema/log that carries PII.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Every source has a terminal store, processor, recipient, or explicit unknown edge.

    line 27

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

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

Data Flow Trace

Trace sensitive data through collection, storage, processing, sharing, retention, and deletion paths for privacy review.

Inputs

  • System boundaries, actors, data stores, processors, and trust zones.
  • Data classes, purposes, legal or policy constraints, and retention promises.
  • Evidence from code, configuration, schemas, logs, and operator-provided diagrams.

Method

  1. Enumerate data sources and classify each field by sensitivity and subject.
  2. Trace every transformation and transfer across trust or jurisdiction boundaries.
  3. Record purpose, access principal, encryption state, retention, and deletion behavior at each hop.
  4. Mark inferred edges separately and identify the evidence needed to confirm them.
  5. Compare observed flows with stated notice, consent, minimization, and deletion commitments.

Acceptance

  • Every source has a terminal store, processor, recipient, or explicit unknown edge.
  • Cross-boundary transfers identify sender, receiver, protocol, and protection state.
  • Retention and deletion paths are included, not just collection and use.
  • Findings distinguish verified evidence from assumptions and rank remediation by exposure.

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.

Check your setup, free