vault-tend

Performs preview-gated batch maintenance across Markdown notes in an Obsidian vault.

Updated May 22, 2026
One-click install
npx skills add https://github.com/fbureau/second-brain --skill vault-tend-fbureau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vault-tend
Source: https://github.com/fbureau/second-brain/tree/main/.claude/skills/vault-tend
Command: npx skills add https://github.com/fbureau/second-brain --skill vault-tend-fbureau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time a personal knowledge vault accumulates inconsistencies: mixed languages, broken wikilinks, duplicate people and project notes, malformed frontmatter, and stale content. Fixing these by hand across hundreds of notes is slow and error-prone, and bulk edits risk destroying append-only history. ## Core Features & Use Cases - Vault-wide operations: Re-language notes to a target language, normalize frontmatter, repair broken wikilinks, deduplicate people/projects, tidy formatting, and propose archives. - Safety-first workflow: Every run follows a scope → preview → confirm → batched apply → report loop, with one Git commit per batch so changes are reversible. - Protected content rules: Never deletes notes, preserves append-only timeline entries and the English "For future Claude" preamble, and confirms every duplicate merge. - Use Case: After a Vault Health Check flags orphans and duplicates, ask to clean up the vault; the skill previews representative diffs, waits for approval, then applies fixes in small committed batches. ## Quick Start Ask the assistant to tidy up the vault and fix broken links and duplicate people notes, previewing changes before applying them.

Frequently Asked Questions about vault-tend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up and normalize an Obsidian vault at scale?▼

Use a vault maintenance pass that scans all notes, previews representative before/after diffs, and applies changes in small Git-committed batches. Operations include frontmatter normalization, wikilink repair, deduplication, and formatting cleanup.

How do I translate my entire Obsidian vault to another language?▼

The re-language operation translates note bodies into the target language while keeping frontmatter values, wikilink paths, and the English preamble verbatim. It detects each note's language and only translates notes not already in the target language.

Can bulk vault edits damage append-only history notes?▼

No, the skill enforces hard rules that protect dated timeline entries and auto-logged markers in people and decision notes, and a pre-commit hook enforces these constraints. Notes are never deleted; stale content is moved to an archive folder instead.

How are duplicate people or project notes merged safely?▼

Duplicates are found via fuzzy matching within the people and projects folders, then each proposed merge requires explicit confirmation. The richer note is kept, the other's timeline is appended, all backlinks are updated, and the loser is archived.

When should I not use a vault-wide maintenance skill?▼

Avoid it for single-note edits, which should be done directly, and for creating new synthesis or searching for information, which belong to knowledge-building and recall workflows. It is designed only for sweeping multi-note changes.