Audit an Obsidian vault before cleanup or reorganization, with broken-link evidence, metadata and attachment checks, a reversible change manifest, and verification.
A vault can feel tidy while links point at the wrong copy of a note, properties drift into incompatible shapes, or an attachment cleanup quietly removes files that canvases and plugins still need. This skill starts with a read-only inventory and treats every orphan, duplicate, and unused file as a question to resolve, not permission to delete.
It maps note identity and link resolution, reviews properties and tags, separates missing attachments from merely unreferenced ones, and checks plugin and external path dependencies before proposing a change. The result is a severity-ranked audit plus an ordered change manifest with preconditions, verification, and rollback for every batch. A bundled Python tool produces a deterministic local inventory without third-party packages or network access.
Use it for periodic vault maintenance, a folder or naming migration, metadata cleanup, duplicate-note triage, or verification after a move. It does not edit the vault by default, execute community plugins, assume Sync is a backup, or claim Obsidian and plugin checks ran when they did not.
Input
Audit this vault before I move Projects into Areas. It has Projects/Plan.md and Archive/Plan.md, and many notes use [[Plan]] without a path. Obsidian automatic link updates are enabled, but a publishing script also reads the old Projects paths. Give me the safe change sequence; do not edit yet.
Output
A plan-migration verdict; an inventory of ambiguous and path-qualified links; a decision queue for canonical note identities; the publishing-script dependency; a batch manifest that separates identity fixes from moves; checkpoint, diff, link-resolution, publish, and rollback checks without claiming any move ran.
Input
Review this team vault. Some notes use status: done, some use status: [done], and older notes use tag and alias instead of tags and aliases. Dataview and Bases views depend on status, owner, and review_date. We want one schema but have no migration checklist.
Provide the vault folder or a bounded export, the maintenance goal, any folders to exclude, and the naming, folder, link, property, or tag conventions you want to preserve. Mention plugins, scripts, published URLs, or other tools that depend on note paths. The skill audits first, labels coverage and uncertainty, and returns findings plus a reversible change manifest. It edits files only after explicit approval of a specific batch and a recoverable checkpoint.
A local vault folder is best. A file tree, selected notes, or a prior inventory can support a scoped review when the full vault cannot be shared.
The problem to solve and any folder, naming, link, property, tag, archive, or retention conventions that should remain in force. Unknown choices can stay explicit.
Backup or version-control state plus any plugins, templates, scripts, published pages, or external apps that depend on paths or metadata. Required before broad or destructive changes.
Required only for the bundled read-only inventory script. It uses the standard library and does not need network access or third-party packages.
SKILL.md; read-only Obsidian vault inventory script; link, metadata, attachment, graph, severity, change-manifest, verification, and rollback rubric; Agent Skills interface metadata
No reviews yet.
Output
A property-shape and deprecated-key inventory; affected query and template dependencies; canonical-schema decisions that still need an owner; a staged migration with exception handling; sample before-and-after records; query, count, and rollback verification for each batch.
Input
This vault has 8,000 notes and 3,000 attachments. Find broken links, orphan notes, and unused files, then tell me what can be archived or deleted. Daily notes, templates, canvases, and a podcast workflow may reference files outside normal Markdown links. Audit only.
Output
A scoped audit that separates missing from unreferenced attachments, labels plugin and canvas blind spots, exempts expected note classes, prioritizes broken references, and produces archive and deletion review queues. No file is called safe to delete without ownership, dependency, checkpoint, and restore evidence.
Creator
Mmiravo73
