vault-librarian
Skill0 starsChanged 5 months agoMITView on GitHub
Use whenever creating, moving, or editing notes in Christian's Obsidian vault, or when the vault risks getting messy. Triggers on 'add a note', 'save this to the vault', 'where does this go', 'organize the vault', creating any new Claude-related folder or file. Enforces PARA placement, updates the Claude Index, backlinks new notes, and appends the activity log so the vault stays honest.
In this repository9 other files it gives its agents.
- ai-brainSkill
- assumption-checkSkill
- cover-letter-loopSkill
- design-inspoSkill
- luno-osSkill
- memory-hygieneSkill
- research-to-vaultSkill
- skill-routerSkill
- telegram-bot-factorySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Place it in the right PARA folder using obsidian_write_note.
- Very specific: line 27
Backlink: add [[...]] links to related existing notes, and link the parent hub note back to it.
- Very specific: line 28
Index: if it's a Claude-related path, structural file, new folder, or new site, update 30 - Resources/Claude Index.md so the locator stays …
- Very specific: line 32
Do not rename the typo'd folders.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vault Librarian
Keeps the Obsidian vault structured instead of accumulating orphan notes.
Vault root: /Users/chanjalme/Documents/ClaudeProject/Obsedian/sample/smaple1 (typos Obsedian/smaple1 are intentional — never rename).
PARA placement rules
00 - Inbox— quick captures, undecided.10 - Projects— active, time-bound work (Luno, specific builds).20 - Areas— ongoing responsibility (Business, Learning, Dev).30 - Resources— reference, templates, the Claude Index.40 - Archive— done/inactive.50 - Zettelkasten— atomic linked ideas.Daily/—YYYY-MM-DD.mdfrom Daily Template.
Pick the most specific home. When unsure between Project and Area: time-bound → Project, evergreen → Area.
On every note create/move
- Place it in the right PARA folder using
obsidian_write_note. - Backlink: add
[[...]]links to related existing notes, and link the parent hub note back to it. - Index: if it's a Claude-related path, structural file, new folder, or new site, update
30 - Resources/Claude Index.mdso the locator stays accurate. - Log: append a one-line dated entry to the vault
Memory.mdactivity log.
Constraints
- Do not rename the typo'd folders. Do not move
~/sites/repos or anything inside~/.claude/that the harness manages. - New orphan files belong in
~/ClaudeArchive/, not loose in home.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

