Reports which Obsidian wiki pages need factual review and drift evaluation coverage.
npx skills add https://github.com/ehartye/wiki-master --skill wiki-stale-ehartye
Please help me install this Agent Skill. Skill: wiki-stale Source: https://github.com/ehartye/wiki-master/tree/main/skills/wiki-stale Command: npx skills add https://github.com/ehartye/wiki-master --skill wiki-stale-ehartye
reviewed (factual verification) from updated (mere edits). - Drift Coverage Check: Reports semantic-drift evaluation coverage and failures in read-only mode, without claiming unevaluated pages are clean. - Currency Assessment: When asked whether guidance is current, inspects actual claims against supporting evidence for a topic, prioritizing high-use or volatile pages. - Use Case: Before acting on wiki recommendations about a fast-changing library, ask which pages need review and whether the relevant claims are still supported by evidence. ## Quick Start Ask which wiki pages are going stale and whether the recommendations on a specific topic are still current.High-intent search queries and answers about installing and using this skill.
Run the staleness report, which executes a Node script against the obsidian CLI to list stale pages and pages missing review. It separates `reviewed` (factual verification) from `updated` (edits), since a recent edit does not make old claims fresh.
Inspect the actual claims and their supporting evidence for the requested topic, prioritizing high-use or volatile guidance. Metadata alone shows what needs review; verifying currency requires checking claims against evidence and reporting what remains unverified.
The `reviewed` field records factual verification of a page's claims against evidence, while `updated` only records that an edit occurred. Refreshing embeddings or adding links counts as an update but never qualifies as a review.
No, the report is strictly read-only: it opens no operation, writes no log, and refreshes no index. The drift coverage check is also read-only; bounded embedding maintenance that writes a cache belongs to the separate lint workflow.
A failed, invalid, or empty CLI query falls back to scoped wiki files at the resolved vault root. A missing vault root or wiki directory is reported as an explicit failure rather than an empty report.
servitolaBuild and maintain a persistent Markdown wiki knowledge base with interlinked pages.
Phife726Verify factual claims against credible evidence with confidence ratings.
JYeswakReproduce reported bugs into minimal steps with environment evidence attached.
alastor0325Verify Firefox Knowledge Wiki facts against primary sources and update stale claims.