vault-organization

Organize and audit Obsidian vaults using the PARA taxonomy with MOC maintenance.

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill vault-organization-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-organization
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/note-taking/vault-organization
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill vault-organization-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Obsidian vaults accumulate clutter over time: duplicate notes, empty folders, stale links, and no clear structure. This Skill structures new vaults with a proven taxonomy and audits existing ones to identify bloat, consolidate duplicates, and keep navigation maps accurate. ## Core Features & Use Cases - New Vault Structuring: Proposes a PARA-based folder tree (Projects, Areas, Resources, Archive) with a top-level MOC, creating only the folders you approve. - Vault Auditing: Maps the directory tree, counts files and sizes per folder, and identifies bloat such as venvs, duplicates, and empty shell directories. - Reference Maintenance: Updates MOCs and stale path references after moves, leaving redirect stubs so existing backlinks keep working. - Use Case: Ask the assistant to audit a vault that has grown messy over a year; it reports file counts and duplicates, presents a reorganization plan, then executes the moves and patches every stale link. ## Quick Start Ask the assistant to audit my Obsidian vault and propose a PARA-based reorganization plan before making any changes.

Frequently Asked Questions about vault-organization

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

FAQPage Schema
How do I organize an Obsidian vault with PARA?

PARA divides a vault into Projects (short-lived efforts), Areas (ongoing responsibilities), Resources (reusable reference material), and Archive (completed items). Add a top-level MOC linking the four roots, and keep daily notes as capture space only.

How to clean up a messy Obsidian vault?

Start by mapping the directory tree and counting files per top-level folder to find where bulk lives. Then identify duplicates, empty shell directories, and misplaced artifacts, present the findings, and execute moves while updating MOC references.

What is a MOC in Obsidian and why use one?

A MOC (Map of Content) is an index note at a folder root linking to its key notes, acting as a table of contents. It lets both humans and agents navigate the vault quickly, but must be updated whenever notes move.

Should build artifacts and screenshots go in an Obsidian vault?

No. The vault stores durable knowledge, not repeatable build or test output. Screenshots, renders, and backups belong under an external artifacts directory like ~/Projects/<project>-artifacts/<date>/, with a pointer note left in the vault.

What happens to existing links when vault files are moved?

After structural changes, all MOC and index files are scanned for stale references and updated to the new locations. Legacy MOCs at old locations become redirect stubs so existing backlinks continue to resolve.