# Wiki Status

Report wiki ingestion/completeness state, pending source delta, structural insights, or...

- Repository: https://github.com/Ar9av/obsidian-wiki (3650 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Ar9av/obsidian-wiki --skill wiki-status -g -a claude-code -y`
Codex: `npx skills add Ar9av/obsidian-wiki --skill wiki-status -g -a codex -y`
Cursor: `npx skills add Ar9av/obsidian-wiki --skill wiki-status -g -a cursor -y`
Gemini CLI: `npx skills add Ar9av/obsidian-wiki --skill wiki-status -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Ar9av/obsidian-wiki`

## Description

Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Wiki Status, Audit & Delta

You are computing the current state of the wiki: what's been ingested, what's new since last ingest, and what the delta looks like. This helps the user decide whether to append (ingest the delta) or rebuild (archive and reprocess everything).

## Before You Start

**Writing profile:** Before drafting or rewriting natural-language Markdown, read and apply the `Writing Profile Resolution` section in `llm-wiki/SKILL.md`. Framework schema, provenance, safety, and operation-specific requirements take precedence.
Apply `WRITING.md` preferences only to generated `_insights.md` prose; keep the analyser snapshot verbatim.

1. **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`, `OBSIDIAN_SOURCES_DIR`, `CLAUDE_HISTORY_PATH`, and `CODEX_HISTORY_PATH`.
2. Read `.manifest.json` at the vault root, this is the ingest tracking ledger

## The Manifest

The manifest lives at `$OBSIDIAN_VAULT_PATH/.manifest.json`. It tracks every source file that has been ingested. If it doesn't exist, this is a fresh vault with nothing ingested.

> **Source keys are portable, never bare absolute paths.** The canonical key is vault-relative for in-vault sources (`Raw/database/x.pdf`), `~`-relative for sources under `$HOME` (`~/.claude/projects/.../abc.jsonl`), or a pseudo-key (`repo:`/`url:`/`agent:`) for sources with no portable path form. Never mix forms, the same file would be tracked twice and re-ingested. See `llm-wiki/SKILL.md` → `.manifest.json` (Source key contract v2). Convert a legacy absolute-key manifest with `scripts/manifest.py migrate <vault>`.

The rest: https://github.com/Ar9av/obsidian-wiki/blob/HEAD/.skills/wiki-status/SKILL.md