mermaid-diagram-generator
Skill28 starsChanged 32 days agoMITView on GitHub
Use when users need Mermaid diagrams for Arduino code structure, state machines, timing diagrams, task architecture, or workflow documentation.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- wedsamuel1230/arduino-skillsword for word, first seen Nov 1, 2026
- mike22890/opencode-skills-entheir own version, first seen Oct 15, 2026
- mike22890/opencode-skills-cntheir own version, first seen Sep 13, 2026
- shalomb/agent-skillstheir own version, first seen Aug 23, 2026
Other versions4 projects use a version of this.
Word for word · 1
- wedsamuel1230/arduino-skills★ 28100% same
Edited · 0
None found.
Wrote their own version · 3
- shalomb/agent-skills★ 3same name
- mike22890/opencode-skills-cn★ 1same name
- mike22890/opencode-skills-en★ 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 repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/arduino-skills.mdcCursor rule
- cli-creatorSkill
- plugin-creatorSkill
- skill-creatorSkill
- arduino-cli-skillSkill
- arduino-code-generatorSkill
- arduino-project-builderSkill
- arduino-serial-monitorSkill
- arduino-workflow-routerSkill
- battery-selectorSkill
- board-selectionSkill
- board-supportSkill
- bom-generatorSkill
- boot-flash-recoverySkill
- bus-debuggingSkill
- circuit-debuggerSkill
- code-review-facilitatorSkill
- datasheet-interpreterSkill
- embedded-build-workflowSkill
- embedded-project-loopSkill
- enclosure-designerSkill
- error-message-explainerSkill
- fault-forensicsSkill
- field-power-and-connectivity-triagerSkill
- freertos-patternsSkill
- hardware-tddSkill
- i2c-bringup-diagnosticianSkill
- library-selectionSkill
- memory-budgetingSkill
- memory-timing-debuggingSkill
- micropython-developmentSkill
- non-blocking-patternsSkill
- ota-deployment-guardianSkill
- pico-sdk-developmentSkill
- pin-assignmentSkill
- power-budget-calculatorSkill
- probe-debuggingSkill
- readme-generatorSkill
- realtime-control-designSkill
- sensor-calibration-workbenchSkill
- sensor-signal-filteringSkill
- stm32-developmentSkill
- usb-debuggingSkill
- wireless-telemetrySkill
- wiring-safety-checkSkill
- zephyr-developmentSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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
- Distinctive: line 21
Use this skill when the request asks to:
- Distinctive: line 25
document timing or protocol sequences
- Distinctive: line 27
add a diagram to project documentation
- Distinctive: line 29
Do not use it for tiny code snippets where a diagram adds no clarity.
- Distinctive: line 38
Prefer the simplest diagram that explains the behavior.
- Very specific: line 39
Use scripts/generate_diagram.py when the input is structured enough for automation.
- Very specific: line 41
Run through references/validation-checklist.md before presenting the final Mermaid output.
- Distinctive: line 60
Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Mermaid Diagram Generator
Generate Mermaid diagrams from Arduino and embedded-system concepts without loading unnecessary detail up front.
Resources
scripts/generate_diagram.py- CLI generator for diagram outputreferences/diagram-templates.md- Mermaid templates by diagram typereferences/code-patterns.md- code-to-diagram extraction heuristicsreferences/validation-checklist.md- rendering and syntax checks
When to Use
Use this skill when the request asks to:
- visualize a state machine
- turn code into a flowchart
- document timing or protocol sequences
- show FreeRTOS task relationships
- add a diagram to project documentation
Do not use it for tiny code snippets where a diagram adds no clarity.
Workflow
- Identify the diagram type:
- state flow -> open
references/code-patterns.md - timing or protocol sequence -> open
references/diagram-templates.md - task architecture -> open both
code-patterns.mdanddiagram-templates.md
- state flow -> open
- Prefer the simplest diagram that explains the behavior.
- Use
scripts/generate_diagram.pywhen the input is structured enough for automation. - Run through
references/validation-checklist.mdbefore presenting the final Mermaid output.
Verification
- Mermaid syntax parses without errors.
- The diagram uses the correct abstraction level for the request.
- State names, transitions, or signals match the source material exactly.
- The output is readable without reverse-engineering the code.
Integration
- Pair with
freertos-patternsfor task and synchronization diagrams. - Pair with
arduino-code-generatorwhen a generated sketch also needs visual documentation. - Pair with
readme-generatorwhen the diagram should ship in repository docs.
Shared Output Contract
Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.
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.

