Help us improve
Share bugs, ideas, or general feedback.
From obsidian-vault-management
Comprehensive vault maintenance with 5 parallel agents scanning file organization, template compliance, project status, metadata validation, and cleanup opportunities. Automatically detects scope and selects optimal path (Quick 30s, Standard 60s, Deep 120s). Use when checking vault health, finding misplaced files, validating templates, or performing weekly maintenance.
npx claudepluginhub bloknayrb/claudestuffHow this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-vault-management:vault-sweepingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Maintains large Obsidian vaults through systematic analysis across five maintenance domains: file organization, template compliance, project status, metadata validation, and cleanup opportunities. The skill uses parallel agent architecture with adaptive path selection to optimize performance based on vault changes since last sweep.
Performs extended vault cleanup: full audits, stale content scans, outdated references, content quality reviews, redundant tag removal, broken external link fixes, and template compliance checks.
Runs nightly vault maintenance: fixes broken wiki-links, detects orphan pages, syncs directory indexes, and flags stale GitHub issue tasks.
Runs vault health diagnostics in 8 categories including schema compliance, orphans, links, three-space boundaries, stale notes, MOC coherence. Quick/full/three-space modes yield FAIL/WARN/PASS reports with fixes.
Share bugs, ideas, or general feedback.
Maintains large Obsidian vaults through systematic analysis across five maintenance domains: file organization, template compliance, project status, metadata validation, and cleanup opportunities. The skill uses parallel agent architecture with adaptive path selection to optimize performance based on vault changes since last sweep.
Designed for vaults with 25,000+ files where manual maintenance is impractical and systematic validation ensures data quality and discoverability.
The skill supports dual-mode execution: Obsidian CLI commands when available, with automatic fallback to Glob/Grep/PowerShell.
Run at the start of every sweep, before launching agents:
obsidian version
overnight-orchestrator.ps1 runs when Obsidian is typically closed. The availability check must fail fast (< 2 seconds) to avoid delaying automated runs.When CLI is available, these commands replace or augment file-based detection:
| CLI Command | Replaces | Used By |
|---|---|---|
obsidian orphans format=json | Custom link-graph orphan detection | Agent 4 (Rule 21) |
obsidian unresolved format=json | Regex-based broken link scan (Rule 13) | Agent 4 |
obsidian properties file="X" format=json | Manual YAML frontmatter parsing | Agent 2 (Rules 6-9) |
obsidian files folder=X format=json | Glob-based file listing | Agent 1 (Rules 1-4) |
When CLI is unavailable (Obsidian closed, PATH not registered, timeout):
orphans and unresolved may return stale/partial results. Do not treat CLI results as authoritative for files created in the last 60 seconds.orphans, unresolved, files, properties) use the param=value syntax confirmed by Obsidian CLI docs. Verify available commands against obsidian help output — the CLI evolves between releases and command names may change.Invoke this skill when you need to:
The skill automatically activates when context suggests vault maintenance needs.
The skill intelligently selects the optimal path based on vault activity:
Best For: Daily or frequent checks, incremental maintenance Trigger: <50 files modified since last sweep Token Budget: ~2,000 tokens
Process:
99-System/Vault Sweep Log.mdOutput: Focused report on immediate problems requiring attention
Best For: Weekly maintenance, comprehensive validation Trigger: 50-300 files modified OR explicit request Token Budget: ~5,000 tokens
Process:
Output: Complete maintenance report with all priority levels
Best For: Full audits, major cleanup, post-migration validation Trigger: >300 files modified OR deep audit requested Token Budget: ~8,000 tokens
Process:
Output: Comprehensive audit with historical context and actionable roadmap
Five parallel agents scan different maintenance domains simultaneously:
Mission: Detect Type property mismatches with folder locations Checks:
03-Contacts/01-Projects/[Client]/[Project]/Emails/02-Meetings/ or project folders
Output: Misplaced files with recommended destinationsMission: Validate required YAML frontmatter fields per template Templates:
Mission: Identify projects needing status updates Checks:
Mission: Validate timestamp and tag integrity Checks:
created or updated timestampsMission: Identify cleanup opportunities Checks:
See agent-specifications.md for detailed agent prompts.
Comprehensive validation logic ensures files meet vault standards:
See validation-rules.md for complete rule definitions.
Systematic patterns identify common issues:
See detection-patterns.md for pattern specifications.
Uses MAINTENANCE template from shared infrastructure:
# Vault Maintenance Report
Generated: [timestamp]
Scope: [Quick/Standard/Deep Path]
Files Scanned: [count]
## Critical Issues (Immediate Action Required)
[Organized by category: File Org, Template, Status, Metadata, Cleanup]
## Important Issues (Action Recommended)
[Same category structure]
## Recommendations (Optional Improvements)
[Same category structure]
## Summary
- Critical: [count]
- Important: [count]
- Recommendations: [count]
- Next Sweep: [date]
See shared/output-templates.md for template details.
Works with Bryan's vault organization:
00-Inbox through 99-SystemEmails/ with tag-based organization01-Projects/[Client]/[Project]/Maintains state in 99-System/Vault Sweep Log.md:
Integrates with existing workflow:
/vault-sweep command calls this skill/track when action items generatedStores patterns for future reference:
Token Usage:
Follows standard error protocols (see shared/error-handling.md):
Pattern 1: Graceful Degradation
Pattern 2: Validation Before Processing
Pattern 4: Error Accumulation
Skill-Specific Handling:
User: "Quick vault check before I start work"
Process:
Output:
# Vault Maintenance Report
Scope: Quick Path
Files Scanned: 23
## Critical Issues
### File Organization
- [ ] email-from-john.md in 00-Inbox/ → Move to Emails/
- [ ] drpa-update.md in 01-Fleeting/ → Move to Emails/
## Summary
- Critical: 2 issues
- Next Sweep: Tonight
Time: 25 seconds
User: "Run weekly vault sweep"
Process:
Output: Full maintenance report with all categories
Time: 58 seconds
User: "I just reorganized the DRPA project folders, do a deep sweep to check everything"
Process:
01-Projects/DRPA/ (no filter)Output: Comprehensive audit with trend analysis and migration quality report
Time: 115 seconds
Uses PowerShell patterns for efficient file filtering:
Quick Path:
$lastSweep = Get-Date "2025-11-12 17:00"
Get-ChildItem -Path $vault -Recurse -File |
Where-Object {$_.LastWriteTime -gt $lastSweep}
Standard Path:
$threshold = (Get-Date).AddDays(-7)
Get-ChildItem -Path $vault -Recurse -File |
Where-Object {$_.LastWriteTime -gt $threshold}
Deep Path: No filter, scan all files
See shared/powershell-temporal-filter.md for complete patterns.
Before sweep:
obsidian version, 2s timeout) — sets mode for agentsDuring sweep:
After sweep:
Track in sweep log:
obsidian tags sort=count counts) for Pattern 10obsidian backlinks file="X") for link quality metricsThis skill ensures vault health through systematic, intelligent maintenance optimized for large-scale Obsidian environments.