orchestrator-wikilisted
Install: claude install-skill ShiJianXi/molt
# Orchestrator wiki
One **wiki** per long-running orchestrator. It belongs to that one session: only it reads the wiki,
only it writes to it, and no other session, child, thread or file ever gets the link. It holds what
the orchestrator would otherwise lose on `/compact` or `/clear`, and nothing else. Over weeks it
stays small: what falls off the pages goes to an archive inside the same wiki (step 8), and the
orchestrator reviews its own friction now and then to tidy up and learn rules (step 9).
The page is written from `wiki-page.md` in this skill's directory; the data lives in the
artifact's database, so writes are database writes, never republishes. The plugin ships no hooks, so nothing reloads the
wiki for you: after `/compact` or `/clear` the user says "resume my <domain> orchestrator" (or a
compacted summary names the wiki) and step 4 runs.
## Facts that shape the procedure (November 2026, Claude Code 2.1.31x)
- `/compact` and `/clear` run as soon as they are typed. No model turn comes before them, so
nothing can be saved "just before". The wiki is written as facts happen (step 3), so it is
current whenever either runs.
- `/compact` keeps Claude Code's own session id. `/clear` starts a new one (`SessionEnd` with reason
`clear`, then `SessionStart` with source `clear`). Both stay in the same Claude process.
- After `/compact` the summary usually still names the domain and the wiki link; after `/clear`
nothing does. Either way, the user's "resume my <domain> o