mermaid-diagrams
Skill60 starsChanged 2 months agoMITView on GitHub
Create or fix Mermaid diagrams in Markdown. Use for requested flowcharts, sequence diagrams, ER diagrams, state machines, or system diagrams when Mermaid is the output format; not every visualization or explanation.
64 other projects use a version of this.
Adopted by
Most recently taken up by
- selamy-labs/agent-skillstheir own version, first seen Nov 8, 2026
- gspencergoog/skillstheir own version, first seen Nov 8, 2026
- openclaw/openclaw-enterprisetheir own version, first seen Nov 8, 2026
- The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026
- compozy/compozytheir own version, first seen Nov 7, 2026
- flopperj/dotfiles-coretheir own version, first seen Nov 4, 2026
Used with
Projects with it also use analytics-metrics, aws-account-management and 10 more.
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.
hoodiniSkillanalytics-metrics
Build data visualization and analytics dashboards. Use when creating charts, KPI displays, metrics dashboards, or data visualization components. Triggers on analytics, dashboard, charts, metrics, KPI, data visualization, Recharts.
Also in 3 projects that use this
- hoodiniSkill
aws-account-management
Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, Identity Center.
Also in 3 projects that use this
LangChainSkilllangchain
Build agents with a prebuilt architecture and integrations for any model or tool. Use when creating tool-calling agents, switching model providers, or adding structured output.
Also in 3 projects that use this
imehrSkillrailway
Railway.com deployment and management - deployment, logs, migrations, troubleshooting, monorepo strategies, security, and CLI reference. Use when deploying to Railway, configuring services, managing environment variables, or debugging deployment issues.
Also in 3 projects that use this
- +8 more from hoodini
Other versions64 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 64
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- langchain-ai/openwiki★ 18ksame name
- compozy/compozy★ 2.9ksame name
- pedronauck/skills★ 649same name
- openclaw/openclaw-enterprise★ 454same name
- hoodini/ai-agents-skills★ 295same name
- shep-ai/shep★ 277same name
- veelenga/claude-mermaid★ 222same name
- magnus919/agent-skills★ 172same name
54 more not listed
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 repository10 other files it gives its agents.
- bazelSkill
- clean-ddd-hexagonalSkill
- feature-slicingSkill
- modern-cssSkill
- modern-javascriptSkill
- postgres-drizzleSkill
- slack-block-kitSkill
- slack-mrkdwnSkill
- teams-adaptive-cardsSkill
- teams-message-formattingSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 60 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 23
Use supplied evidence for nodes, edges, cardinalities, dates, and values.
- Distinctive: line 28
Prefer stable syntax supported by the destination.
- Distinctive: line 30
Keep ER attributes one per line and alias sequence participants whose names contain spaces.
- Distinctive: line 50
Check Mermaid documentation and the destination's own support notes when a feature is version-sensitive.
“Common” is measured: kept by at least 6 in 10 of the 60 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.
Files
Mermaid Diagrams
Turn the supplied process, code, schema, or relationships into the requested Mermaid diagram. The user's explicit instructions take precedence over this skill's guidelines, including their choice of output format.
Choose the representation
Establish the facts to show and the destination renderer. If the request leaves the format open and a text-based system/process diagram fits, Mermaid is a reasonable choice. Preserve an explicitly requested drawing tool or artifact format.
| Question | Diagram |
| What happens next or which path is taken? | flowchart |
| Who calls whom, in what order? | sequenceDiagram |
| What tables and cardinalities exist? | erDiagram |
| What states and transitions exist? | stateDiagram-v2 |
| How are types or services related? | classDiagram or flowchart with subgraphs |
| What is scheduled or measured? | A matching planning/data type from the references |
Use supplied evidence for nodes, edges, cardinalities, dates, and values. Mark conceptual assumptions; ask for missing facts that determine the diagram rather than inventing a system.
Produce a renderable result
- Return a fenced
mermaidblock, or the requested.mmd/rendered artifact. Use one diagram declaration per block. - Prefer stable syntax supported by the destination. Examples were checked against Mermaid 11.16; a host can bundle an older version.
- Give nodes stable IDs distinct from display labels and subgraph IDs. Quote labels with punctuation; avoid reserved
endIDs and use%%comments on their own lines. - Keep ER attributes one per line and alias sequence participants whose names contain spaces.
- Split diagrams when readability suffers, not at a fixed node count.
Validate nontrivial or repaired syntax with the project's renderer or an available Mermaid CLI. Inspect the rendered result when producing an artifact; if rendering is unavailable, state that limitation. A simple syntax answer does not require installing a new toolchain.
References
Load the diagram type or rendering topic required.
| Task | Reference |
| Flowcharts, subgraphs, shapes, edges | FLOWCHARTS.md |
| Calls, activation, loops, alternatives | SEQUENCE.md |
| Classes, types, database relationships | CLASS-ER.md |
| State machines and user journeys | STATE-JOURNEY.md |
| Gantt, timeline, pie, XY, sankey, mindmap, gitGraph | DATA-CHARTS.md |
| C4, architecture, block, kanban, packet, requirements | ARCHITECTURE.md |
| Configuration, styling, export, troubleshooting | ADVANCED.md |
| Compact syntax and platform lookup | CHEATSHEET.md |
Check Mermaid documentation and the destination's own support notes when a feature is version-sensitive.
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.