SkillAgentSearch skills...

wiki-lint

Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.

Install / Use

npx skills add Ar9av/obsidian-wiki --skill wiki-lint

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

95/100

Supported Platforms

Universal

Tags

Our assessment of wiki-lint

wiki-lint scores 95/100 on our quality scale, 152nd of 947 AI & Machine Learning skills we index (top 17%).

Its SKILL.md is 38 KB long, well organised into 68 sections with 20 code examples: a thorough specification that gives an agent plenty to work with.

With 3,485 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so wiki-lint is actively maintained.
  • Our last check on 2026-11-16 could not reach the source (HTTP 404); it may have been moved or deleted.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

wiki-lint compared with similar skills

All 4 of these similar skills score higher than wiki-lint; compare them before choosing.

SkillScoreStarsUpdatedFormat
wiki-lint (this skill)by Ar9av953.5k54d agoSKILL.md
claude-memby thedotmack100117.6ktodayCLAUDE.md
Understand-Anythingby Egonex-AI10092.8k1d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install wiki-lint?
Run npx skills add Ar9av/obsidian-wiki --skill wiki-lint. The install tabs above show the steps for each supported agent.
Which AI agents does wiki-lint work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is wiki-lint safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is wiki-lint still maintained?
The repository was last updated about 2 months ago, so wiki-lint is actively maintained.

name: wiki-lint description: > Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.

Wiki Lint β€” Health Audit

You are performing a health check on an Obsidian wiki. Your goal is to find and fix structural issues that degrade the wiki's value over time.

Before scanning anything: follow the Retrieval Primitives table in llm-wiki/SKILL.md. Prefer frontmatter-scoped greps and section-anchored reads over full-page reads. On a large vault, blindly reading every page to lint it is exactly what this framework is built to avoid.

Before You Start

Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence. Apply WRITING.md preferences only to generated consolidation reports; deterministic findings and fixes keep their existing formats.

  1. Resolve config β€” follow the Config Resolution Protocol in llm-wiki/SKILL.md (inline @name override β†’ walk up CWD for .env β†’ global config β†’ prompt setup). This gives OBSIDIAN_VAULT_PATH plus any OBSIDIAN_ALLOWED_LIFECYCLES, OBSIDIAN_ALLOWED_RELATIONSHIP_TYPES, OBSIDIAN_REQUIRED_TRUST_FIELDS, and OBSIDIAN_SCHEMA_SOURCE values.
  2. Read owner rules β€” if $OBSIDIAN_VAULT_PATH/AGENTS.md exists, read it before interpreting any schema. Owner rules override framework defaults.
  3. Form the effective schema β€” record the schema source locator plus effective required/optional frontmatter, lifecycle values, relationship types, and provenance markers. Framework values are defaults; preserve owner extensions and relaxed requiredness exactly. Never coerce an owner type to a framework type.
  4. Read index.md for the full page inventory
  5. Read log.md for recent activity context

Pass the effective schema to deterministic checks explicitly. For example, add each owner extension with --allow-lifecycle / --allow-relationship-type, replace trust requiredness with repeatable --required-trust-field, and identify the authority with --schema-source "$OBSIDIAN_VAULT_PATH/AGENTS.md". The JSON report's schema block must match the schema you formed before findings are accepted.

Schema precedence is CLI flags > resolved environment/config values > framework defaults; lifecycle and relationship extensions remain additive. Strip every override before use. An explicitly configured empty or whitespace-only valueβ€”and any empty comma-separated list entryβ€”fails closed; never treat it as a valid lifecycle, relationship type, required field, or authority locator. Remove the variable instead when defaults are intended.

When obsidian-wiki is on PATH, prefer obsidian-wiki lint "$OBSIDIAN_VAULT_PATH" --json (with the same schema override flags as above) and fold the JSON findings into the health report. If the CLI is unavailable, keep the grep-based checks below β€” do not require the binary.

