Skip to content
SkillModel-led745 tokens in use

wiki-lint

A deterministic, read-only health check for an Obsidian wiki that reports dead links, orphans, frontmatter gaps and ledger problems.

16,653 stars on the repository MIT LicenseAgriciDaniel/claude-obsidian · skills/wiki-lint
claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing wiki-lint costs

80tokens idle
745tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure19/25
  • Examples12/15
  • Output15/15
  • Size11/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 15

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity84
  • Maintenance100
  • Community56
  • Maturity28
  • Momentum40

wiki-lint runs the claude-obsidian lint engine on your vault and explains what it finds. It understands wikilinks, embeds, aliases, heading and block fragments and code fences, and reports dead or ambiguous links, orphan pages, missing frontmatter, empty sections, stale index entries and source or claim ledger violations.

It only observes. Repairs are a separate operation you choose, built as a new reviewed transaction.

What You Get

  • A lint report in text or Markdown with paths, lines, targets and counts
  • Findings grouped by impact with suggested remediation kept separate from facts
  • Path exclusion for scratch folders
  • A repair plan for findings you pick, built as a new transaction
  • A before and after lint comparison once repairs are applied

Common Use Cases

  • Auditing a vault for dead links and orphans before sharing it
  • Checking required frontmatter across all pages
  • Verifying that source and claim ledgers stay consistent after an ingest

What Makes It Unique

The linter is deterministic and honors gitignore files inside the vault without calling git, skips dot-prefixed folders as Obsidian does, and never writes a report into the vault. Repairs are never automatic: each fix re-reads its target, records the expected hash and applies through the transaction engine.

Under The Hood

The skill is instructions that run the plugin’s Python core script through the shell with the lint command, which reads the vault and prints a report. It does not fetch web pages or write files during linting. Only if you choose repairs does it build and apply a transaction bundle, and that step writes the approved fixes after you approve the plan hash.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers