How do I install the Mermaid Flowchart skill?

Run npx skillmds@latest add tuanloc1105/mermaid-flowchart in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mermaid Flowchart safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mermaid Flowchart?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mermaid Flowchart free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mermaid Flowchart?

tuanloc1105 (@tuanloc1105) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mermaid Flowchart by tuanloc1105 — Agent Skill

Name: Mermaid Flowchart
Author: tuanloc1105

Mermaid Flowchart

Create or edit a technical workflow/flowchart from session context, natural-language processes, code paths, or Mermaid flowchart source. This is the permanent flowchart-only compatibility alias for technical-diagrams; do not use it for sequence, state, data-flow, or other diagram families.

tuanloc1105 Updated Sep 21, 2026

File contents

Mermaid Flowchart Compatibility Alias

Preserve the established flowchart invocation while using technical-diagrams as the only authoring, validation, rendering, delivery, and visual-QA engine. This alias is permanent and should route quietly without migration warnings.

Route the request

Resolve the target from the current request, then relevant session context, then named files or code. Read references/context-extraction.md when the request depends on earlier discussion or repository evidence.
Keep this alias flowchart-only. Route an ordered process, decision tree, runbook, or CI/CD flow to the workflow family. Route a component/service handoff map to architecture only when the nodes represent system parts rather than process steps.
Preserve stable IDs, exact domain terms, labeled branches, loops, ownership boundaries, and exception paths. Use references/flowchart-style-guide.md for legacy intent normalization.
Follow technical-diagrams/SKILL.md from its artifact-first authoring step. Do not invoke another renderer or validator from this alias.

Mermaid input

When the request includes Mermaid flowchart or graph source, translate it through the canonical importer:

node ../technical-diagrams/bin/technical-diagrams.mjs import-mermaid input.mmd candidate.json --json

Add --target architecture only for a component map. Then validate and deliver the typed IR with the same technical-diagrams CLI. Mermaid style directives are not canonical and must not create a second rendering path.

Artifact compatibility

Honor an explicit destination. Otherwise use the destination rules from technical-diagrams; during $discuss, keep artifacts under ./discussion/.
The final artifact is the checked standalone HTML produced by technical-diagrams. If the user explicitly requests normalized Mermaid source too, preserve it as an auxiliary .mmd input, not as the rendered source of truth.
Return the artifact path, chosen family, validation/delivery receipt, and truthful visual-review status exactly as required by technical-diagrams.

---name: mermaid-flowchartdescription: Create or edit a technical workflow/flowchart from session context, natural-language processes, code paths, or Mermaid flowchart source. This is the permanent flowchart-only compatibility alias for technical-diagrams; do not use it for sequence, state, data-flow, or other diagram families.---# Mermaid Flowchart Compatibility AliasPreserve the established flowchart invocation while using `technical-diagrams`as the only authoring, validation, rendering, delivery, and visual-QA engine.This alias is permanent and should route quietly without migration warnings.## Route the request1. Resolve the target from the current request, then relevant session context, then named files or code. Read [references/context-extraction.md](references/context-extraction.md) when the request depends on earlier discussion or repository evidence.2. Keep this alias flowchart-only. Route an ordered process, decision tree, runbook, or CI/CD flow to the `workflow` family. Route a component/service handoff map to `architecture` only when the nodes represent system parts rather than process steps.3. Preserve stable IDs, exact domain terms, labeled branches, loops, ownership boundaries, and exception paths. Use [references/flowchart-style-guide.md](references/flowchart-style-guide.md) for legacy intent normalization.4. Follow `technical-diagrams/SKILL.md` from its artifact-first authoring step. Do not invoke another renderer or validator from this alias.## Mermaid inputWhen the request includes Mermaid `flowchart` or `graph` source, translate itthrough the canonical importer:```bashnode ../technical-diagrams/bin/technical-diagrams.mjs import-mermaid input.mmd candidate.json --json```Add `--target architecture` only for a component map. Then validate and deliverthe typed IR with the same `technical-diagrams` CLI. Mermaid style directivesare not canonical and must not create a second rendering path.## Artifact compatibility- Honor an explicit destination. Otherwise use the destination rules from `technical-diagrams`; during `$discuss`, keep artifacts under `./discussion/`.- The final artifact is the checked standalone HTML produced by `technical-diagrams`. If the user explicitly requests normalized Mermaid source too, preserve it as an auxiliary `.mmd` input, not as the rendered source of truth.- Return the artifact path, chosen family, validation/delivery receipt, and truthful visual-review status exactly as required by `technical-diagrams`.

Frequently asked questions