Workflow Diagram logo

Workflow Diagram

Community
athola
workflow-diagram

Generates a Mermaid workflow diagram showing process steps, decisions, and state transitions. Use when documenting CI/CD pipelines or lifecycle processes.

Overview

Publisherathola
Repositoryclaude-night-market
Skill nameworkflow-diagram
Stars
343
Forks
37
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by athola on GitHub. Read the source before you install it.

Installation

Install the Workflow Diagram AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/athola/claude-night-market/tree/master/plugins/cartograph/skills/workflow-diagram
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/athola/claude-night-market.git /tmp/claude-night-market
mkdir -p .claude/skills
cp -r /tmp/claude-night-market/plugins/cartograph/skills/workflow-diagram .claude/skills/workflow-diagram
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Workflow Diagram in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Workflow Diagram on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Workflow Diagram is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Workflow Diagram

Generate a Mermaid flowchart showing process workflows, pipelines, or state machines from code or documentation.

When To Use

  • Visualizing CI/CD or deployment pipelines
  • Documenting multi-step development workflows
  • Mapping state machines or lifecycle processes
  • Answering "what steps happen when X runs?"

When NOT To Use

  • Data moving between components (use cartograph:data-flow)
  • Component structure (use cartograph:architecture-diagram)

Workflow

Step 1: Explore the Codebase

Dispatch the codebase explorer agent:

Agent(cartograph:codebase-explorer)
Prompt: Explore [scope] and return a structural model.
Focus on process steps, conditional logic, state
transitions, and pipeline stages for a workflow diagram.
Look for: Makefiles, CI configs, hook chains, command
sequences, and lifecycle methods.

Step 2: Generate Mermaid Syntax

Transform the structural model into a Mermaid flowchart with decision nodes and process steps.

Rules for workflow diagrams:

  • Use flowchart TD for sequential processes
  • Use flowchart LR for pipelines with parallel tracks
  • Use shapes to distinguish step types:
    • [Rectangle] for process steps
    • {Diamond} for decision points
    • ([Stadium]) for start/end states
    • [[Subroutine]] for sub-processes
    • ((Circle)) for join/sync points
  • Use -->|label| for transition conditions
  • Group parallel tracks into subgraphs
  • Color-code by outcome:
    • Default for happy path
    • Dotted (-.->) for error/fallback paths
    • Thick (==>) for critical path
  • Limit to 20 nodes maximum

Example output:

Step 3: Render via MCP

Call the Mermaid Chart MCP to render:

mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
  prompt: "Workflow diagram of [scope/process]"
  mermaidCode: [generated syntax]
  diagramType: "flowchart"
  clientName: "claude-code"

If rendering fails, fix syntax and retry (max 2 retries).

Step 4: Present Results

Show the rendered diagram with a brief description of the workflow stages and decision points (2-3 sentences).

Exit Criteria

  • Mermaid flowchart syntax generated containing at least one diamond {Decision} node representing a conditional branch
  • mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram called and returns without error (or retry attempted and result reported)
  • Error/fallback paths rendered as dotted arrows (-.->) distinct from happy-path arrows when error paths exist in the source
  • Node count is at most 20; if more steps exist, sub-processes are collapsed into [[Subroutine]] nodes
  • A 2-3 sentence description of workflow stages and decision points is shown alongside the diagram

Frequently asked questions

What does the Workflow Diagram AI skill do?

Generates a Mermaid workflow diagram showing process steps, decisions, and state transitions. Use when documenting CI/CD pipelines or lifecycle processes.

Why use Workflow Diagram on TypingMind?

Because you install it once and use it with any model. Workflow Diagram is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Workflow Diagram in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/athola/claude-night-market/tree/master/plugins/cartograph/skills/workflow-diagram. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Workflow Diagram?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Workflow Diagram?

As many as you like. As long as a model supports skills, you can use Workflow Diagram with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Workflow Diagram AI skill free?

Yes. It is published on GitHub by athola under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