markdownlisted
Install: claude install-skill odere-pro/claude-wiki-pages-plugin
# LLM Wiki — Markdown export
Run a query against `vault/wiki/`, render the answer as **portable markdown**,
and write it to `vault/output/<slug>.md`. The result is plain
GitHub-flavored markdown — no `[[wikilinks]]`, no Dataview blocks, no
Obsidian callouts — suitable for pasting into a PR body, an email, or a
non-Obsidian doc tool.
This skill is the publish-side counterpart to `/claude-wiki-pages:query`.
Query stays in the conversation; markdown lands on disk.
## When to invoke
- The user explicitly asks to export, save, or render an answer as
markdown ("export this as markdown", "save to the output folder").
- The user invokes `/claude-wiki-pages:markdown` directly.
- An agent (`claude-wiki-pages-analyst-agent` Compile mode) chains this skill as a step.
Do NOT invoke when the user just wants an answer in the chat — use
`/claude-wiki-pages:query` for that.
Do NOT invoke for synthesis notes (cross-topic analyses live under
`wiki/_synthesis/`) — use `/claude-wiki-pages:synthesize`.
## Reading contract
Same order and scope as `/claude-wiki-pages:query`:
- `vault/CLAUDE.md` — the schema. Read first.
- `vault/wiki/index.md` — the top-level catalog.
- `vault/wiki/**/_index.md` — per-folder MOCs.
- `vault/wiki/<topic>/*.md` — candidate typed pages, plus pages reached by
following `[[wikilinks]]` (one hop) when the answer needs them.
- `vault/wiki/_synthesis/*.md` — prior syntheses, if relevant.
- `vault/wiki/_sources/*.md` — source summaries, when provenance matters.