wiki-lint
wiki-lint is a vault maintenance skill that audits Obsidian wiki health by detecting orphan pages, dead links, missing cross-references, frontmatter gaps, stale index entries, and semantic duplicates. Run it after every 10-15 ingests or weekly, and use it to generate structured lint reports that identify structural issues requiring manual review or automated fixing before they accumulate in the knowledge base.
git clone --depth 1 https://github.com/AgriciDaniel/claude-obsidian /tmp/wiki-lint && cp -r /tmp/wiki-lint/skills/wiki-lint ~/.claude/skills/wiki-lintSKILL.md
# 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: ```bash 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: ```bash 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 1. Preserve the engine's paths, line numbers, targets, categories, and counts. 2. Group findings by likely impact: broken navigation, ambiguous resolution, metadata quality, then maintainability. 3. Explain that an orphan may be intentional and an ambiguous basename needs a path-qualified link; do not infer intent from the finding alone. 4. Treat allowlisted findings as policy, not as proof that the target exists. 5. 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: 1. Re-read each target and record its expected SHA-256. 2. Draft only the selected changes; do not delete or merge pages without explicit consent. 3. Build one repair bundle with a new operation ID. 4. Inspect the bundle and show exact changed paths. 5. Apply only after that separate review. 6. Re-run lint read-only and compare the relevant findings. Follow the [operation transaction contract](../wiki/references/operation-transactions.md). 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.
>
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this URL, process this source, read and file this source, batch ingest, ingest these sources.
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find everything about, research and file, go research, build a wiki on.
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation, save this analysis, keep this insight, preserve this chat result.
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.