Download .skills/wiki-rebuild/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does wiki-rebuild live?
The publisher keeps it at https://github.com/Ar9av/obsidian-wiki.
Which agents can use wiki-rebuild?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
>
name: wiki-rebuild
description: >
Archive and rebuild wiki knowledge from source, or restore a prior archive. Use for full restart/recovery when incremental repair is inappropriate; this is broader and more destructive than ordinary update or lint.
Wiki Rebuild — Archive, Rebuild, Restore
You are performing a destructive operation on the wiki. Always archive first, always confirm with the user before proceeding.
Before You Start
Resolve config — follow the Config Resolution Protocol in llm-wiki/SKILL.md (inline @name override → walk up CWD for .env → global config → prompt setup). This gives OBSIDIAN_VAULT_PATH and optional QMD settings such as QMD_WIKI_COLLECTION
Read .manifest.json to understand current state
Confirm the user's intent. This skill supports three modes:
Archive only — snapshot current wiki, no rebuild
Archive + Rebuild — snapshot, then reprocess all sources from scratch
Restore — bring back a previous archive
The Archive System
Archives live at $OBSIDIAN_VAULT_PATH/_archives/. Each archive is a timestamped directory containing a full copy of the wiki state at that point.
Optionally refresh QMD if log.md is indexed and QMD_WIKI_COLLECTION is configured (see "QMD Refresh After Live Wiki Changes").
Report: "Archived 87 pages. Current wiki is untouched."
Mode 2: Archive + Rebuild
When the user wants to start fresh. This is the full sequence:
Step 1: Archive current state
Same as Mode 1 above, but with reason "rebuild".
Step 2: Clear live wiki
Remove all content from the category directories (concepts/, entities/, skills/, etc.) and the projects/ directory. Keep:
_archives/ (obviously)
.obsidian/ (Obsidian config)
.env (if present in vault)
Reset index.md to the empty template. Reset log.md with just the rebuild entry. Delete .manifest.json (it'll be recreated during ingest).
Step 3: Rebuild
Tell the user the vault is cleared and ready for a full re-ingest. They can now run:
wiki-status — to see all sources as "new"
claude-history-ingest — to reprocess Claude history
codex-history-ingest — to reprocess Codex session history
wiki-ingest — to reprocess documents and any other raw data
Each of these will rebuild the manifest as they go.
Important: Don't run the ingest yourself automatically. The user should choose what to re-ingest and in what order. Some sources may no longer be relevant.
Refresh QMD after clearing and logging the live wiki (see "QMD Refresh After Live Wiki Changes"), then report that the vault is ready for selected re-ingest skills.
Mode 3: Restore from Archive
When the user wants to go back to a previous state.
Step 1: List available archives
Read _archives/ directory. For each archive, read archive-meta.json and present:
Refresh QMD after restore (see "QMD Refresh After Live Wiki Changes"), then tell the user what was restored and suggest running wiki-lint to check for any issues with the restored state.
QMD Refresh After Live Wiki Changes
QMD is a search index, not the source of truth. If QMD refresh fails, do not roll back archive, rebuild, or restore work; report the failure and leave the markdown vault intact.
GUARD: If $QMD_WIKI_COLLECTION is empty or unset, skip this step.
When to run:
Mode
Refresh QMD?
Reason
Archive only
Optional
Live wiki content is unchanged except log.md; refresh if log.md is indexed and QMD is configured.
Archive + Rebuild
Required after clearing live wiki
QMD must forget deleted pages or it will return stale search results. Later ingest skills will refresh again as sources are reprocessed.
Restore
Required after restore
The live wiki was replaced with archive content, so QMD must match the restored state.
This refresh currently requires the local QMD CLI. Use $QMD_CLI if set; otherwise use qmd. If the CLI is unavailable, report QMD skipped: qmd CLI unavailable.
For CLI refresh:
${QMD_CLI:-qmd} update
If the output says new hashes need vectors, or if restore replaced live pages and embeddings may be stale, run:
${QMD_CLI:-qmd} embed
Verify the wiki collection reflects the operation:
${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION"
For restore, also verify one restored page if the archive has a known page path:
${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<restored-page>.md" -l 5
Record QMD refresh in the final report as one of:
QMD refreshed: update + embed + verified
QMD refreshed: update only + verified
QMD skipped: QMD_WIKI_COLLECTION unset
QMD skipped: archive-only live content unchanged
QMD skipped: qmd CLI unavailable
QMD failed: <short error summary>
Safety Rules
Always archive before destructive operations. No exceptions.
Always confirm with the user before clearing the live wiki.
Never delete archives unless the user explicitly asks. Archives are cheap insurance.
The .obsidian/ directory is sacred. Never touch it during archive/rebuild/restore — it contains the user's Obsidian settings, plugins, and themes.
If something goes wrong mid-rebuild, the archive is there. Tell the user they can restore.
How do I install wiki-rebuild?
Download .skills/wiki-rebuild/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does wiki-rebuild live?
The publisher keeps it at https://github.com/Ar9av/obsidian-wiki.
Which agents can use wiki-rebuild?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.