MCPInstall

mermaid

Create or revise Mermaid diagrams that render inside Markdown, README files, GitHub, GitLab, wikis, and documentation sites. Use when the user explicitly requests Mermaid or needs a Markdown-native flowchart, sequence diagram, state diagram, class diagram, ER diagram, journey, Gantt chart, mind map, timeline, or lightweight architecture diagram. Prefer PlantUML for strict UML/C4 deliverables and ProcessOn only when editable hosted output is requested.

Installs
91
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/full-stack-skills/document-skills --skill mermaid
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads mermaid automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Mermaid Diagrams

Produce valid Mermaid source that communicates relationships more clearly than prose.

Routing

  • Choose Mermaid by default for Markdown-native diagrams.
  • Choose the plantuml skill for strict UML notation, detailed C4, or .puml output. Install with: npx skills add full-stack-skills/document-skills --skill plantuml.
  • Choose the processon-diagram-generator skill when the user explicitly wants ProcessOn or hosted editable rendering. Install with: npx skills add full-stack-skills/document-skills --skill processon-diagram-generator.
  • Do not ask the user to choose a tool when the context already determines a safe default.

Workflow

  1. Extract entities, states, decisions, messages, or dependencies from the request and available source.
  2. Select the smallest suitable diagram type.
  3. Generate syntactically complete Mermaid source.
  4. Keep labels concise and quote labels containing punctuation, parentheses, or special characters.
  5. Validate the structure and, when a Mermaid renderer is available, render it before delivery.
  6. Save a file only when the user asks for a file or the diagram belongs in an existing document.

Diagram selection

NeedMermaid declaration
Process or decisionflowchart TD or flowchart LR
Calls over timesequenceDiagram
State lifecyclestateDiagram-v2
Type relationshipsclassDiagram
Data entitieserDiagram
Schedulegantt
User experiencejourney
Hierarchymindmap
Chronologytimeline
Lightweight architecturearchitecture-beta or a flowchart

Load only the matching file under examples/ when syntax details are needed. Do not load all examples.

Authoring rules

  • Give every node a stable, simple identifier.
  • Quote human-readable labels when they contain punctuation.
  • Use one direction consistently; avoid unnecessary crossings.
  • Represent a decision with a diamond and label outgoing branches.
  • Keep sequence participants and messages explicit.
  • Avoid styling that depends on a single renderer unless the target platform is known.
  • Split an unreadable diagram instead of shrinking labels or adding excessive subgraphs.
  • Do not encode unsupported facts merely to make the diagram look complete.

Output

For inline delivery, return a fenced block:

```mermaid
flowchart LR
    A["Input"] --> B{"Valid?"}
    B -->|Yes| C["Process"]
    B -->|No| D["Reject"]
```

For file delivery, prefer docs/diagrams/<descriptive-name>.md unless the repository already has a diagram convention. Preserve existing files and ask before overwriting.

Validation checklist

  • Opening declaration matches the intended diagram type.
  • Identifiers are valid and unique.
  • Labels with punctuation are quoted.
  • All branches, participants, and relationships are connected as intended.
  • Fenced Markdown blocks are closed.
  • The diagram renders on the user's target platform when that renderer is available.

FAQ

What does the mermaid skill do?

Create or revise Mermaid diagrams that render inside Markdown, README files, GitHub, GitLab, wikis, and documentation sites. Use when the user explicitly requests Mermaid or needs a Markdown-native flowchart, sequence diagram, state diagram, class diagram, ER diagram, journey, Gantt chart, mind map, timeline, or lightweight architecture diagram. Prefer PlantUML for strict UML/C4 deliverables and ProcessOn only when editable hosted output is requested.

How do I install mermaid?

Run npx skills add https://github.com/full-stack-skills/document-skills --skill mermaid in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mermaid/ (personal) or .claude/skills/mermaid/ (project).

Which AI agents can use mermaid?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is mermaid safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains mermaid?

It is published by full-stack-skills in full-stack-skills/document-skills. It has 91 recorded installs.

More from full-stack-skills/document-skills

View all →

api-doc-generator

full-stack-skills/document-skills

Generate or update evidence-backed API documentation from OpenAPI specifications, framework routes, controllers, request/response models, validation rules, and tests. Use when the user explicitly asks for API or interface documentation, route inventory, endpoint reference, OpenAPI-derived docs, or synchronization between code and API docs. Supports OpenAPI-first projects and framework-specific discovery for Spring, FastAPI, NestJS, Express, and Gin; do not use for generic product documentation.

Backend & APIs87 installs

doc-coauthoring

full-stack-skills/document-skills

Collaboratively draft, revise, and reader-test substantial documentation such as proposals, RFCs, decision records, technical specifications, strategy documents, and cross-team plans. Use when the user needs help transferring context, shaping an argument, resolving gaps, iterating on an existing document, or validating whether a document works for readers. Use a more specialized document skill when the requested artifact is a product-doc suite, technical tutorial, or API reference.

Backend & APIs81 installs

full-stack-doc

full-stack-skills/document-skills

Scaffold, adapt, validate, and maintain example-rich full-stack product documentation: 10 product-level documents, 7 version documents, optional module PRD/Stitch/UI triplets, 5 delivery documents, and a detailed project README template family. Use when users ask to initialize a documentation repository, create product or version plans, write PRDs and architecture/UI documents, preserve and adapt detailed examples, audit document structure, or improve an existing product-docs tree, including Chinese requests such as 初始化文档、产品文档、写规划文档.

Docs & Writing80 installs

plantuml

full-stack-skills/document-skills

Open the skill to read its SKILL.md instructions.

76 installs

technical-blog-doc

full-stack-skills/document-skills

Create or revise evidence-backed technical tutorials, integration guides, deployment articles, engineering walkthroughs, and project documentation in Markdown. Use when the user asks for a technical blog post or tutorial that combines concepts, prerequisites, implementation, runnable commands, verification, troubleshooting, and sources. Do not use for a product-documentation suite or API-only reference.

Docs & Writing75 installs

processon-mindmap

full-stack-skills/document-skills

Design a ProcessOn-ready mind-map outline for ideas, requirements, knowledge systems, meeting notes, learning plans, or hierarchical analysis. Use when the user explicitly requests a ProcessOn mind map, editable mind map, or a hierarchical outline intended for ProcessOn. Do not trigger for ordinary diagrams, generic prose outlines, or Mermaid mind maps unless ProcessOn is requested.

Docs & Writing75 installs

Popular docs & writing skills

View category →

grill-with-docs

mattpocock/skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Docs & Writing1.2M installs

lark-markdown

open.feishu.cn

飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。

Docs & Writing778.7K installs

writing-beats

mattpocock/skills

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Docs & Writing490.7K installs

writing-shape

mattpocock/skills

Writing, exploit: shape raw material into an article, paragraph by paragraph.

Docs & Writing490.2K installs

writing-fragments

mattpocock/skills

Writing, explore: mine raw fragments, no structure yet.

Docs & Writing489.6K installs

writing-for-agents

mattpocock/skills

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Docs & Writing479.3K installs