If the JSON report includes findings.snapshot_mismatch, list those pages in the report. Missing or drifted snapshots: is not missing required frontmatter (section 3 still covers only title, category, tags, sources, created, updated). Do not rewrite sources: to fix snapshot drift. Run obsidian-wiki snapshots apply --from-json <lint.json> (dry-run), show the preview, and pass --apply only after explicit user confirmation. Apply writes quoted "[[_raw/_archived/stem|stem]]" list items (native Property links with display text). wiki-lint --consolidate still does not apply this finding.

Lint Checks

Run these checks in order. Report findings as you go.

Scope: skip _archives/, _raw/, _readouts/, and .obsidian/ in every check. These hold frozen snapshots, unprocessed staging drafts, and derived readouts (saved by wiki-narrate) β€” they are not knowledge-graph pages, so orphan, frontmatter, and link checks don't apply to them.

1. Orphaned Pages

Find pages with zero incoming wikilinks. These are knowledge islands that nothing connects to.

How to check:

  • Glob all .md files in the vault
  • For each page, Grep the rest of the vault for [[page-name]] references
  • Pages with zero incoming links (except index.md and log.md) are orphans

How to fix:

  • Identify which existing pages should link to the orphan
  • Add wikilinks in appropriate sections

2. Broken Wikilinks

Find [[wikilinks]] that point to pages that don't exist.

How to check:

  • Grep for \[\[.*?\]\] across all pages
  • Extract the link target: drop everything from the first | (alias) or # (heading/block anchor), and strip a trailing backslash left by an escaped \| inside a table cell
  • Skip a target whose extension is an attachment type (.png, .jpg, .gif, .svg, .webp, .pdf, .canvas, .base, audio and video): it's an embed, not a page link, and has no entry in the .md inventory this check compares against
  • Do not treat every dot as an extension β€” [[Node.js]], [[Next.js]], and [[v1.2 release notes]] are page links whose names happen to contain a dot, and dropping them would both miss real broken links and make the target page look like an orphan
  • Strip an explicit .md suffix from what remains, then check if a corresponding .md file exists

How to fix:

  • If the target was renamed, update the link
  • If the target should exist, create it
  • If the link is wrong, remove or correct it

3. Missing Frontmatter

Every page should have: title, category, tags, sources, created, updated.

How to check:

  • Grep frontmatter blocks (scope to ^--- at file heads) instead of reading every page in full
  • Flag pages missing required fields

How to fix:

  • Add missing fields with reasonable defaults

3a. Missing Summary (soft warning)

