Download .skills/wiki-status/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-status live?
The publisher keeps it at https://github.com/Ar9av/obsidian-wiki.
Which agents can use wiki-status?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
>
name: wiki-status
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.
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 prose; keep the analyser snapshot verbatim.
_insights.md
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.
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>.
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)
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:
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).
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.
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.
Typical query estimate — Index-only estimate + average full-read cost of 5 pages (total_chars / total_pages * 5 / 4).
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.
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
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).
_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.
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.
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.
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".
Source delta — from Step 2: count of new + modified sources ready to ingest.
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
5
New/modified sources
Count from delta in Step 2
6
Lint issues
Known issues from last lint run, OR lint overdue
Render as:
## What to Do Next
0. 📋 6 staged pages waiting for review (oldest: 3 days ago)
→ 4 new pages + 2 patches in _staging/
run: /wiki-stage-commit
1. 📥 Ingest 3 files waiting in _raw/
→ architecture-notes.md, meeting-2026-05-10.md, paper-draft.pdf
run: /wiki-ingest
2. 🔄 Refresh 2 stale core pages (not updated in 90+ days)
→ [[System Architecture]] (last updated 2026-02-10), [[API Design]] (2026-01-15)
run: open these pages and re-run /wiki-update
3. 🔗 Link 7 orphan pages → run: /cross-linker
Disconnected: [[Redis Caching]], [[JWT Tokens]], +5 more
4. 🧩 2 synthesis opportunities identified → run: /wiki-synthesize
[[Redis Caching]] × [[Session Management]] (co-occur in 8 pages)
5. ✅ 4 sources modified since last ingest → run: /wiki-ingest (append mode)
6. 🩺 Lint not run in 30+ days — run: /wiki-lint
Empty state: If all categories have nothing to report (no staged files, no _raw/ files, no orphans, no stale pages, no synthesis opportunities, no new sources, no lint issues), output instead:
## What to Do Next
✅ Wiki is healthy — nothing urgent.
All sources up to date · no orphans · no stale core pages · no _raw/ files pending · no staged writes
Overflow: If more than 6 items would be shown, add a footer line: _(N more items available — run /wiki-status --full to see all)_. The --full flag is not yet implemented; this is forward-looking copy that sets expectations.
Insights Mode
Triggered when the user asks something like "wiki insights", "what's central in my wiki", "show me the hubs", "cross-domain bridges", "what pages are most important", or "wiki structure". This mode is additive — it doesn't replace the delta report, it analyzes the shape of the wiki itself.
Where the delta report tells the user what's pending, insights mode tells them what they've already built and where the interesting structure lives. Complements wiki-lint (which finds problems) by surfacing interesting structure.
What to compute
First, run the graph analyser. This replaces manual wikilink parsing — one command produces all the raw data you need:
obsidian-wiki graph-analyse "$OBSIDIAN_VAULT_PATH" --pretty --snapshot \
--diff-against "$OBSIDIAN_VAULT_PATH/_insights.md" # omit if no previous _insights.md
The analyser runs the same algorithm family graphify applies to code graphs, in pure Python: degree ranking, community detection (Leiden if obsidian-wiki[graph] is installed, else label propagation), community cohesion, Brandes betweenness centrality, cross-community surprise scoring, and snapshot diffing. Vault bookkeeping files (index, log, hot, _insights, _meta/, _readouts/) are excluded so they don't dominate every ranking.
Output fields used below:
god_nodes — pages ranked by total degree (in + out), with in_degree/out_degree. Use for anchor pages and hub classification.
bridges — pages ranked by betweenness centrality (share of shortest paths passing through them), with community and the list of other communities they connects. Use directly for the Bridge Pages section — no manual tag-pair search needed.
communities — page clusters by link density, each with label, size, pages, and cohesion (intra-cluster edge density, 0–1). Use for cluster labelling and the cohesion section.
surprising_connections — cross-community edges ranked by unexpectedness, one per community pair before any pair repeats, each with a note naming the two communities. Use directly in the Surprising Connections section.
suggested_questions — {type, question, why} derived from bridges, sink hubs, isolates and low-cohesion clusters. Seed the Questions section with these.
dead_ends — pages with zero outgoing links. Use for orphan-adjacent and cross-linker suggestions.
isolated — pages with zero links in either direction. Use for stubs/orphan reporting.
stats — total pages, edges, communities, graph density.
diff (only with --diff-against) — added_pages, removed_pages, added_edges, removed_edges, newly_connected, lost_incoming, summary. Use for the Graph Delta section.
snapshot (only with --snapshot) — write this JSON verbatim into the `` comment at the end of _insights.md.
Query modes (useful when the user asks a follow-up): --path A B returns the shortest link chain between two pages; --around PAGE --depth N [--direction in|out|both] returns the N-hop neighbourhood (--direction in = the blast radius if PAGE were renamed or removed).
Fallback (if obsidian-wiki is not installed): glob all .md pages, extract every [[wikilink]], and build incoming, outgoing, and tags maps manually, then approximate the sections below by hand.
You'll reuse this data across all sections below.
Anchor pages (top hubs). Pages with the most incoming links — the load-bearing concepts.
Rank all pages by incoming count, take top 10
For each, note both incoming and outgoing counts: pages with high incoming and high outgoing are connector hubs (most valuable)
Pages with high incoming but zero outgoing are sink hubs — flag as cross-linker candidates
Bridge pages. Pages that connect otherwise-disconnected clusters — removing them would partition the graph. These are often more structurally important than raw hub count suggests.
Take the top 5 of bridges (already ranked by betweenness centrality)
Label each using the community labels: "P bridges [label of community] ↔ [labels of connects]". A bridge with an empty connects list is an intra-cluster chokepoint — note it as "internal hub of [label]"
Show the betweenness score so runs are comparable over time
Cluster cohesion. How tightly each community's pages are interlinked — read straight from communities[].cohesion (actual_links / (n × (n−1) / 2)).
Fragmented clusters (cohesion < 0.15, size ≥ 5): these pages share a topic but aren't woven together. Surface them as cross-linker targets.
Show the top 5 communities by cohesion (strongest clusters) and bottom 5 (most fragmented), each with its label and size
Optionally repeat the same formula per tag (for tags with ≥ 5 pages) if the user cares about tag-level cohesion
Surprising connections. Cross-community wikilinks that are non-obvious.
Start from surprising_connections (structural score = 1/√(cross-degree(A)·cross-degree(B)); one edge per community pair before any pair repeats, so a single hub can't fill the list)
Re-rank the candidates with content signals the analyser can't see:
+3 if the linking page or claim is marked ^[ambiguous] (uncertain connection, worth reviewing)
+2 if the linking page is marked ^[inferred] (synthesized, not directly stated)
+2 if the categories are in different knowledge layers (e.g., concepts ↔ entities more surprising than concepts ↔ concepts)
Show top 5 with a plain-language reason for each (use the note — "bridges [label A] → [label B]" — plus any content bonus)
Orphan-adjacent suggestions. Pages linked from a top-10 hub but with zero outgoing links of their own. Dead-ends in high-traffic areas — prime cross-linker candidates.
Rough clusters. Group anchor pages by dominant tag. (Simple tag intersection — just for orientation.)
Graph delta since last run. Read straight from the diff field (produced by --diff-against on the previous _insights.md, which the analyser reads from its `` comment):
summary → "+N pages, +M wikilinks"; list added_pages / removed_pages
newly_connected → "newly connected: X, Y" (pages that had no incoming links last run)
lost_incoming → "link target may have been renamed: A, B"
If no previous snapshot exists (no diff field), skip this section
Tier assignment suggestions. After computing hubs and bridges, recommend tier: changes. Never write tier: to pages — only surface suggestions so the human can decide.
Promote to core: pages with ≥5 incoming links OR top-5 bridge position that currently have tier: supporting or no tier: field
Demote to peripheral: pages with ≤1 incoming link AND not updated in 90+ days that currently have tier: supporting or tier: core
Show up to 10 suggestions (promotions first, then demotions), formatted as:
Tier Suggestions:
↑ core [[concepts/attention-mechanism]] — 14 incoming links, currently tier=supporting
↑ core [[entities/andrej-karpathy]] — bridge (3 cluster pairs), currently unset
↓ peripheral [[concepts/old-concept]] — 0 incoming, 120 days stale
If all high-link pages already have tier: core and all low-link pages have tier: peripheral, emit: "Tier assignments look healthy — no changes suggested."
Suggested questions. Questions this wiki structure is uniquely positioned to answer — or that reveal gaps:
From ^[ambiguous] claims (content scan — the analyser doesn't see these): "Resolve: What is the exact relationship between X and Y?"
From suggested_questions — already generated for you: bridge_node → "Explore: …", sink_hub → "Link: …", isolated_nodes → "Link: …", low_cohesion → "Audit: …". Rewrite each into the matching prefix form
Show up to 7, prioritizing AMBIGUOUS first, then bridge nodes, then sink hubs / isolates, then cohesion audits
Output
Write the result to _insights.md at the vault root. Overwrite freely — it's regenerable. At the very end, embed the analyser's snapshot field verbatim as an HTML comment so the next run can diff against it with --diff-against.
# Wiki Insights — <TIMESTAMP>
## Anchor Pages (top 10 hubs)
| Page | Incoming | Outgoing | Note |
|---|---|---|---|
| [[concepts/transformer-architecture]] | 23 | 8 | connector hub |
| [[entities/andrej-karpathy]] | 17 | 0 | sink hub — cross-linker candidate |
## Bridge Pages (top 5)
| Page | Bridges | Cross-cluster pairs |
|---|---|---|
| [[concepts/exponential-growth]] | #ml ↔ #economics | 4 pairs |
## Tag Cluster Cohesion
### Most cohesive (well-linked)
- **#ml** — 12 pages, cohesion 0.41
### Most fragmented (cross-linker targets)
- **#systems** — 7 pages, cohesion 0.06 ⚠️ run cross-linker on this tag
## Surprising Connections (top 5)
- [[concepts/scaling-laws]] → [[entities/gordon-moore]] — score 5
- Reason: cross-layer (concepts ↔ entities), marked ^[inferred]
- ...
## Orphan-Adjacent (dead-ends near hubs)
- [[concepts/foo]] — linked from 3 hubs, 0 outbound links
## Rough Clusters
- **#ml** — transformer-architecture, attention-mechanism, scaling-laws
- **#systems** — distributed-consensus, raft, paxos
## Graph Delta Since Last Run
- +3 new pages, +11 new wikilinks
- Newly connected: [[concepts/bar]], [[entities/baz]]
- Lost incoming links: [[references/old-paper]] (target may have been renamed)
## Tier Suggestions
↑ core [[concepts/attention-mechanism]] — 14 incoming links, currently tier=supporting
↑ core [[entities/andrej-karpathy]] — top bridge (4 cluster pairs), currently unset
↓ peripheral [[concepts/old-concept]] — 0 incoming, 132 days stale
## Questions Worth Asking
1. Resolve: What is the exact relationship between `scaling-laws` and `moore's-law`? (^[ambiguous] claim)
2. Explore: Why does `exponential-growth` bridge #ml and #economics?
3. Link: `references/foo.md` has no incoming links — what should reference it?
4. Audit: Should tag `#systems` be split? (cohesion 0.06, 7 pages)
Vaults with fewer than 20 pages — not enough graph structure. Tell the user and skip.
After a fresh wiki-rebuild — wait until at least one ingest has happened.
Equilibrium Mode
Triggered when the user asks "is my vault at equilibrium", "wiki equilibrium", "is the vault converged", "is maintenance done", "are my skills fighting", or "what's still pending across all the maintenance skills".
The maintenance skills are players in a game over one shared vault. Each has a move set (lint fixes, dedup merges, new links, tag normalizations) and each judges the vault by its own objective. The vault is at equilibrium when no player has a profitable deviation — every audit pass proposes zero changes. That is the real "maintenance is done" signal, and it is stronger than any single skill reporting clean, because skills can undo each other.
This mode is read-only over the players: run every audit in its report-only form and never let one apply changes. It writes nothing except the snapshot line in _insights.md.
The players
Player
Audit-only invocation
Counts as a move
wiki-lint
obsidian-wiki lint "$OBSIDIAN_VAULT_PATH" --json
each finding in findings (sum the stats.findings counts)
wiki-dedup
audit mode (no --merge, no --auto)
each HIGH or MEDIUM duplicate pair
cross-linker
audit pass only — report proposed links, insert none
each unlinked mention it would link
tag-taxonomy
Step 1 audit only — report drift, normalize nothing
each tag it would rename or drop
Only wiki-lint is deterministic; the other three are LLM passes, so their counts are estimates from their own reports. Say so in the output rather than implying exactness.
What to report
# Vault Equilibrium — <TIMESTAMP>
equilibrium: no
| Player | Pending moves | Top proposed move |
|---|---|---|
| wiki-lint | 4 | fix broken link [[concepts/old-name]] in synthesis/foo.md |
| wiki-dedup | 1 | merge entities/gpt-4.md ← entities/gpt4.md (0.91) |
| cross-linker | 12 | link "attention mechanism" in concepts/transformers.md |
| tag-taxonomy | 0 | — |
Deviating players: wiki-lint, wiki-dedup, cross-linker
Converged players: tag-taxonomy
When every count is zero, report equilibrium: yes and state plainly that running any maintenance skill right now would change nothing.
Oscillation detection
A player whose count keeps returning after being driven to zero means two players are fighting — the classic case is tag-taxonomy normalizing a tag that an ingest skill's defaults keep re-adding, so the vault cycles forever and never converges.
Append a snapshot beside the existing GRAPH_SNAPSHOT in _insights.md:
Read the previous EQUILIBRIUM_SNAPSHOT lines (keep the last 5; drop older ones) and compare:
A player going 0 → N → 0 → N across runs is oscillating — flag it by name and name the likely opponent (the skill whose writes reintroduce those moves).
A player whose count only ever grows is losing ground — nobody is running it.
No previous snapshot: report "first run, no baseline yet" and skip the comparison.
Oscillation is a report, not a fix. The resolution is a human decision about which player's objective wins — usually a rule change in _meta/taxonomy.md or the owner's AGENTS.md, not another maintenance run.
Source track record
Pending moves are not evenly distributed across sources. Attribute them back: for each page appearing in a player's findings, look up which manifest source produced it (.manifest.json → pages_created / pages_produced).
When one source accounts for ≥3 issues or ≥50% of a player's pending moves, add a line:
Source track record:
- ~/exports/slack-dump/ — 7 of 12 cross-linker moves, 3 of 4 lint findings.
Its pages consistently need repair; consider reviewing its source_quality bucket.
This is the repeated-game view: a source that keeps producing pages needing repair has earned a lower source_quality. Report only — never adjust source_quality or the trust ledger automatically. The owner decides, through the existing trust flow (obsidian-wiki trust-record), exactly as with every other confidence change.
When to skip
Vaults with fewer than 20 pages — the audits are noise at that size.
If any player's audit can't be run cleanly in report-only form, omit that row and say which player is missing rather than guessing a count.
Notes
If the manifest doesn't exist, report everything as "new" and recommend a full ingest
This skill only reads and reports — it doesn't modify anything (except writing _insights.md in insights mode, which is regenerable)
The actual ingest work is done by the ingest skills (wiki-ingest, claude-history-ingest, codex-history-ingest)
Those skills are responsible for updating the manifest after they finish
QMD Refresh After Vault Writes
QMD is a search index, not the source of truth. If $QMD_WIKI_COLLECTION is empty or unset, skip this step. Run it only after this skill has written or rewritten vault markdown. If QMD refresh fails, do not roll back the vault changes; report the QMD status separately.
Use $QMD_CLI if set; otherwise use qmd.
${QMD_CLI:-qmd} update
If the output says vectors are needed or embeddings may be stale, run:
${QMD_CLI:-qmd} embed
Verify the collection with either:
${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION"
or, when a specific page path is known:
${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<page>.md" -l 5
Record one of:
QMD refreshed: update + embed + verified
QMD refreshed: update only + verified
QMD skipped: QMD_WIKI_COLLECTION unset
QMD skipped: qmd CLI unavailable
QMD failed: <short error summary>
How do I install wiki-status?
Download .skills/wiki-status/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-status live?
The publisher keeps it at https://github.com/Ar9av/obsidian-wiki.
Which agents can use wiki-status?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.