agentleFS
bharathgnanabharathgnana/archdiagram/.claude/skills/data-flow/SKILL.md

data-flow

Skill1 starsChanged 18 days agoMITView on GitHub

Use for stores, feeds, transforms, documents, and lineage between data sources and consumers.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Autocss-com/ai★ 1same name
    2. sankalpaacharya/skills★ 1same 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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for where data comes from, how it changes, and where it lands.

    line 8
  2. Very specific:

    Use shape: "data_store", process, io, document, or decision according to each node's role.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Use this skill for where data comes from, how it changes, and where it lands. Use a cylinder for persistent stores, a process shape for transforms, an IO shape for a feed, and a document shape for a produced artifact.

Spec rules

  • Use shape: "data_store", process, io, document, or decision according to each node's role.
  • Each lineage edge uses source, target, and kind: "data"; label it with the dataset or contract if useful.
  • direction: "LR" is the normal default. Use tier to keep stages in order. IDs must be unique strings.
  • Service icons may coexist with shapes when a concrete cloud service matters.
{"title":"Investment lineage","direction":"LR","nodes":[{"id":"feed","shape":"io","label":"Trade feed"},{"id":"clean","shape":"process","label":"Normalize"},{"id":"store","shape":"data_store","label":"Warehouse"},{"id":"report","shape":"document","label":"Risk report"}],"edges":[{"source":"feed","target":"clean","kind":"data","label":"trades"},{"source":"clean","target":"store","kind":"data","label":"curated"},{"source":"store","target":"report","kind":"data","label":"positions"}]}

Render and inspect

On first use run python -m tools.bootstrap. Run python -m archdiagram.cli validate spec.json, then python -m archdiagram.cli render spec.json -f svg -o out/lineage.svg. Other formats are drawio, html, pdf, pptx, and vsdx; PDF needs python -m tools.bootstrap --pdf. Check direction, dataset labels, and store boundaries, then revise and render again. Via MCP, use get_diagram_template("data_flow"), validate_spec, and generate_diagram.

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.