agentleFS
JunMA98JunMA98/Computer-science-claude-skills/skills/scientific-schematics/SKILL.md

scientific-schematics

Skill3 starsChanged 8 months agoMITView on GitHub

Create polished technical diagrams for CS papers, slides, posters, demos, and repo documentation. Use when a Mermaid diagram is not enough and the task needs a cleaner architecture figure, system overview, pipeline graphic, benchmark setup diagram, or agent workflow illustration.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use scikit-bio.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • tondevrelSkill

    scikit-bio

    Library for bioinformatics and community ecology statistics. Provides data structures and algorithms for sequences, alignments, phylogenetics, and diversity analysis. Essential for microbiome research and ecological data science. Use for alpha/beta diversity metrics, ordination (PCoA), phylogenetic trees, sequence manipulation (DNA/RNA/Protein), distance matrices, PERMANOVA, and community ecology analysis.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for polished technical figures, not for routine text-native diagrams.

    line 8
  2. Distinctive:

    Start from the message the figure must communicate.

    line 21
  3. Distinctive:

    Avoid overloading one figure with both architecture and results.

    line 24
  4. Distinctive:

    Prefer a small number of well-grouped components over exhaustive detail.

    line 25
  5. Very specific:

    Read references/best_practices.md when you need diagram design guidance.

    line 29
  6. Distinctive:

    Use local scripts only when the configured image-generation workflow is available and the user actually wants rendered figures:

    line 31
  7. Very specific:

    Use markdown-mermaid-writing for editable diagrams in docs and notes.

    line 39
  8. Distinctive:

    Use this skill when the figure is headed into a paper, poster, deck, or polished README.

    line 40
  9. Distinctive:

    When the user asks for a diagram without a target format, return:

    line 44

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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

Scientific Schematics

Use this skill for polished technical figures, not for routine text-native diagrams. Prefer Mermaid first when editability matters more than appearance.

Good Fits

  • model architecture overviews
  • system component diagrams
  • agent or tool-call workflows
  • training / inference pipelines
  • benchmark or evaluation setup figures
  • data processing or serving architecture diagrams

Working Rules

  • Start from the message the figure must communicate.
  • Label components by role, not by decorative wording.
  • Make data flow, control flow, and evaluation boundaries explicit.
  • Avoid overloading one figure with both architecture and results.
  • Prefer a small number of well-grouped components over exhaustive detail.

Local Resources

Read references/best_practices.md when you need diagram design guidance.

Use local scripts only when the configured image-generation workflow is available and the user actually wants rendered figures:

  • scripts/generate_schematic.py
  • scripts/generate_schematic_ai.py

The quick-reference files in references/ are inherited upstream support material. Use them selectively.

Relationship to Other Skills

  • Use markdown-mermaid-writing for editable diagrams in docs and notes.
  • Use this skill when the figure is headed into a paper, poster, deck, or polished README.

Default Output

When the user asks for a diagram without a target format, return:

  1. the figure concept
  2. required components and labels
  3. a recommended diagram structure
  4. whether Mermaid or a rendered schematic is the better fit

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.