Mermaid Diagrams
Create, review, render, and maintain Mermaid diagrams for architecture, flows, sequences, state machines, schemas, timelines, and tradeoffs. Use when a visual model materially clarifies structure or behavior and the result should remain diagrams-as-code or exported SVG/PNG.
Install
$ agentstack add skill-zacharygcook-agent-skills-mermaid-diagrams ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-zacharygcook-agent-skills-mermaid-diagrams) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Mermaid Diagrams
Use a diagram only when relationships, sequence, hierarchy, state, or ownership are harder to understand in prose or a small table.
Choose the Smallest Useful Form
flowchart/graph: pipelines, decisions, dependencies.sequenceDiagram: request/response and async interaction.stateDiagram-v2: lifecycle and transition rules.erDiagram: entities, keys, and cardinality.classDiagram: type/object relationships.- C4 context/container: system boundaries and ownership.
timeline: history or roadmap.quadrantChart: explicit two-axis tradeoffs.
Start with fewer than ten meaningful nodes when possible; split crowded diagrams by concern.
Authoring Rules
- Verify labels and edges against source code or authoritative docs.
- Use short nouns or verb phrases, and quote labels containing punctuation.
- Draw direction only when it carries meaning.
- Encode status or category with color sparingly; never rely on color alone.
- Add a caption that states the diagram's purpose.
- Keep layout deterministic enough that future edits remain readable.
- Prefer SVG for documentation and PNG for quick review when both are supported.
Validate and Render
Use repository-native docs/build tooling first. Otherwise use an already available Mermaid CLI or renderer; do not require a global install merely for a small draft. Inspect the actual render for syntax failures, clipped labels, crossing edges, and light/dark contrast.
Store source and exports according to repository convention. If the user wants only a review artifact, keep scratch source and renders in a gitignored location. If the diagram is durable documentation, track the source next to its consumer and ensure docs do not link to disposable paths.
Handoff
Provide the source, rendered artifact paths, validation command, and any assumptions the diagram makes. Do not claim the visual is authoritative unless it was checked against the implementation.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: zacharygcook
- Source: zacharygcook/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.