SkillAgentSearch skills...

wiki-status

Report wiki ingestion/completeness state, pending source delta, structural insights, maintenance equilibrium, or what each recurring job costs.

Install / Use

npx skills add Ar9av/obsidian-wiki --skill wiki-status

Installs into whichever agent you are using.

About this skill
๐Ÿ“„

SKILL.md

Installable skill definition

Quality Score

95/100

Supported Platforms

Universal

Tags

Our assessment of wiki-status

wiki-status scores 95/100 on our quality scale, 377th of 4,698 Development & Engineering skills we index (top 9%).

Its SKILL.md is 31 KB long, well organised into 51 sections with 18 code examples: a thorough specification that gives an agent plenty to work with.

With 3,485 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so wiki-status is actively maintained.
  • Our last check on 2026-11-16 could not reach the source (HTTP 404); it may have been moved or deleted.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit โ€” read the skill file before letting an agent act on it.

wiki-status compared with similar skills

All 4 of these similar skills score higher than wiki-status; compare them before choosing.

SkillScoreStarsUpdatedFormat
wiki-status (this skill)by Ar9av953.5k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install wiki-status?
Run npx skills add Ar9av/obsidian-wiki --skill wiki-status. The install tabs above show the steps for each supported agent.
Which AI agents does wiki-status work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is wiki-status safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is wiki-status still maintained?
The repository was last updated about 2 months ago, so wiki-status is actively maintained.

name: wiki-status description: > Report wiki ingestion/completeness state, pending source delta, structural insights, maintenance equilibrium, or what each recurring job costs. Use for remaining-work/status questions, hubs and bridges, whether maintenance skills still have pending changes, or "what is the wiki costing me" / "cost per job". wiki-digest summarizes learned knowledge instead.

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>.

