Skip to content
Skills Library
Programming · Building & coding

flow

/flow

Draw and iterate on Mermaid diagrams the user watches live in the Flow viewer, and handle their node comments. Use when the user asks for a diagram, flowchart, architecture sketch, sequence, state machine, ER diagram, or says "flow", or when Flow feedback arrives.

Repository
flow ↗
Licence
MIT
Last repository change
06.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Draw and iterate on Mermaid diagrams the user watches live in the Flow viewer, and handle their node comments. Use when the user asks for a diagram, flowchart, architecture sketch, sequence, state machine, ER diagram, or says "flow", or when Flow feedback arrives.

Triggers from the description

flow
Original author description

Draw and iterate on Mermaid diagrams the user watches live in the Flow viewer, and handle their node comments. Use when the user asks for a diagram, flowchart, architecture sketch, sequence, state machine, ER diagram, or says "flow", or when Flow feedback arrives.

How it works

  1. Tools
  2. Workflow
  3. Never clobber the user
  4. Style
  5. Errors
Original SKILL.md headings · 46 lines, 648 words
SKILL.md preview
---
name: flow
description: Draw and iterate on Mermaid diagrams the user watches live in the Flow viewer, and handle their node comments. Use when the user asks for a diagram, flowchart, architecture sketch, sequence, state machine, ER diagram, or says "flow", or when Flow feedback arrives.
---

# Flow

Flow is a live canvas: you write Mermaid through the Flow tools, the user watches each revision render at <http://127.0.0.1:4729>, clicks nodes to comment, and can edit the source themselves. Comments are drafts until the user presses **Send to agent**, so feedback arrives as one complete review, never half-written.

## Tools

| Tool | Use it to |
|---|---|
| `create_diagram {title, source, note?}` | Start a diagram. Returns its `id` and viewer URL. |
| `update_diagram {id, source, note?, title?}` | Save a new revision. Always the **full** source, never a patch. |
| `list_diagrams` | Find existing diagrams (check before creating a duplicate). |
| `get_diagram {id, revision?}` | Read the current (or an old) source and history. |
| `get_feedback {id, includeResolved?}` | Read open comments, each anchored to a node id. |
| `wait_for_feedback {id?, timeoutSec?}` | Block until the user sends a review (default 50s, max 600s). |
| `resolve_feedback {id, feedbackId, reply?}` | Close a comment after a revision fixes it. |

## Workflow

1. **Reuse first.** If the user refers to an existing diagram, `list_diagrams` then `get_diagram`. Otherwise `create_diagram`.
2. **Show, don't paste.** Put Mermaid in the tool, not the chat. In chat, give the viewer URL and a one-line summary.
3. **Revise with intent.** Every `update_diagram` gets a short `note` saying what changed ("split API into gateway + worker"). The viewer highlights the diff on its own.
4. **Close the loop on feedback.** For each open item: change the diagram, `update_diagram`, then `resolve_feedback` with a short reply. Resolve only what the revision actually fixed; reply to explain if you chose not to change something.
5. **Hand off to the viewer and wait.** In Claude Code with the Flow plugin, a hook does this for you: after you draw, it holds until the user sends a review (it comes back as hook feedback) or presses **Looks good** (you're told to carry on). Then don't call `wait_for_feedback`. In other clients (not pi), wait yourself: after `create_diagram` or `update_diagram`, call `wait_for_feedback {id, timeoutSec: 600}` so the user can comment right away without prompting you. When it returns feedback, address it (step 4) and wait again. When it times out with no feedback, stop waiting and end your turn, saying the user can comment in the viewer anytime. Skip waiting only if the user said they don't want to review ("just draw it"). With the Claude Code plugin's hooks, comments left later still reach you on the next prompt or before you stop.

In pi, feedback arrives on its own as a `flow-feedback` message; just address it (step 4). `/flow [id]` opens the viewer.

## Never clobber the user

The user can edit in the viewer. If `update_diagram` is refused with "Not saved: revision rN was written by …", it returns the current source: **apply your change on top of that source and retry**. Never re-send your old version. Feedback of kind `edit` also ships the current source; treat their edit as the new baseline and only tidy around it.

## Style

- One node per component: short bold title, optional subtitle on a second line: `api["API Gateway<br/>auth, rate limit"]`.
- Stable, meaningful node ids (`api`, `queue`, `db`), not `A`, `B`, `C`. Comments are anchored to ids, so keep ids stable across revisions.
- No colors, `classDef`, or `style` lines; the viewer themes and highlights changes itself.
- Pick the right diagram type: `flowchart` for architecture/process, `sequenceDiagram` for interactions over time, `stateDiagram-v2` for lifecycles, `erDiagram` for data models.
- Keep it readable: roughly 5–20 nodes. Use `subgraph` to group; split into a second diagram rather than cramming.
- Quote labels containing punctuation: `n["Retry (3x)"]`.

## Errors

- "Mermaid did not parse": nothing was saved. Fix the syntax from the parser error and call again.
- "Source is identical": you sent no change; nothing to do.
- "No diagram with id": call `list_diagrams`.

Versions

RepositoryScoreLicence
This page · rawnly/flow90MIT
lifecycle-innovations-limited/claude-ops100MIT
manhquydev/flow-skill100MIT
simota/agent-skills100MIT
justinedevs/meta-architect100MIT
cofin/flow100Apache-2.0
panayiotism/claude-harness100MIT
Panza-Labs/floorboss96Apache-2.0
ohdearquant/lionagi95Apache-2.0

Database snapshot: 13.11.2026 · package version 9efedab62551 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100diagrams
    Use when creating technical diagrams as code. Covers Mermaid for architecture, sequence, and flow diagrams, choosing the right diagram type, and keeping diagrams accurate as the system changes. Trigger on "draw an architecture diagram", "make a mermaid sequence diagram",…
  • 100mermaid-diagramming
    Create Mermaid diagrams using the project's blue-gray theme. Use whenever the user asks to draw a diagram, create a flowchart, visualize a process, document architecture, or add any Mermaid diagram to a markdown file. Trigger on phrases like "draw a diagram", "create a…
  • 100visual-communication
    Communicate systems and flows visually using Mermaid (flowchart, sequence, state, ER, class), the C4 model, and diagram-as-code. Use when the user asks to draw a flow, sequence diagram, state machine, ER diagram, C4 model, architecture diagram, or wants Mermaid code for a…
  • 90doncheli-diagram
    Auto-generate Mermaid or C4 diagrams from code analysis. Activate when user mentions "diagram", "mermaid", "architecture diagram", "C4", "class diagram", "sequence diagram", "ERD", "flowchart", "visualize code".
  • 100mermaid-diagrams
    Create or fix Mermaid diagrams in Markdown. Use for requested flowcharts, sequence diagrams, ER diagrams, state machines, or system diagrams when Mermaid is the output format; not every visualization or explanation.
  • 100docs-mermaid
    Generate precise diagrams (flowchart, sequence, state, ER, class, gantt, gitGraph) using Mermaid for nexus-agents docs. Use when the user wants to "diagram this", "show how X works", "draw the flow", or asks for a flowchart / sequence / state diagram. Cross-references docs-chart…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.