Wiki lint

Skill AgriciDaniel/claude-obsidian/skills/wiki-lint

Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason broadly or repair files.From its SKILL.md

Install

npx -y skills add AgriciDaniel/claude-obsidian --skill wiki-lint

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.0 KB, as published. Nobody here has run it

Lint the wiki

Use the portable lint engine as the source of truth. Lint observes vault state; it does not create reports, dashboards, canvases, stubs, or fixes.

Resolve the installed product root from this skill's own location, not from the vault or current working directory:

PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
test -f "$CORE"

Run

Resolve the user vault, then run one of:

python3 "$CORE" lint --vault "$VAULT"
python3 "$CORE" lint --vault "$VAULT" --format markdown

Use --strict only when a nonzero exit for findings is useful in automation. The command remains read-only either way.

The deterministic parser understands Obsidian wikilinks and embeds, Markdown links, aliases, heading and block fragments, escaped aliases, and code fences. It reports such categories as dead or ambiguous links, orphan pages, required frontmatter gaps (including title), empty sections, stale index entries, and source/claim ledger contract violations. Report only the checks and counts present in its output; do not claim that it performed semantic, stylistic, or prose-level contradiction analysis when it did not.

Explain findings

Preserve the engine's paths, line numbers, targets, categories, and counts.
Group findings by likely impact: broken navigation, ambiguous resolution, metadata quality, then maintainability.
Explain that an orphan may be intentional and an ambiguous basename needs a path-qualified link; do not infer intent from the finding alone.
Treat allowlisted findings as policy, not as proof that the target exists.
Separate deterministic facts from suggested remediation.

Do not write the Markdown rendering into the vault. Return it in chat or stdout.

Repair is a separate operation

Never auto-fix a lint result. After the user chooses specific findings to repair:

Re-read each target and record its expected SHA-256.
Draft only the selected changes; do not delete or merge pages without explicit consent.
Build one repair bundle with a new operation ID.
Inspect the bundle and show exact changed paths.
Apply only after that separate review.
Re-run lint read-only and compare the relevant findings.

Follow the operation transaction contract. Lint itself never applies that transaction and never commits Git.

Checkpoint

Observe the deterministic report, think about root causes rather than finding count, verify proposed repairs against current hashes, and grow by improving the workflow that produced repeated findings.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

Read full output and check exit codein 45 of 1524, across 40 files
Verify output confirms the claimin 44 of 1524, across 39 files
Identify the command that proves the claimin 43 of 1524, across 39 files
Execute the full verification commandin 36 of 1524, across 30 files
Produce a verification reportin 34 of 1524, across 18 files
Review git diff changesin 30 of 1524, across 16 files
Fix build failures immediatelyin 29 of 1524, across 9 files
Group findings by severityin 28 of 1524
State claim only with evidencein 27 of 1524, across 22 files
Verify regression tests with red-green cyclein 26 of 1524, across 22 files
Run the full test suitein 26 of 1524, across 25 files
Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

Use the portable lint engine as source of truth
Resolve product root from the script location
Run lint command with vault path
Preserve engine paths and line numbers
Separate deterministic facts from remediation
Re-read target and record SHA-256 before repair

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.