Mc Wiki Promote

Wiki Promote

A bundled MulmoClaude preset skill (mc- prefix = launcher-managed; do not edit this file in the workspace, it is overwritten on every server boot).

This is the query→page return-loop of the LLM-Wiki pattern (Karpathy's gist: "ask questions against wiki pages; file valuable answers back as new pages"). Where mc-wiki-ingest (Phase A) starts from an external source, this one starts from a Q&A in the current chat: a question the user just asked plus the assistant's just-given answer that's worth keeping. Writes to data/wiki/.

Sister presets:

• mc-wiki-health-check (D, structural lint, scheduled, read-only)
• mc-wiki-deep-lint (B, LLM lint, on-demand, read-only)
• mc-wiki-ingest (A, source-driven ingest, writes)
• mc-wiki-promote (C, this one — chat-derived promote, writes)

Inputs

Reads from the current chat session — no file path / pasted text needed. The capture unit is:

• the assistant turn the user is promoting (their previous message in the case where the user invokes this skill right after a useful answer — i.e. the answer just spoken)
• the immediately prior user turn (the question that elicited it)

That's the Q&A pair (per #1528 Q2). If the prior user turn isn't a question — for example the user said "actually, also save this" after the assistant's answer — pair the assistant turn with the most recent user turn that does look like a question. If no usable question can be found, ask the user to restate the topic in one line and use that as the synthesised question.

Do NOT crawl earlier turns, summaries, or other sessions. The capture unit is the local Q&A pair only (v1 scope, #1528 Q2.b).

What to do (in order)

1. Propose slug + new-or-append + draft

In the next assistant turn after the user's promote request, output a structured proposal (do not write to disk yet):

**Proposed wiki promotion:**
- target: NEW `pages/<slug>.md`     # or: APPEND `pages/<existing-slug>.md` (## Promoted YYYY-MM-DD)
- slug: `<slug>`
- title: <H1 title — display>
- draft body (markdown):

  <draft markdown body — see Q5 / Q6 below for what to include>

How to pick the target:

• Read data/wiki/index.md to see existing slug/category map.
• Read manageWiki.graph if helpful (#1520) to see what pages cluster near this topic.
• If a clearly-matching existing page exists → propose APPEND with a new ## Promoted YYYY-MM-DD section (never silent overwrite, consistent with mc-wiki-ingest idempotency rule, #1527 Q5).
• Otherwise → propose NEW with a fresh slug derived from the Q&A topic (lowercase kebab-case ASCII; transliterate if non-ASCII).

2. Wait for user confirmation

Stop after the proposal. The user will either:

• confirm ("OK / commit / 書いて / yes"): proceed to step 3.
• request edits ("change the slug to X / shorten / drop the example / use Y page instead"): regenerate the proposal with the requested changes and re-emit. Loop until confirm.
• cancel ("never mind / cancel"): stop without writing.

Never write to disk on the same turn as the proposal. The proposal turn is the preview gate (#1528 Q6). At least one explicit confirm turn must intervene before any manageWiki write action.

3. Write (only after explicit confirm)

Once the user confirms:

• NEW page: write data/wiki/pages/<slug>.md with the draft body. Body shape: H1 title; one short overview paragraph; the Q&A rendered as a focused "Q: … / A: …" block or as a clean prose digest (whichever the proposal landed on); provenance markers per step 4.
• APPEND: read the target page, append a new section ## Promoted YYYY-MM-DD at the bottom containing the draft. Do not rewrite the existing body. (Same idempotency contract as mc-wiki-ingest, #1527 Q5.)

4. Provenance markers

Each generated bullet in the page body MUST end with an HTML comment:

- The model X was released in 2026-Q1. <!-- promoted: <slug> 2026-MM-DD -->

• promoted: (not source: — distinguishes Phase C origin from Phase A ingest origin)
• <slug> is the new (or appended-to) page's slug
• YYYY-MM-DD is today's date — Phase B mc-wiki-deep-lint's stale-claims detection uses this