メニュー
Convert markdown to portable, shareable HTML documents with syntax highlighting and optional tabbed navigation. Use when users say "publish", "make HTML", "make this shareable", "create a document for the team", or want to share output with non-technical audiences.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | publish |
| description | Convert markdown to portable, shareable HTML documents with syntax highlighting and optional tabbed navigation. Use when users say "publish", "make HTML", "make this shareable", "create a document for the team", or want to share output with non-technical audiences. |
Convert a markdown file to a self-contained HTML document:
node {pluginDir}/dist/publish/cli.js \
--input file.md \
--output file.html \
--template default \
--title "Document Title"
Or pipe markdown via stdin:
echo "# Title\n\nContent" | node {pluginDir}/dist/publish/cli.js --output file.html
| Flag | Description |
|---|---|
--input path | Input markdown file |
--output path | Output HTML file path (required) |
--template name | default, report, review, or briefing |
--title "text" | Override document title (default: first H1) |
--tabs | Force tabbed interface |
--no-tabs | Force single-page layout |
JSON to stdout:
{ "success": true, "outputPath": "/path/to/file.html", "title": "...", "template": "...", "tabbed": true, "sectionCount": 4, "wordCount": 1200 }
| Template | Best for | Tabs default |
|---|---|---|
default | General prose, summaries | Off |
report | Release reports, metrics, team stats | On (3+ sections) |
review | Code reviews, diff walkthroughs | On (3+ sections) |
briefing | Stakeholder summaries, larger font | Off |
Tabs activate automatically when the template defaults to tabs AND the document has 3+ H2 sections. Each H2 heading becomes a tab label. Override with --tabs or --no-tabs.
For print and no-JS contexts, all tab panels display as stacked sections.
When generating markdown that will be published:
Open the HTML in the default browser:
open file.html
Review codebase architecture for deepening opportunities — modules where the interface is nearly as complex as the implementation. Uses depth-as-leverage model and the deletion test. Use when the codebase feels tangled, after a burst of fast development, or when asked to review architecture.
Ultra-compressed communication. Drops filler, hedging, and pleasantries while keeping technical terms exact. ~75% token reduction. Use when user says "caveman", "caveman mode", "be terse", or "stop being chatty".
Structured debugging as a state machine: reproduce, minimize, hypothesize, instrument, fix, regression-test. Use when something is broken, a bug needs fixing, tests are failing unexpectedly, or behavior doesn't match expectations.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Test-driven development with vertical slices. Enforces behavior-focused tests through public interfaces, one red-green-refactor cycle at a time. Use when writing tests, adding test coverage, or building features test-first.
Generates publication-quality illustrations using a 5-agent pipeline inspired by PaperBanana (academic illustration framework). Orchestrates specialized agents: Retriever, Planner, Stylist, Visualizer, and Critic. Use when users need high-quality, iterative image generation with style consistency and quality review.