wiki-rebuild — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited wiki-rebuild (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are performing a destructive operation on the wiki. Always archive first, always confirm with the user before proceeding.
llm-wiki/SKILL.md (walk up CWD for .env → ~/.obsidian-wiki/config → prompt setup). This gives OBSIDIAN_VAULT_PATH and optional QMD settings such as QMD_WIKI_COLLECTION.manifest.json to understand current stateArchives live at $OBSIDIAN_VAULT_PATH/_archives/. Each archive is a timestamped directory containing a full copy of the wiki state at that point.
$OBSIDIAN_VAULT_PATH/
├── _archives/
│ ├── 2026-04-01T10-30-00Z/
│ │ ├── archive-meta.json
│ │ ├── concepts/
│ │ ├── entities/
│ │ ├── skills/
│ │ ├── references/
│ │ ├── synthesis/
│ │ ├── journal/
│ │ ├── projects/
│ │ ├── index.md
│ │ ├── log.md
│ │ └── .manifest.json
│ └── 2026-03-15T08-00-00Z/
│ └── ...
├── concepts/ ← live wiki
├── entities/
└── ...{
"archived_at": "2026-04-06T10:30:00Z",
"reason": "rebuild",
"total_pages": 87,
"total_sources": 42,
"total_projects": 6,
"vault_path": "/Users/name/Knowledge",
"manifest_snapshot": ".manifest.json"
}When the user wants to snapshot the current state without rebuilding.
_archives/YYYY-MM-DDTHH-MM-SSZ/index.md, log.md, .manifest.json, and projects/ into the archivearchive-meta.json with reason "snapshot"log.md: - [TIMESTAMP] ARCHIVE reason="snapshot" pages=87 destination="_archives/2026-04-06T10-30-00Z"log.md is indexed and QMD_WIKI_COLLECTION is configured (see "QMD Refresh After Live Wiki Changes").When the user wants to start fresh. This is the full sequence:
Same as Mode 1 above, but with reason "rebuild".
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).
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 historycodex-history-ingest — to reprocess Codex session historywiki-ingest — to reprocess documents and any other raw dataEach 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.
Append to log.md:
- [TIMESTAMP] REBUILD archived_to="_archives/2026-04-06T10-30-00Z" previous_pages=87Refresh 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.
When the user wants to go back to a previous state.
Read _archives/ directory. For each archive, read archive-meta.json and present:
## Available Archives
| Date | Reason | Pages | Sources |
|---|---|---|---|
| 2026-04-06 10:30 | rebuild | 87 | 42 |
| 2026-03-15 08:00 | snapshot | 65 | 31 |Ask the user which archive they want. Warn them that restoring will overwrite the current live wiki.
Before restoring, archive the current state (reason: "pre-restore") so nothing is lost.
index.md, log.md, and .manifest.json from the archivelog.md: - [TIMESTAMP] RESTORE from="_archives/2026-03-15T08-00-00Z" pages_restored=65Refresh 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 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} updateIf the output says new hashes need vectors, or if restore replaced live pages and embeddings may be stale, run:
${QMD_CLI:-qmd} embedVerify 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 5Record QMD refresh in the final report as one of:
QMD refreshed: update + embed + verifiedQMD refreshed: update only + verifiedQMD skipped: QMD_WIKI_COLLECTION unsetQMD skipped: archive-only live content unchangedQMD skipped: qmd CLI unavailableQMD failed: <short error summary>~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.