dataflow-diagram
Skill6 starsChanged 3 months agoNo licenceView on GitHub
Draw a dataflow or pipeline diagram for a program that already exists in code — a DAG, a processing chain, a stream topology, a service graph. Use when asked to "diagram the pipeline", "show the dataflow", "chart the DAG", "visualize how the data moves", "make a graph of the program", or when a design doc or PR needs a picture of a running system. Symptoms that this skill applies: a hand-maintained diagram that no longer matches the code, a chart whose legend disagrees with the chart, a glyph reused for two different kinds of thing, a diagram that silently omits a node nobody classified, a legend placed by eye that overlaps an edge, or a picture that is a screenshot rather than a source file.
In this repository26 other files it gives its agents.
- document-featureSkill
- recommend-skillsSkill
- seed-skill-templateSkill
- architecture-diagramSkill
- catchupSkill
- engineering-journalSkill
- format-layout-diagramSkill
- review-exchangeSkill
- review-guideSkill
- rust-source-layoutSkill
- sharable-artifactSkill
- sweep-commentsSkill
- technical-proseSkill
- close-arcSkill
- define-scopeSkill
- discussSkill
- frame-problemSkill
- open-arcSkill
- open-inquirySkill
- plan-featureSkill
- propose-designSkill
- reconcile-vaultSkill
- record-decisionSkill
- submit-explorationSkill
- synthesizeSkill
- vault-searchSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.