iWiki MD Publisher

What It Solves

Many teams already have HTML reports, product notes, CLI docs, or weekly digests, but pasting them into iWiki often produces plain Markdown: loose structure, brittle styles, separated code blocks, or inline code split across lines. iWiki MD Publisher focuses on turning user-visible content into a stable, publishable iWiki MD page rather than rewriting the source as new documentation. It defaults to report or portal-style pages, preserves the original copy, and shapes layout, cards, sections, and code display around iWiki compatibility constraints.

How It Works

The skill treats environment readiness as a prerequisite: it expects a PAT token, an iwiki-cli command available in a new login shell, and persistent PATH and IWIKI_TOKEN. If these are missing, it stops content generation and handles setup first. During conversion, it follows a deliberate workflow:
- Extracts sections, headings, body copy, links, and command snippets from source HTML or MD, not DOM structure.
- Checks the target page with iwiki-cli metadata, then retrieves the live content with iwiki-cli get before updating existing pages.
- Chooses a template variant from general portal, product/CLI, feature, help, or digest families instead of building each page from scratch.
- Selects one code-display mode per section: native copy with a fenced code block, or integrated visuals with conservative inline HTML panels.
- Publishes using safe primitives such as div, span, a, strong, and simple flex layouts, avoiding JavaScript, SVG, complex semantic tags, and advanced CSS.

Boundaries

It is suited to reformatting existing content into iWiki pages, not inventing new explanations, training copy, or marketing language. If the target page type is incompatible, the skill prefers creating a new MD page under the same parent rather than force-editing the old page. If CLI execution is blocked by a runtime environment issue, the output explicitly distinguishes environment blocking from content conversion failure, and recommends completing runtime upgrade, setup, and post-publish validation.