pipeline-diagram
Skill4 starsChanged 43 days agoNo licenceView on GitHub
Generate a publication-style processing-pipeline diagram from a small YAML spec: a flowing-backbone OVERVIEW (steps down a backbone, inputs branching in from the left, key decisions as blue annotations, output files branching right) plus an optional PER-STEP DETAIL view (one card per step showing input files -> key params/decisions -> output files). Use when the user wants to diagram, visualize, map, or document an analysis/processing pipeline or multi-script workflow; create a pipeline figure / schematic / flow diagram; or show/communicate the steps, key decisions, and input/output files of a pipeline. Spec-driven by design (you write a short YAML, not auto-parsed from code). Do NOT load for the analysis RESULT figures themselves (networks, heatmaps, trees), for generic flowcharts unrelated to a data pipeline, or for Quarto/script scaffolding (use script-organization).
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- audit-projectSkill
- audit-scriptSkill
- audit-skillsSkill
- cleanup-scriptsSkill
- conda-envSkill
- data-handlingSkill
- debugging-before-patchingSkill
- deep-research-genelistSkill
- deep-research-reportsSkill
- doneSkill
- expression-reportSkill
- feedback-walkthroughSkill
- figure-exportSkill
- file-safetySkill
- gene-lookupSkill
- git-conventionsSkill
- handoffSkill
- hpcSkill
- learn-codeSkill
- new-planSkill
- new-projectSkill
- new-skillSkill
- plugin-feedbackSkill
- protein-phylogenySkill
- quarto-book-setupSkill
- quarto-docsSkill
- publishSkill
- r-plotting-styleSkill
- r-renvSkill
- script-organizationSkill
- security-setupSkill
- sync-projectSkill
- tree-formattingSkill
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.
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.