okhp3-mermaid-publish

Topics in the source

• okhp3-mermaid-publish
• Local Render
• Execution contract
• MCP Publish (Mermaid Chart)
• Output Format Selection
• Privacy
• Scope
• Validation

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 The output layer. Runs after core's Gate 1-3 validation. Use references/render-pipeline.sh [output.png] [puppeteer-config.json]. The optional third argument passes a local Puppeteer config to the CLI; leave it out for normal rendering. The script: Checks for Node.js/npx and gives a clear, actionable error if missing - it does NOT fail silently or produce a confusing mmdc stack trace as the only signal Reads the exact @mermaid-js/mermaid-cli version from this package's package.json, using a matching local install when present or downloading that version with npx --package Never deletes the input .mmd or the output render. This directly addresses a defect found in mgranberry's community skill, which instructs deletion of "temporary" output after user approval - the rendered file is the deliverable, not scratch space If the script reports mmdc syntax errors, return to okhp3-mermaid-core Gate 1 - do not attempt to patch syntax here, this skill only renders. Confirm the requested format and destination before running a publish step. Prefer the local pipeline, preserve source and rendered artifacts, and report the actual path or link

This is an excerpt. Refer to the complete source and its current requirements.