Audit your Obsidian vault in Claude Code — finds stale drafts, empty folders, duplicate filenames, and incomplete files. Saves a dated report.
npx skills add https://github.com/BrianRWagner/ai-marketing-claude-code-skills --skill vault-cleanup-auditor
Runs 4 targeted checks against your Obsidian vault and saves a prioritized audit report to vault-audit/YYYY-MM-DD-audit.md. Takes under 30 seconds. No APIs, no paid services.
Run it monthly or whenever the vault starts feeling messy.
Open Claude Code and say:
Run the Vault Cleanup Auditor skill against my vault at /path/to/vault.
When this skill is invoked, follow these phases exactly.
Check whether the user has provided:
vault_path — absolute path to their Obsidian vault rootIf missing, ask:
What's the absolute path to your Obsidian vault? (e.g. /root/obsidian-vault)
Do not proceed until confirmed.
Run all 4 checks. Capture raw output from each before writing the report.
Check 1 — Stale drafts (30+ days, unposted):
VAULT="VAULT_PATH_HERE"
echo "=== CHECK 1: STALE DRAFTS ==="
find "$VAULT/content/ready-to-post" -name "*.md" -mtime +30 2>/dev/null | while read f; do
if grep -q '\*\*Posted:\*\* ❌' "$f" 2>/dev/null; then
days=$(( ($(date +%s) - $(stat -c %Y "$f")) / 86400 ))
echo "${days}d|${f##$VAULT/}"
fi
done
echo "=== END CHECK 1 ==="
Check 2 — Incomplete files (no headings, 5+ lines):
VAULT="VAULT_PATH_HERE"
echo "=== CHECK 2: INCOMPLETE FILES ==="
find "$VAULT" -name "*.md" \
-not -path "*/.git/*" \
-not -path "*/.obsidian/*" \
-not -path "*/.openclaw/*" | while read f; do
if ! grep -qE '^#{1,6} ' "$f" 2>/dev/null; then
lines=$(wc -l < "$f")
if [ "$lines" -gt 5 ]; then
echo "${lines}lines|${f##$VAULT/}"
fi
fi
done
echo "=== END CHECK 2 ==="
Check 3 — Duplicate filenames:
VAULT="VAULT_PATH_HERE"
echo "=== CHECK 3: DUPLICATE FILENAMES ==="
find "$VAULT" -name "*.md" \
-not -path "*/.git/*" \
-not -path "*/.obsidian/*" \
-not -path "*/.openclaw/*" \
-printf "%f\n" | sort | uniq -d | while read name; do
echo "DUPE:$name"
find "$VAULT" -name "$name" \
-not -path "*/.git/*" \
-not -path "*/.obsidian/*" | while read f; do
echo " PATH:${f##$VAULT/}"
done
done
echo "=== END CHECK 3 ==="
Check 4 — Empty folders:
VAULT="VAULT_PATH_HERE"
echo "=== CHECK 4: EMPTY FOLDERS ==="
find "$VAULT" -type d -empty \
-not -path "*/.git/*" \
-not -path "*/.obsidian/*" \
-not -path "*/.openclaw/*" | while read d; do
echo "${d##$VAULT/}/"
done
echo "=== END CHECK 4 ==="
3a. Create the report directory and file:
VAULT="VAULT_PATH_HERE"
DATE=$(date +%Y-%m-%d)
mkdir -p "$VAULT/vault-audit"
REPORT="$VAULT/vault-audit/${DATE}-audit.md"
echo "Report path: $REPORT"
3b. Write the report using this exact structure:
# Vault Cleanup Audit — YYYY-MM-DD
Generated: YYYY-MM-DD HH:MM
**Summary:** 🔴 [N] stale | 🟡 [N] incomplete | 🟡 [N] dupes | 🟢 [N] empty
---
## 🔴 Stale Drafts (30+ days, unposted)
- [Nd old] path/to/file.md
[cap at 15 items — add "...and N more" if over]
## 🟡 Incomplete Files (no headings, 5+ lines)
- path/to/file.md (N lines)
[cap at 15]
## 🟡 Duplicate Filenames
- **filename.md**
- path/one/filename.md
- path/two/filename.md
[cap at 15 duplicate names]
## 🟢 Empty Folders
- path/to/folder/
[cap at 15]
---
**What to do:**
- 🔴 Stale drafts: post them, delete them, or archive to `content/posted/`
- 🟡 Incomplete files: finish or trash
- 🟡 Duplicates: merge or rename the less important one
- 🟢 Empty folders: safe to delete (or keep if you're about to use them)
3c. Print the summary to terminal:
✅ Audit saved to: vault-audit/YYYY-MM-DD-audit.md
Summary:
🔴 [N] stale drafts
🟡 [N] incomplete files
🟡 [N] duplicate filenames
🟢 [N] empty folders
Before finalizing, check:
=== CHECK N === / === END CHECK N === marker. If a check produced no output, note "0 issues found" in the report — do not skip the section.vault-audit/YYYY-MM-DD-audit.md. If the write failed, report the error and provide the report content inline.Fix any failures before delivering the final output.
# Vault Cleanup Audit — 2026-03-01
Generated: 2026-03-01 08:14
**Summary:** 🔴 3 stale | 🟡 2 incomplete | 🟡 1 dupe | 🟢 2 empty
---
## 🔴 Stale Drafts (30+ days, unposted)
- [47d old] content/ready-to-post/linkedin/2026-01-12-ai-systems-post.md
- [38d old] content/ready-to-post/twitter/2026-01-21-founder-ops.md
- [31d old] content/ready-to-post/newsletter/2026-01-28-tools-roundup.md
## 🟡 Incomplete Files (no headings, 5+ lines)
- bambf/research/untitled-notes.md (23 lines)
- thinking/random-thoughts.md (11 lines)
## 🟡 Duplicate Filenames
- **README.md**
- bambf/brand/README.md
- bambf/tracking/README.md
## 🟢 Empty Folders
- content/queue/rejected/
- bambf/clients/archived/
---
**What to do:**
- 🔴 Stale drafts: post them, delete them, or archive to `content/posted/`
- 🟡 Incomplete files: finish or trash
- 🟡 Duplicates: merge or rename the less important one
- 🟢 Empty folders: safe to delete (or keep if you're about to use them)
find, grep, wc, stat, date, awkvault-audit/ inside the vault (auto-created)Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
Write, review, and edit documentation files with consistent structure, tone, and technical accuracy. Use when creating docs, reviewing markdown files, writing READMEs, updating `/docs` directories, or when user says "write documentation", "review this doc", "improve this README", "create a guide", or "edit markdown". Do NOT use for code comments, inline JSDoc, or API reference generation.
Real-time Constitution compliance checker for devflow documents. Blocks partial implementations and hardcoded secrets during file editing.
Write self-documenting code with minimal, evergreen comments that explain complex logic without describing recent changes or temporary fixes. Use this skill when writing code comments, documentation strings, explaining complex algorithms, clarifying business logic, or deciding whether code needs comments. Apply when working with any source code files where comments or documentation might be added, ensuring comments remain relevant, helpful, and focused on explaining why rather than what the code does, while preferring clear code structure and naming over excessive commenting.
Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
Draft a structured investment committee memo for PE deal approval. Synthesizes due diligence findings, financial analysis, and deal terms into a professional IC-ready document. Use when preparing for investment committee, writing up a deal, or creating a formal recommendation. Triggers on "write IC memo", "investment committee memo", "deal write-up", "prepare IC materials", or "recommendation memo".
Take brianrwagner/vault-cleanup-auditor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.