Wiki Status
Audit an Obsidian wiki against source folders and manifest ledger to see ingest progress, delta, and graph insights before append or rebuild.
Overview
Wiki Status is an agent skill most often used in Operate (also Build docs) that reports ingest health, source-to-wiki delta, and optional graph insights for an Obsidian knowledge base.
Install
npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-statusWhat is this skill?
- Resolves vault paths via Config Resolution Protocol (.env, ~/.obsidian-wiki/config, or setup prompt)
- Reads .manifest.json at vault root as the ingest tracking ledger
- Delta view between sources and wiki content for append-vs-rebuild decisions
- Insights mode for hubs, cross-domain bridges, and orphan-adjacent structure via natural-language triggers
Adoption & trust: 2.2k installs on skills.sh; 1.8k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You do not know which source files are ingested, what changed since the last run, or whether to append or rebuild your wiki.
Who is it for?
Builders maintaining an Obsidian wiki synced from agent histories and a sources directory with .manifest.json tracking.
Skip if: Greenfield note-taking with no ingest manifest or users who only want one-off Markdown edits without a sources pipeline.
When should I use this skill?
User asks for wiki status, ingest progress, delta, dashboard, append vs rebuild guidance, or insights triggers such as wiki insights, central pages, hubs, and what's connected.
What do I get? / Deliverables
You get a manifest-backed status and delta summary (and optional hub insights) so you can choose append ingest, rebuild, or targeted fixes.
- Ingest status summary (ingested vs pending sources)
- Source-to-wiki delta report for append or rebuild decisions
- Optional insights report on hubs, bridges, and connectivity
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Operating a personal knowledge base is ongoing iteration; status checks answer what is stale, pending, or unhealthy in production use. Iterate fits maintenance decisions—append delta versus rebuild—driven by manifest and source comparison rather than first-time authoring alone.
Where it fits
Compare source folder changes to .manifest.json before scheduling an append ingest.
Run wiki insights to find hub pages and orphan-adjacent notes before reorganizing links.
Verify agent history paths ingested into the vault before publishing internal docs from Obsidian.
Survey what knowledge is already captured versus missing from recent Codex sessions.
How it compares
Audit and dashboard skill for an existing wiki pack—not a generic Obsidian theme or daily notes template.
Common Questions / FAQ
Who is wiki-status for?
Solo builders using the Obsidian Wiki skill pack who ingest Claude/Codex history and external sources into a vault and need health checks before maintenance runs.
When should I use wiki-status?
When you ask for status, delta, what's left to process, or wiki insights; in Operate iterate before append/rebuild, and in Build docs when validating knowledge-base completeness.
Is wiki-status safe to install?
It is designed to read config, manifest, and vault metadata; review filesystem scope in your agent policy and the Security Audits panel on this Prism page.
SKILL.md
READMESKILL.md - Wiki Status
# 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 1. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md` (walk up CWD for `.env` → `~/.obsidian-wiki/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. ```json { "version": 1, "last_updated": "2026-04-06T10:30:00Z", "sources": { "/absolute/path/to/file.md": { "ingested_at": "2026-04-06T10:30:00Z", "size_bytes": 4523, "modified_at": "2026-04-05T08:00:00Z", "source_type": "document", "project": null, "pages_created": ["concepts/transformers.md"], "pages_updated": ["entities/vaswani.md"] }, "~/.claude/projects/-Users-name-my-app/abc123.jsonl": { "ingested_at": "2026-04-06T11:00:00Z", "size_bytes": 128000, "modified_at": "2026-04-06T09:00:00Z", "source_type": "claude_conversation", "project": "my-app", "pages_created": ["entities/my-app.md"], "pages_updated": ["skills/react-debugging.md"] } }, "projects": { "my-app": { "source_path": "~/.claude/projects/-Users-name-my-app", "vault_path": "projects/my-app", "last_ingested": "2026-04-06T11:00:00Z", "conversations_ingested": 5, "conversations_total": 8, "memory_files_ingested": 3 } }, "stats": { "total_sources_ingested": 42, "total_pages": 87, "total_projects": 6, "last_full_rebuild": null } } ``` ## Step 1: Scan Current Sources Build an inventory of everything available to ingest right now: ### Documents (from `OBSIDIAN_SOURCES_DIR`) ``` Glob each directory in OBSIDIAN_SOURCES_DIR for all text files Record: path, size, modification time ``` ### Claude History (from `CLAUDE_HISTORY_PATH`) ``` Glob: ~/.claude/projects/*/ → project directories Glob: ~/.claude/projects/*/*.jsonl → conversation files Glob: ~/.claude/projects/*/memory/*.md → memory files Record: path, size, modification time, parent project ``` ### Codex History (from `CODEX_HISTORY_PATH`) ``` Glob: ~/.codex/session_index.jsonl → session inventory index Glob: ~/.codex/sessions/**/rollout-*.jsonl → session rollout transcripts Glob: ~/.codex/history.jsonl → optional local history log Glob: ~/.codex/archived_sessions/**/rollout-*.jsonl → archived rollouts (if user wants archive coverage) Record: path, size, modification time, inferred project from cwd when available ``` ### Any other sources the user has pointed at previously Check the manifest for source paths outside the standard directories. ## Step 2: Compute the Delta Compare current sources against the manifest. Classify each source file: | Status | M