--- name: format-diagram description: "Draw process flows, architecture views, stakeholder maps, org charts, timelines, matrices, mind maps and sequence/state/ER/gantt diagrams from Mermaid text. Two modes: BRANDED (the server-side `render_diagram` tool returns an auto-laid-out, brand-themed SVG/PNG for PPTX, DOCX, PDF or deck deliverables) and MARKDOWN (plain fenced Mermaid for a README, wiki or any Markdown host that renders it). Use when asked to draw, map or visualize a process, structure, workflow or relationship. Not for numeric data charts (use format-chart)." metadata: stromy-client-summary: "Draw a process, structure or relationship as an on-brand diagram for your documents." --- # Diagram: branded figures and plain Mermaid (MCP-hosted skill) This skill's full instructions are hosted on the `stromy-format` MCP server. Do not hardcode workflow logic locally — always fetch the live version from the MCP. ## Loading instructions 1. Read the main skill instructions: → call the `fs_read` tool on the `stromy-format` MCP with `path="skills/format-diagram/SKILL.md"`. **Read it to the end.** `fs_read` returns one page at a time. If the result's `next_offset_chars` is not null — or the returned text ends in a `<<< PARTIAL READ … >>>` block — the body is incomplete: call `fs_read` again with `offset_chars` set to that value and concatenate, repeating until it comes back null. Do **not** start work on a partial skill body. Hard rules and anti-patterns often sit in the final third, and a partial read fails silently — it looks like a complete skill. 2. Discover reference files (and any other skill assets), then read on demand: → call `fs_list` with `path="skills/format-diagram"` (and `path="skills/format-diagram/references"`), → call `fs_read` with `path="skills/format-diagram/references/"`. Follow the instructions returned by the MCP exactly. ## This MCP is the only correct path Produce this skill's output **only** by following the live SKILL.md fetched above and calling the `stromy-format` MCP's own tools. Do **not** substitute a local or identically-named base skill from elsewhere, and do **not** invent your own output path. A locally-produced or unbranded artifact is **wrong output, not a fallback** — it bypasses the server-side brand and quality gates.