/SKILL.md
Render Mermaid diagrams into high-resolution PNG with sharp text (non-upscaled). Use when users ask to convert Mermaid code to PNG, request higher resolution, complain about blurry output, report missing text after SVG/PNG conversion, or need batch export for many Mermaid files.
npx skillsauth add allenyllee/mermaid-hq-png-export-skill mermaid-hq-png-exportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
python3 scripts/bootstrap_renderer_env.py
.mmd file.mmdc first, then kroki-local.kroki only when the user explicitly asks for Kroki output or Kroki compatibility.kroki, tell the user that remote PNG size is fixed and --scale will not change it.scripts/render_mermaid_png.py to render PNG natively from SVG.Use this command:
python3 scripts/render_mermaid_png.py \
--input /abs/path/diagram.mmd \
--output /abs/path/diagram-4x.png \
--scale 4
Batch mode:
python3 scripts/render_mermaid_png.py \
--batch-dir /abs/path/mermaid-files \
--output-dir /abs/path/png-output \
--pattern '*.mmd' \
--recursive \
--scale 4
mmdc for PNG output so flowchart labels are preserved.kroki-local, a local CLI/backend that targets Kroki-like Mermaid output.~/.local/mermaid-hq-png-export.auto fallback order is mmdc -> kroki-local -> kroki.mmdc or kroki-local; do not choose remote kroki unless the user specifically wants Kroki output.flowchart.htmlLabels=false by default; it breaks HTML-styled labels in tested block-beta cases.mmdc: no preinstalled mmdc required (script auto-installs).
mmdc.cmd and other Windows-specific executable names automatically.kroki-local: prefer local Chromium/Chrome, but bundled browser fallback is supported.
puppeteer-core.puppeteer and use its bundled browser.kroki fallback/path: curl and network access to https://kroki.io.
kroki path fetches PNG directly from remote Kroki.--keep-svg is requested, the renderer fetches remote SVG separately and saves it locally.--scale does not change remote Kroki PNG size; the renderer warns when backend=kroki is used with a scale other than 1.curl and tar are needed if Node.js must be downloaded automatically.scripts/bootstrap_renderer_env.py installs the expected local toolchain up front and verifies the installed versions.kroki-local packages are installed locally under ~/.local/mermaid-hq-png-export/kroki-mermaid-local-cli.kroki-local pins Mermaid 11.12.3, and regression tests verify the installed version matches.kroki-local is using either the expected puppeteer-core version or the expected puppeteer version.Run regression tests from the skill root:
python3 tests/run_regression_tests.py
Expected behavior:
mmdc_flowchart_text: PASSkroki_flowchart_text: PASSkroki_local_flowchart_text: PASSkroki_local_block_beta_geometry: PASSmmdc in restricted environments, run outside sandbox or with compatible Chromium flags.backend=kroki-local cannot start, set MERMAID_SKILL_CHROME to your Chromium/Chrome path.npm.ps1; the renderer prefers npm.cmd automatically, so no execution-policy change should be required.mmdc install fails and Kroki is unavailable, install Node.js + @mermaid-js/mermaid-cli manually.<text> nodes, not only <foreignObject>.--scale.kroki-local keeps a Kroki-style Mermaid SVG path, but PNG output uses browser screenshot instead of ffmpeg.foreignObject.flowchart and block-beta.kroki-local Mermaid is pinned to 11.12.3 because it stays closer to current Kroki layout than 11.13.0 in the tested block-beta case.development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.