Code Review
polyipseity/obsidian-terminal
A skill your agent uses when reviewing PRs, code changes, or conducting code audits in obsidian-terminal.
A skill your agent uses when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps.
Install Vault Lint
$ npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thoreinstein/gemini-obsidian vault-lint --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thoreinstein/gemini-obsidian.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vault-lint .claude/skills/vault-lint && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vault-lint" agent skill from https://github.com/thoreinstein/gemini-obsidian/tree/main/skills/vault-lint into .claude/skills/vault-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-lint", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thoreinstein/gemini-obsidian/tree/main/skills/vault-lintType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thoreinstein/gemini-obsidian vault-lint --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thoreinstein/gemini-obsidian.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vault-lint .agents/skills/vault-lint && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vault-lint" agent skill from https://github.com/thoreinstein/gemini-obsidian/tree/main/skills/vault-lint into .agents/skills/vault-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-lint", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thoreinstein/gemini-obsidian vault-lint --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thoreinstein/gemini-obsidian.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vault-lint .cursor/skills/vault-lint && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vault-lint" agent skill from https://github.com/thoreinstein/gemini-obsidian/tree/main/skills/vault-lint into .cursor/skills/vault-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-lint", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thoreinstein/gemini-obsidian.git --path skills/vault-lint--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thoreinstein/gemini-obsidian vault-lint --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thoreinstein/gemini-obsidian.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vault-lint .gemini/skills/vault-lint && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vault-lint" agent skill from https://github.com/thoreinstein/gemini-obsidian/tree/main/skills/vault-lint into .gemini/skills/vault-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-lint", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thoreinstein/gemini-obsidian vault-lintInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thoreinstein/gemini-obsidian.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vault-lint .github/skills/vault-lint && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vault-lint" agent skill from https://github.com/thoreinstein/gemini-obsidian/tree/main/skills/vault-lint into .github/skills/vault-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-lint", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thoreinstein/gemini-obsidian vault-lint --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thoreinstein/gemini-obsidian.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vault-lint .opencode/skills/vault-lint && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vault-lint" agent skill from https://github.com/thoreinstein/gemini-obsidian/tree/main/skills/vault-lint into .opencode/skills/vault-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vault-lint", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vault-lint- GitHub stars
- 102
- Token cost
- ~920 tokens
- SKILL.md length
- 407 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- ISC
At a glance
A skill your agent uses when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps.
- Works in 5 steps: Frontmatter Compliance → Provenance Drift → Stale Content → …
- The user wants a health audit of the vault — stale content
- SKILL.md covers Checks, Report Format, Arguments and Tips
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vault Lint is an agent skill from thoreinstein/gemini-obsidian. 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".
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting and Test coverage. It works with Obsidian. The repository describes itself as: A Gemini CLI extension for interfacing with an Obsidian vault with local first RAG capabilities. The licence is ISC.
When your agent uses it
- The user wants a health audit of the vault — stale content
- Provenance drift
- Frontmatter compliance
- MOC coverage gaps
Example prompts
- “lint vault”
- “vault health”
- “check vault”
- “/vault-lint”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9156cba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vault Lint loads about 920 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 407 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thoreinstein/gemini-obsidian at commit 9156cba, republished under its ISC licence (© thoreinstein). 407 words, ~920 tokens.
Download SKILL.mdSave it as
.claude/skills/vault-lint/SKILL.md (or your agent's skills folder).- 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:
- Call
obsidian_list_noteswithsubfolder: "Engineering". - For each note, call
obsidian_read_noteand check frontmatter for:type:— must be pattern, trap, decision, or conceptproject:— must be presentstatus:— must be presenttags:— must be a listcreated:— must be a date
- Report notes with missing or malformed fields.
- 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:
- From the notes already read in Check 1, filter those with
provenance:frontmatter. - Flag notes where
inferred> 0.5 — these are majority-synthesized and may need source verification. - Flag notes where
ambiguous> 0.1 — these have unresolved contradictions. - Report flagged notes with their provenance fractions.
3. Stale Content
If .manifest.json exists at vault root:
- Read it with the
Readtool. - For each entry in
sources, check ifpages_createdorpages_updatednotes still exist usingobsidian_read_note. - If a source file's modification time on disk is newer than
ingested_at, the derived notes may be stale. - 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.
Show full SKILL.md (178 more words)Show less
4. MOC Coverage
Check whether recent Engineering/ notes appear in at least one thematic MOC:
- Call
obsidian_list_noteswithsubfolder: "MOCs". - For each MOC, call
obsidian_read_noteand extract all[[wikilinks]]. - Build a set of all notes referenced by at least one MOC.
- Compare against the Engineering/ note list — any note not in the MOC set is uncovered.
- Exclude notes created in the last 24 hours (grace period).
- 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-ingestto catch compliance issues early - High
inferredfractions 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-linkerafter fixing MOC coverage gaps
© thoreinstein, ISC. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/vault-lint of thoreinstein/gemini-obsidian.
Open the folder on GitHubat commit 9156cba
Compare with similar skills
Vault Lint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vault Lint this skillthoreinstein/gemini-obsidian | 102 | — | ~920 | Automated safety check: Pass | ISC | |
| Code Reviewpolyipseity/obsidian-terminal | 950 | — | ~1.6k | Automated safety check: Pass | AGPL-3.0 | |
| Django Verification Loopaffaan-m/ECC | 276k | 7 repos | ~2.9k | Automated safety check: Pass | MIT | |
| LLM Wikilewislulu/llm-wiki-skill | 655 | — | ~3.7k | Automated safety check: Pass | None | |
| Obsidian Plugin Development Guidelinesgapmiss/obsidian-plugin-skill | 190 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Obsidian Plugin Releasecrafter-station/skills | 112 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Django Verification Loop
affaan-m/ECC
Runs a phased pre-PR and pre-deploy check on a Django project: environment, linting, migrations, tests with coverage, security scans and settings review.
LLM Wiki
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
Obsidian Plugin Development Guidelines
gapmiss/obsidian-plugin-skill
Rules and references for building Obsidian plugins: ESLint rules, TypeScript practices, memory cleanup, API choices, UI standards and the community submission process.
Obsidian Plugin Release
crafter-station/skills
Release a new version of an Obsidian community plugin without forgetting steps.
Obsidian Plugin Quality
RafaelGB/Obsidian-ZettelFlow
Audit ZettelFlow against the official Obsidian plugin guidelines and the Community-hub automated review / quality score.
More from thoreinstein/gemini-obsidian
All 12 skills in this repoCross Linker
thoreinstein/gemini-obsidian
A skill your agent uses when the user wants to find and insert missing wikilinks across vault notes.
Wiki Ingest
thoreinstein/gemini-obsidian
A skill your agent uses when the user wants to ingest external sources into the vault — PDFs, markdown files, transcripts, Readwise exports, or any document.
Compound
thoreinstein/gemini-obsidian
A skill your agent uses when the user wants to promote cross-project knowledge to the global Engineering/ folder, or says "promote knowledge", "compound notes", "knowledge synthesis", or "find…
Journal
thoreinstein/gemini-obsidian
A skill your agent uses when the user wants to work with their daily note — view today's entry, add a log, do a daily review, or capture quick thoughts.
Link Audit
thoreinstein/gemini-obsidian
A skill your agent uses when the user wants to audit vault link health, find broken wikilinks, orphaned notes, or semantic clusters.
Links
thoreinstein/gemini-obsidian
A skill your agent uses when the user wants to explore connections between notes, see what links to or from a note, or says "links", "backlinks", "connections", or "graph".
Related
Works with
Categories
Questions about Vault Lint
What does Vault Lint do?
A skill your agent uses when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps. Vault Lint is an agent skill from thoreinstein/gemini-obsidian. Use when the user wants a health audit of the vault — stale content, provenance drift, frontmatter compliance, or MOC coverage gaps.
When should I use Vault Lint?
Vault Lint fits situations like: the user wants a health audit of the vault — stale content; provenance drift; frontmatter compliance; MOC coverage gaps.
How do I install Vault Lint in Claude Code?
Run `npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a claude-code`. Or copy the skill folder (skills/vault-lint in thoreinstein/gemini-obsidian) into .claude/skills/vault-lint in your project. Claude Code loads it when a task matches its description.
How do I install Vault Lint in Codex?
Run `npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a codex`. Or copy the skill folder (skills/vault-lint in thoreinstein/gemini-obsidian) into .agents/skills/vault-lint in your project. Codex loads it when a task matches its description.
Can I use Vault Lint in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thoreinstein/gemini-obsidian --skill vault-lint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vault-lint, .gemini/skills/vault-lint, .github/skills/vault-lint and .opencode/skills/vault-lint in your project.
What does Vault Lint need to run?
SKILL.md names no scripts, command-line tools or credentials: Vault Lint is instructions for the agent only.
Does Vault Lint access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vault Lint safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vault Lint use?
Vault Lint is published under the ISC licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vault Lint use?
About 920 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vault Lint?
Skills that share tags, products or a category with Vault Lint: Code Review (polyipseity/obsidian-terminal, 950 stars), Django Verification Loop (affaan-m/ECC, 276k stars), LLM Wiki (lewislulu/llm-wiki-skill, 655 stars) and Obsidian Plugin Development Guidelines (gapmiss/obsidian-plugin-skill, 190 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vault Lint?
thoreinstein (a GitHub user) maintains it in thoreinstein/gemini-obsidian, which has 102 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 31, 2026.
Source: thoreinstein/gemini-obsidian on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.