wiki-lint

Audits an LLM wiki vault for structural issues, stale pages, and contradictions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Personal or team knowledge wikis degrade over time: pages become orphaned, wikilinks break, content goes stale, and contradictory claims accumulate silently across related pages. This Skill performs a systematic health check of an LLM wiki vault and produces a prioritized report with concrete remediation actions. ## Core Features & Use Cases - Structural and navigability checks: Detects missing agent instruction files, incomplete taxonomy or index files, orphaned pages, and broken wikilinks. - Freshness and deduplication analysis: Compares updated: frontmatter against raw sources, flags pages untouched for over 90 days, and identifies merge or consolidation candidates among similar pages. - Conflict detection across page clusters: Groups related pages by wikilinks, tags, and frontmatter, then extracts claims to find factual, status, recommendation, quantitative, temporal, presuppositional, and categorical contradictions. - Use Case: Run a periodic lint on your Obsidian-style vault to get a report classifying every issue as CRITICO, ATTENZIONE, or SUGGERIMENTO, each paired with a concrete fix action. ## Quick Start Ask the assistant to lint the wiki vault and produce a health report of structural problems, stale content, and contradictions.

Frequently Asked Questions about wiki-lint

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

FAQPage Schema
How do I check my wiki or knowledge base for broken links and orphaned pages?

Run a wiki lint that scans the vault for orphaned pages, broken wikilinks, and incomplete index or taxonomy files. The check verifies that declared active paths actually exist and that navigation files reflect the real vault structure.

How to detect contradictions between notes in a markdown wiki?

Contradiction detection works by clustering related pages via wikilinks, shared tags, and frontmatter fields, then extracting claims using copula, modal, polarity, number, and date signals. Claims are grouped by subject and predicate to surface factual, status, temporal, and other conflict types.

What files does the wiki lint need before running?

The lint reads four vault metadata files first: _meta/log.md, _meta/index.md, _meta/taxonomy.md, and _meta/hot-cache.md. It also checks that at least one agent instruction file such as CLAUDE.md, AGENTS.md, or GEMINI.md exists at the vault root.

How does the lint decide whether a wiki page is stale?

A page is stale when its updated frontmatter field is older than the referenced raw source, or when it has not been updated in over 90 days. Pages older than 90 days with no inbound wikilinks are flagged as potentially obsolete and orphaned.

When are conflicting claims between pages not reported as problems?

Conflicts already resolved in the log, explicitly speculative low-confidence claims, attributed third-party opinions, documented temporal evolutions, and declared scope differences are excluded. These cases represent legitimate disagreement or historical change rather than true contradictions.