agentleFS
Sign inStart free
WH-2099WH-2099/mermaid-skill/.claude/skills/mermaid/SKILL.md

mermaid

Skill268 starsChanged 3 months agoMITView on GitHub

Generate Mermaid diagrams from user requirements. Supports flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, and 18 more diagram types.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Read Documentation: Read the corresponding syntax reference for the diagram type

    line 16
  2. Distinctive:

    Use semantic node naming

    line 65

“Common” is measured: kept by at least 6 in 10 of the 36 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

Mermaid Diagram Generator

Generate high-quality Mermaid diagram code based on user requirements.

Workflow

  1. Understand Requirements: Analyze user description to determine the most suitable diagram type
  2. Read Documentation: Read the corresponding syntax reference for the diagram type
  3. Generate Code: Generate Mermaid code following the specification
  4. Apply Styling: Apply appropriate themes and style configurations

Diagram Type Reference

Select the appropriate diagram type and read the corresponding documentation:

TypeDocumentationUse Cases
Flowchartflowchart.mdProcesses, decisions, steps
Sequence DiagramsequenceDiagram.mdInteractions, messaging, API calls
Class DiagramclassDiagram.mdClass structure, inheritance, associations
State DiagramstateDiagram.mdState machines, state transitions
ER DiagramentityRelationshipDiagram.mdDatabase design, entity relationships
Gantt Chartgantt.mdProject planning, timelines
Pie Chartpie.mdProportions, distributions
Mindmapmindmap.mdHierarchical structures, knowledge graphs
Timelinetimeline.mdHistorical events, milestones
Git Graphgitgraph.mdBranches, merges, versions
Quadrant ChartquadrantChart.mdFour-quadrant analysis
Requirement DiagramrequirementDiagram.mdRequirements traceability
C4 Diagramc4.mdSystem architecture (C4 model)
Sankey Diagramsankey.mdFlow, conversions
XY ChartxyChart.mdLine charts, bar charts
Block Diagramblock.mdSystem components, modules
Packet Diagrampacket.mdNetwork protocols, data structures
Kanbankanban.mdTask management, workflows
Architecture Diagramarchitecture.mdSystem architecture
Radar Chartradar.mdMulti-dimensional comparison
Treemaptreemap.mdHierarchical data visualization
User JourneyuserJourney.mdUser experience flows
ZenUMLzenuml.mdSequence diagrams (code style)

Configuration & Themes

  • Theming - Custom colors and styles
  • Directives - Diagram-level configuration
  • Layouts - Layout direction and spacing
  • Configuration - Global settings
  • Math - LaTeX math support

Output Specification

Generated Mermaid code should:

  1. Be wrapped in ```mermaid code blocks
  2. Have correct syntax that renders directly
  3. Have clear structure with proper line breaks and indentation
  4. Use semantic node naming
  5. Include styling when needed to improve visual appearance

Example Output

flowchart TD
    A[Start] --> B{Condition}
    B -->|Yes| C[Execute]
    B -->|No| D[End]
    C --> D

User requirements: $ARGUMENTS

Download now (ZIP)

  • Other versions43 projects use a version of this.

    Word for word · 4

    1. Kripu77/software-factory★ 7100% same
    2. MovGP0/Skills★ 1100% same
    3. willlee1995/skills★ 1100% same
    4. IsaacBell/ai-marketing-toolkit★ 0100% same

    Edited · 3

    1. chrislacey89/skills★ 410% same
    2. blas1n/claude-skills★ 252% same
    3. chrislacey89/content-to-skill★ 110% same

    Wrote their own version · 36

    1. puncsky/system-design-and-architecture★ 3.6ksame name
    2. alibaba/loongcollector★ 2.2ksame name
    3. chujianyun/skills★ 748same name
    4. bex-co/bex★ 577same name
    5. xenodium/emacs-skills★ 142same name
    6. mgifford/accessibility-skills★ 48same name
    7. nilecui/SkillsBase★ 27same name
    8. greedychipmunk/agent-skills★ 24same name
    9. ulises-jeremias/agent-toolkit★ 19same name
    10. soujava/agent-skills★ 10same name

    26 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.

  • Used alongsideProjects with it also use ansible, plantuml and 6 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.
    • julweberSkill

      ansible

      Ansible automation reference for playbooks, roles, inventory, variables, and modules. Includes Proxmox VE and Docker integration via community.general and community.docker collections. Use when writing playbooks, troubleshooting Ansible runs, or designing automation workflows. Triggers: ansible, playbook, inventory, role, task, handler, vars, jinja2, galaxy, proxmox_kvm, proxmox_lxc, docker_container, docker_compose.

      Also in 3 projects that use this

    • xenodiumSkill

      plantuml

      This skill should be used when the user invokes "/plantuml" to create a diagram from the current context using PlantUML and output the resulting image path.

      Also in 3 projects that use this

    • ihiteshguptaSkill

      terraform

      Expert in Infrastructure as Code with Terraform. Use for creating, managing, and versioning infrastructure across cloud providers.

      Also in 3 projects that use this

    • PostHogSkill

      karpathy-guidelines

      Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria. Based on https://github.com/multica-ai/andrej-karpathy-skills.

      Also in 3 projects that use this

    • AWSSkill

      ship

      Finalize dev work on an issue branch — update docs, push, and open a PR.

      Also in 4 projects that use this

    • SentrySkill

      commit

      Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

      Also in 4 projects that use this

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.

Check your setup, free