wiki-lint

Review Obsidian wiki pages for contradictions, unverified quotes, and stale claims, then apply safe fixes.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/ehartye/wiki-master --skill wiki-lint-ehartye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-lint
Source: https://github.com/ehartye/wiki-master/tree/main/skills/wiki-lint
Command: npx skills add https://github.com/ehartye/wiki-master --skill wiki-lint-ehartye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-lived markdown wikis accumulate contradictions, unsupported quotes, and stale claims as sources change. This Skill audits an Obsidian vault for semantic and content-level issues and applies safe, authorized maintenance fixes with a committed audit trail. ## Core Features & Use Cases - Semantic Drift Detection: Runs Ollama-backed embedding checks to flag pages whose content has drifted from their evidence trail. - Quote Verification: Lints quotes against each page's raw clipping evidence, adjudicating real drift versus quoting-convention artifacts and marking genuinely unsourced claims. - Safe Fix Workflow: Applies only unambiguous fixes under an explicit operation lifecycle (op-begin/op-commit) so lint changes are committed separately from the user's in-progress work. - Use Case: After a month of ingesting new sources, run the lint to find pages contradicting newer evidence, verify flagged quotes against clippings, fix mechanical issues, and commit a logged maintenance operation. ## Quick Start Ask the agent to run wiki-lint to review the vault for contradictions, stale claims, and unverified quotes, then apply safe fixes.

Frequently Asked Questions about wiki-lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check an Obsidian wiki for contradictions and stale claims?▼

Run wiki-lint, which starts with a structural health check, then samples changed or high-use pages for stale claims, contradictory evidence, and missing cross-references. It applies only safe fixes and presents the rest as a proposed change list.

How does semantic drift detection work in a markdown wiki?▼

The drift.mjs script uses an Ollama embedding model to compare page content against its evidence trail, reporting eligible, evaluated, failed, and skipped counts. Similarity is a topical diagnostic only, never proof of claim correctness.

What is the difference between wiki-lint, wiki-health, and wiki-stale?▼

wiki-health produces a structural report only, and wiki-stale reports freshness only. wiki-lint performs the deeper semantic review of contradictions, unsupported quotes, and stale claims, and can apply authorized maintenance fixes.

Does wiki-lint require Ollama to run?▼

Ollama with an embedding model such as nomic-embed-text is required for the semantic drift check, but the setup degrades gracefully if absent. Structural health and content lint steps still run without it.

Why does wiki-lint open an operation before editing pages?▼

The op-begin script records what was already uncommitted so the final op-commit includes only the lint's fixes, not the user's in-progress work. This guarantees every applied fix leaves a committed, logged audit trail.