vault-cleanup-auditor — Claude Code skill: audit your Obsidian vault

What vault-cleanup-auditor does

Four checks run against the vault. The first looks in content/ready-to-post for drafts older than 30 days that still carry the **Posted:** ❌ marker. The second picks out .md files over five lines with no heading at all. The third groups files that share a name across folders, the fourth lists directories with nothing in them. The .git, .obsidian and .openclaw trees are skipped.

If you have not named the vault, the skill asks for its absolute path before doing anything. Checks go through find, grep, wc and stat, and the report is written to vault-audit/YYYY-MM-DD-audit.md — the folder is created along the way. It holds four sections marked by severity plus a short list of next moves: publish, delete, move to content/posted/, finish, or rename the weaker copy. Each section stops at 15 entries and rolls the rest into an “...and N more” line.

You need Claude with bash access and the usual Unix tools: find, grep, wc, stat, date, awk. Read access to the vault, write access to vault-audit/ inside it. No APIs, nothing paid. The duplicate check leans on find -printf, which is a GNU findutils extension, so on macOS and BSD systems that call will not behave as intended.