Every page should have a summary: frontmatter field β€” 1–2 sentences, ≀200 chars. This is what cheap retrieval (e.g. wiki-query's index-only mode) reads to avoid opening page bodies.

How to check:

  • Grep frontmatter for ^summary: across the vault
  • Flag pages without it, but as a soft warning, not an error β€” older pages predating this field are fine; the check exists to nudge ingest skills into filling it on new writes.
  • Also flag pages whose summary exceeds 200 chars.

How to fix:

  • Re-ingest the page, or manually write a short summary (1–2 sentences of the page's content).

4. Stale Content

Pages whose updated timestamp is old relative to their sources.

How to check:

  • Compare page updated timestamps to source file modification times
  • Flag pages where sources have been modified after the page was last updated

Uncovered sources. obsidian-wiki lint reports uncovered_sources: .manifest.json entries whose pages_produced/pages_created/pages_updated list is empty (no_pages) or names only pages that no longer exist (pages_missing). Each one is a source the vault says it ingested but no page now carries. A warning. For each, re-ingest the source, or point the manifest entry at the page that absorbed it (after a rename or wiki-dedup merge). Never delete the entry to silence the finding.

Undated claims (line-level). obsidian-wiki lint reports undated_claims: lines stating a count or amount that goes stale (stars, users, customers, downloads, deals, MRR/ARR) with no date on the line. Lines under a dated heading, pages in journal/ or named YYYY-MM-…, code, and blockquotes are exempt. A warning, never a failure. For each one, either re-check the number and stamp it (as of YYYY-MM-DD), replace it with a link to where the live number lives, or move it under a dated heading as history.

5. Contradictions

Claims that conflict across pages.

How to check:

  • This requires reading related pages and comparing claims
  • Focus on pages that share tags or are heavily cross-referenced
  • Look for phrases like "however", "in contrast", "despite" that may signal existing acknowledged contradictions vs. unacknowledged ones

How to fix:

  • Add an "Open Questions" section noting the contradiction
  • Reference both sources and their claims

6. Index Consistency

Verify index.md matches the actual page inventory.

How to check:

  • Compare pages listed in index.md to actual files on disk
  • Check that summaries in index.md still match page content

7. Provenance Drift

Check whether pages are being honest about how much of their content is inferred vs extracted. See the Provenance Markers section in llm-wiki for the convention.

How to check:

  • For each page with a provenance: block or any ^[inferred]/^[ambiguous] markers, count sentences/bullets and how many end with each marker
  • Compute rough fractions (extracted, inferred, ambiguous)
  • Apply these thresholds:
    • AMBIGUOUS > 15%: flag as "speculation-heavy" β€” even 1-in-7 claims being genuinely uncertain is a signal the page needs tighter sourcing or should be moved to synthesis/
    • INFERRED > 40% with no sources: in frontmatter: flag as "unsourced synthesis" β€” the page is making connections but has nothing to cite
    • Hub pages (top 10 by incoming wikilink count) with INFERRED > 20%: flag as "high-traffic page with questionable provenance" β€” errors on hub pages propagate to every page that links to them
    • Drift: if the page has a provenance: frontmatter block, flag it when any field is more than 0.20 off from the recomputed value
  • Skip pages with no provenance: frontmatter and no markers β€” treated as fully extracted by convention

How to fix:

  • For ambiguous-heavy: re-ingest from sources, resolve the uncertain claims, or split speculative content into a synthesis/ page
  • For unsourced synthesis: add sources: to frontmatter or clearly label the page as synthesis
  • For hub pages with INFERRED > 20%: prioritize for re-ingestion β€” errors here have the widest blast radius
  • For drift: update the provenance: frontmatter to match the recomputed values

8. Fragmented Tag Clusters

Checks whether pages that share a tag are actually linked to each other. Tags imply a topic cluster; if those pages don't reference each other, the cluster is fragmented β€” knowledge islands that should be woven together.

How to check:

  • For each tag that appears on β‰₯ 5 pages:
    • n = count of pages with this tag
    • actual_links = count of wikilinks between any two pages in this tag group (check both directions)
    • cohesion = actual_links / (n Γ— (nβˆ’1) / 2)
  • Flag any tag group where cohesion < 0.15 and n β‰₯ 5

How to fix:

  • Run the cross-linker skill targeted at the fragmented tag β€” it will surface and insert the missing links
  • If a tag group is large (n > 15) and still fragmented, consider splitting it into more specific sub-tags

9. Visibility Tag Consistency

Checks that visibility/ tags are applied correctly and aren't silently missing where they matter.

How to check:

  • Untagged PII patterns: Grep page bodies for patterns that commonly indicate sensitive data β€” lines containing password, api_key, secret, token, ssn, email:, phone: followed by an actual value (not a field description). If a page matches and lacks visibility/pii or visibility/internal, flag it as a likely mis-classification.
  • visibility/pii without sources:: A page tagged visibility/pii should always have a sources: frontmatter field β€” if there's no provenance, there's no way to verify the classification. Flag any visibility/pii page missing sources:.
  • Visibility tags in taxonomy: visibility/ tags are system tags and must not appear in _meta/taxonomy.md. If found there, flag as misconfigured β€” they'd be counted toward the 5-tag limit on pages that include them.

How to fix:

  • For untagged PII patterns: add `vis

Truncated for display β€” read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3.5k
CategoryAI
Updated1mo ago
Forks345

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
wiki-lint β€” Universal Skill: Install & Safety Check | SkillAgent