Skip to main content
skill CX Codex

vault-lint — Claude Code & Gemini CLI skill

vault-lint audits an Obsidian vault across five checks and returns a prioritised report with fixes you accept one at a time.

ISC ★ 102 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a claude-code
Open on GitHub

What vault-lint does

The skill walks Engineering/ notes and tests their frontmatter against the vault conventions: type has to be pattern, trap, decision or concept, and project, status, tags, created must be present too. Bad notes get listed, and a fix can be applied through obsidian_update_frontmatter one note at a time.

Next it reads the provenance block: anything above 0.5 inferred is flagged as mostly synthesised, while above 0.1 ambiguous means contradictions are still open. Stale sources come from .manifest.json at the vault root, where ingested_at is compared with file times on disk, and /wiki-ingest --force <source> refreshes them. No manifest and that whole step drops out — the other four still report.

MOC coverage compares note titles against wikilinks pulled from every note in MOCs/, with a 24-hour grace period for fresh notes, and obsidian_rag_query suggests where an uncovered note belongs. Orphan detection is left to /link-audit. Narrow the run with a folder argument or a single check.

What it helps with

  • list Engineering/ notes that miss required frontmatter fields
  • flag notes whose provenance is mostly inferred
  • re-ingest sources that changed after ingested_at
  • confirm recent notes sit in at least one MOC
  • get a prioritised health report for the vault

Example prompts for the agent

  • Run /vault-lint on the vault and show me the critical section first.
  • Only check frontmatter: /vault-lint --check frontmatter.
  • Scope the audit to /vault-lint Engineering/Patterns/.

How to install vault-lint

1Skills CLI (Vercel)

npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a claude-code

2Manually: put the files in place

~/.claude/skills/vault-lint/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vault-lint/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vault-lint

How do I install vault-lint in Claude Code?

Run npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a claude-code. The skill file lands at ~/.claude/skills/vault-lint/SKILL.md.

What does vault-lint do?

It checks five things in an Obsidian vault: required frontmatter fields, provenance drift, stale sources, MOC coverage and orphans. You get a prioritised report with suggested fixes.

What does the stale-content check need?

A .manifest.json file at the vault root, which supplies ingested_at per source. Without it the step is skipped and the rest of the audit runs as usual.

Source text

SKILL.md · ISC
---
name: vault-lint
description: >-
  Use when the user wants a health audit of the vault — stale content,
  provenance drift, frontmatter compliance, or MOC coverage gaps. Triggers
  on "lint vault", "vault health", "check vault", "stale notes", "vault
  audit", "vault quality", or "check conventions".
---

# Vault Lint

Comprehensive vault health audit. Checks five dimensions and presents a prioritized report with fix options.

## Checks

### 1. Frontmatter Compliance

Scan `Engineering/` notes for missing required frontmatter fields per VAULT_CONVENTIONS:

1. Call `obsidian_list_notes` with `subfolder: "Engineering"`.
2. For each note, call `obsidian_read_note` and check frontmatter for:
   - `type:` — must be pattern, trap, decision, or concept
   - `project:` — must be present
   - `status:` — must be present
   - `tags:` — must be a list
   - `created:` — must be a date
3. Report notes with missing or malformed fields.
4. Offer to fix with `obsidian_update_frontmatter` (one at a time, user confirms).

### 2. Provenance Drift

Find Engineering/ notes where the `provenance:` block suggests high uncertainty:

1. From the notes already read in Check 1, filter those with `provenance:` frontmatter.
2. Flag notes where `inferred` > 0.5 — these are majority-synthesized and may need source verification.
3. Flag notes where `ambiguous` > 0.1 — these have unresolved contradictions.
4. Report flagged notes with their provenance fractions.

### 3. Stale Content

If `.manifest.json` exists at vault root:

1. Read it with the `Read` tool.
2. For each entry in `sources`, check if `pages_created` or `pages_updated` notes still exist using `obsidian_read_note`.
3. If a source file's modification time on disk is newer than `ingested_at`, the derived notes may be stale.
4. Report stale notes and suggest re-ingesting with `/wiki-ingest --force <source>`.

If no `.manifest.json` exists, skip this check and note that no ingest tracking is available.

### 4. MOC Coverage

Check whether recent Engineering/ notes appear in at least one thematic MOC:

1. Call `obsidian_list_notes` with `subfolder: "MOCs"`.
2. For each MOC, call `obsidian_read_note` and extract all `[[wikilinks]]`.
3. Build a set of all notes referenced by at least one MOC.
4. Compare against the Engineering/ note list — any note not in the MOC set is uncovered.
5. Exclude notes created in the last 24 hours (grace period).
6. Report uncovered notes and suggest which MOC(s) they belong in via `obsidian_rag_query` (query the note title against MOC titles).

### 5. Orphan Check

Defer to the existing `link-audit` skill (Phase 2). Mention this in the report:
> "For orphan detection, run `/link-audit`."

## Report Format

Present findings as a prioritized summary:

```
## Vault Health Report

### Critical (fix now)
- 3 Engineering/ notes missing `type:` frontmatter
- 1 note with ambiguous provenance > 0.1

### Warning (review soon)
- 5 notes with inferred provenance > 0.5
- 2 notes with stale source material

### Info
- 8 Engineering/ notes not in any MOC
- Run `/link-audit` for orphan detection

### Stats
- Total Engineering/ notes scanned: N
- Frontmatter compliant: N/N (X%)
- Provenance tracked: N/N (X%)
- MOC coverage: N/N (X%)
```

## Arguments

- Optional scope: `/vault-lint Engineering/Patterns/`
- Optional check: `/vault-lint --check frontmatter` (run only one check)

## Tips

- Run after a batch `/wiki-ingest` to catch compliance issues early
- High `inferred` fractions aren't inherently bad — they just need periodic human review
- For large vaults, scope to a subfolder first to keep the audit manageable
- Pair with `/cross-linker` after fixing MOC coverage gaps

© thoreinstein · ISC · thoreinstein/gemini-obsidian

Similar skills

All skills for Notes, tasks and projects →

From the same set15

The whole set →
research research is a Claude Code skill that searches an Obsidian vault, reads relevant notes, and follows links to answer questions about stored knowledge. CX Codex +1 ★ 102repo stars moc-update moc-update finds the Maps of Content (MOCs) in an Obsidian vault that should link to a freshly created Engineering/ note. Fires on prompts like “update MOC” or “which MOCs”. CX Codex +1 ★ 102repo stars link-audit link-audit audits Obsidian vaults for broken wikilinks and orphaned notes. Helps repair target paths or generate new links via semantic search. CX Codex +1 ★ 102repo stars knowledge This skill finds ideas repeated across project notes and drafts a shared note in Engineering/. Use it to turn recurring project knowledge into a linked concept. CX Codex +1 ★ 102repo stars journal journal — a skill for your Obsidian daily note: it reads today's entry, appends quick logs and builds weekly or end-of-day reviews from CLI sessions. CX Codex +1 ★ 102repo stars obsidian-companion obsidian-companion connects your assistant to an Obsidian vault to edit files, inspect broken wikilinks, and run queries using local RAG. CX Codex +1 ★ 102repo stars cross-linker cross-linker finds mentions of other Obsidian notes that lack wikilinks, then sorts possible links by confidence. Use it to connect notes across a chosen folder or a wider vault scope. CX Codex +1 ★ 102repo stars wiki-ingest wiki-ingest distills external files, transcripts, and Readwise exports into structured Obsidian notes with RAG-based deduplication and source tracking. CX Codex +1 ★ 102repo stars

Project sponsors

Companies that keep this analytics open