Mermaid renderer
Skill eugenelim/agent-ready-repo/packs/converters/.apm/skills/mermaid-renderer
The complete AI operating model for software teams — from first idea to production. Three peer-supervised loops (discovery → build → release) over a catalogue of curated packs: skills, subagents, and hooks, each installed in one line. It's npm for your coding agent. Any agent, any stack — Claude Code, Codex, Cursor, Copilot, Gemini, Kiro.
npx -y skills add eugenelim/agent-ready-repo --skill mermaid-rendererAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Extract ` ```mermaid ` fenced blocks from a Markdown file, render each one to a PNG (or SVG) via the Mermaid CLI (`mmdc`), and write a rewritten Markdown file alongside with each fence replaced by an image reference. Use when the user wants Mermaid diagrams baked into images for downstream tools that don't render Mermaid natively (Confluence, PDF, slides). The agent only invokes the script.
SKILL.md
4.9 KB, as published. Nobody here has run it
Mermaid Renderer
A thin wrapper around scripts/render_mermaid.py. The script walks a
Markdown file, extracts ```mermaid blocks, calls the Mermaid CLI
(mmdc) to render each to a PNG, and writes a rewritten Markdown file
where every fence is replaced by a standard Markdown image reference
pointing at the rendered file (e.g. mermaid-1.png).
Prerequisites
The renderer shells out to @mermaid-js/mermaid-cli. Install once:
npm install -g @mermaid-js/mermaid-cli
(Or npm install --save-dev @mermaid-js/mermaid-cli in a project that
ships its own node_modules/; the script finds mmdc on PATH.)
No Python deps beyond the standard library.
Instructions
You are not the renderer. The script is. Invoke it and report what landed where.
Step 1 — Verify mmdc is available
python scripts/render_mermaid.py --check
- Exit code 0 →
mmdcis onPATH, proceed. - Exit code 2 →
mmdcis not installed. Tell the user to runnpm install -g @mermaid-js/mermaid-clithemselves. Don't try to install it for them.
Step 2 — Render
python scripts/render_mermaid.py --input report.md --output-dir ./rendered [--format png|svg] [--theme default|forest|dark|neutral] [--background white|transparent|#hex] [--prefix diagram]
| Flag | Meaning |
|---|---|
--input PATH | Source Markdown file. Required. |
--output-dir DIR | Directory for rendered images and the rewritten Markdown. Default: ./mermaid-out. |
--format | png (default) or svg. |
--theme | default (default), forest, dark, neutral. |
--background | Background colour, e.g. white, transparent, #f0f0f0. Default: white. |
--prefix NAME | Output filename prefix. Default: mermaid. |
--width N | Output width in pixels (passes through to mmdc -w). |
--height N | Output height in pixels (passes through to mmdc -H). |
--check | Verify mmdc is on PATH; exit 0 or 2. |
--verbose | Debug logging. |
The script writes:
<output-dir>/<prefix>-1.<ext>,<prefix>-2.<ext>, … — one image per Mermaid block, numbered in document order.<output-dir>/<input-basename>.md— a rewritten copy of the input with each```mermaidfence replaced by a standard Markdown image reference pointing at the rendered file (e.g.``mermaid-1.png``for the first block).
The original input file is not modified.
stdout summary:
OUTPUT_DIR: /abs/path/to/rendered
REWRITTEN: /abs/path/to/rendered/report.md
DIAGRAMS: 3
Surface the rewritten path and the diagram count.
Step 3 — Composing with other skills
The rewritten Markdown plus the image files form a self-contained bundle you can feed to:
confluence-publisher --input <rewritten>.md --attach <prefix>-1.png --attach <prefix>-2.png …— image refs become<ac:image>macros on the Confluence side.markdown-to-html— the rendered images replace the live-CDN Mermaid renderer for fully-offline HTML output.- Any PDF or slide pipeline that takes Markdown + images.
Don't
- Don't write your own Mermaid renderer. Extend
mmdcinvocations in the script if a flag is missing. - Don't pre-process the Markdown by hand to strip the fences — the script does that.
- Don't fall back to a Mermaid Live Editor URL — that would leak the diagram source to a third party.
- Don't try to install
mmdcautomatically. Tell the user the one-line install command and stop. - Don't render to the input file's own directory by default — the
script writes to
--output-direxactly so the original stays untouched.
Edge cases
- No Mermaid blocks in the input. The script reports
DIAGRAMS: 0, copies the input to<output-dir>/<basename>.mdunchanged, and exits 0. - A block fails to render (syntax error,
mmdcnon-zero). The script keeps going, writes amermaid-N.error.txtnext to where the image would have gone, leaves the fence intact in the rewritten Markdown, and exits non-zero at the end with a count of failures. mmdcnot on PATH.--checkexits 2 with the install command. Don't shell out to find it elsewhere.- Theme name not in the list.
mmdcexits with the list of valid choices; the script surfaces that. Don't invent a fifth. - Trust model. Mermaid input is the user's own document. The
renderer runs
mmdcon whatever fences it finds; do not use this skill on Markdown from untrusted sources without a separate sanitization step.