{
  "version": 1,
  "last_updated": "2026-04-06T10:30:00Z",
  "sources": {
    "Raw/papers/attention.pdf": {
      "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_repo": "github.com/owner/my-app",
      "source_cwd_hint": "~/.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 | Meaning | Action needed | |---|---|---| | New | File exists on disk, not in manifest | Needs ingesting | | Modified | File in manifest, hash differs from content_hash | Needs re-ingesting | | Touched | File in manifest, mtime newer but hash unchanged | Skip โ€” content identical, no re-ingest needed | | Unchanged | File in manifest, mtime and hash both match | Nothing to do | | Deleted | Vault-local source in the manifest, but the file no longer exists on disk | Note it โ€” wiki pages may be stale | | Unavailable | Machine-local source (home-relative or absolute key) absent on this machine โ€” e.g. a synced entry from another host | Skip โ€” do not report as deleted or clean up; it may exist on the machine that ingested it |

When a manifest entry has no content_hash (older entry), fall back to mtime comparison only.

For Claude history specifically, also compute:

  • New projects (directories in ~/.claude/projects/ not in manifest)
  • New conversations within existing projects
  • Updated memory files

For Codex history specifically, also compute:

  • New rollout files under sessions/**
  • Updated session_index.jsonl entries (session title/freshness changes)
  • Archived rollout delta only when archive coverage is requested

Step 3: Report the Status

Visibility tally (before rendering the report): Grep frontmatter across all vault .md pages for visibility/internal and visibility/pii tag values. Count:

  • public = pages with visibility/public tag or no visibility/ tag at all
  • internal = pages with visibility/internal tag
  • pii = pages with visibility/pii tag

Include this in the Overview section as Page visibility: N public ยท M internal ยท K pii. Skip the line if all pages are untagged (fully public vault).

Present a clear summary:

# Wiki Status

## Overview
- **Total wiki pages:** 87 across 6 categories
- **Page visibility:** 72 public ยท 11 internal ยท 4 pii
- **Total sources ingested:** 42
- **Projects tracked:** 6
- **Last ingest:** 2026-04-06T11:00:00Z
- **Staged writes pending:** 4 pages ยท 2 patches (oldest: 3 days ago)  โ† only when WIKI_STAGED_WRITES=true

## Delta (what's changed since last ingest)

### New sources (never ingested): 12
| Source | Type | Size |
|---|---|---|
| ~/Documents/research/new-paper.pdf | document | 2.1 MB |
| ~/.claude/projects/-Users-.../session-xyz.jsonl | claude_conversation | 340 KB |
| ~/.codex/sessions/2026/04/12/rollout-...jsonl | codex_rollout | 220 KB |
| ... | | |

### Modified sources (need re-ingesting): 3
| Source | Last ingested | Last modified | Delta |
|---|---|---|---|
| ~/notes/architecture.md | 2026-04-01 | 2026-04-05 | 4 days newer |
| ... | | | |

### New projects (not yet in wiki): 2
- **tractorex** (3 conversations, 2 memory files)
- **papertech** (1 conversation, 0 memory files)

### Deleted sources (ingested but gone): 0

## Summary
- **Ready to ingest:** 12 new + 3 modified = 15 sources
- **Up to date:** 27 sources unchanged
- **Recommendation:** Append (delta is small relative to total)

## Token Footprint (estimated)

| Scope | Pages | ~Tokens |
|---|---|---|
| core tier | 12 | 18,400 |
| supporting tier | 87 | 94,200 |
| peripheral tier | 43 | 31,600 |
| **Full wiki (all)** | **142** | **144,200** |

Index-only pass (frontmatter + summaries): ~8,900 tokens
Typical query (index + 5 full pages):      ~14,200 tokens

โš ๏ธ  Full wiki exceeds 100K tokens. Consider:
  - Demoting peripheral pages (promote tier suggestions from wiki-status insights mode)
  - Running /wiki-lint --consolidate to merge near-duplicates
  - Using wiki-query fast mode for most queries

Step 3b: Compute Token Footprint

After building the status summary, compute the token footprint estimate:

  1. Per-tier page sizes โ€” Glob all .md pages. Read the tier: frontmatter field of each (cheap grep). Group pages by tier value (core, supporting, peripheral; unset โ†’ supporting).

  2. Estimate tokens โ€” For each page, estimate token count as file_size_bytes / 4 (4 chars/token heuristic โ€” no actual tokenizer needed). Sum per tier and total.

  3. Index-only estimate โ€” Estimate the cost of an index-only pass: sum len(title) + len(summary) + len(tags) for each page frontmatter (~100 chars each on average), divided by 4.

  4. Typical query estimate โ€” Index-only estimate + average full-read cost of 5 pages (total_chars / total_pages * 5 / 4).

  5. Threshold check โ€” Read WIKI_TOKEN_WARN_THRESHOLD from config (default: 100000). If 0, skip the warning. If full-wiki token estimate exceeds the threshold, emit a โš ๏ธ warning with the three remediation suggestions shown in the template above.

  6. Include in every standard status run โ€” both normal and insights mode. The methodology note (4 chars/token heuristic) appears as a footnote below the table.

Step 4: What to Do Next

Replace the old single-line Recommendation with a ranked What to Do Next section. Gather these signals before rendering:

4a: Gather signals

  1. Staged writes pending (only when WIKI_STAGED_WRITES=true) โ€” Glob $OBSIDIAN_VAULT_PATH/_staging/**/*.md and **/*.patch.md. Count new pages and patches separately. Report the oldest file's age (mtime). This is always listed first if any staged files exist โ€” it has the highest intent signal (the LLM already did the work; the human just needs to review).

  2. _raw/ files โ€” list every file at the top level of $OBSIDIAN_VAULT_PATH/_raw/ that isn't a .gitkeep, excluding the _archived/ subdirectory (already-promoted drafts kept for provenance, not pending work). Count and name them.

  3. Stale core pages โ€” scan all vault .md files. A page is "stale" when its updated frontmatter field is โ‰ฅ90 days before today's date AND it has โ‰ฅ5 incoming wikilinks (i.e., it's "core" โ€” other pages depend on it). List them by name + last-updated date.

  4. Orphan pages โ€” pages with zero incoming wikilinks. To compute: glob all .md pages, extract every [[wikilink]], count references to each page, collect pages with incoming == 0. Show up to 5 names; report total count.

  5. Synthesis opportunities โ€” check hot.md for any recent /wiki-synthesize run summary. If the last synthesis run reported N opportunities, surface that count. If no synthesis has been run recently (not in hot.md or log.md within last 14 days), flag it as "synthesis scan overdue".

  6. Source delta โ€” from Step 2: count of new + modified sources ready to ingest.

  7. Lint issues โ€” check log.md for a recent /wiki-lint run (within last 30 days). If a recent run recorded broken links or missing frontmatter, surface the count. If no lint run appears in the log, flag "lint not run recently".

4b: Rank and render

Score each category and emit a ranked list, capped at 6 items. Always rank in this priority order (skip a category if its count is 0 or it has nothing to report):

| Priority | Category | Trigger | |---|---|---| | 0 | Staged writes pending | Any .md/.patch.md in _staging/ (only when WIKI_STAGED_WRITES=true) | | 1 | _raw/ files waiting | Any files present in _raw/ | | 2 | Stale core pages | Any page: updated โ‰ฅ90 days ago AND โ‰ฅ5 incoming links | | 3 | Orphan pages | Any pages with zero incoming wikilinks | | 4 | Synthesis opportunities | N opportunities from last synthesize run, OR scan overdue | |

Truncated for display โ€” read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3.5k
CategoryDevelopment
Updated1mo ago
Forks345

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit โ€” see the Safety scan above for what the skill file itself contains.

No cautions
wiki-status โ€” Universal Skill: Install & Safety Check | SkillAgent