obsidian-vault-manager
Skill76 starsChanged 8 months agoMITView on GitHub
Manage, search, organize, and maintain Obsidian vaults integrated with Claude Code and Cowork. Use this skill whenever the user mentions Obsidian, vault, notes, daily journal, meeting notes, knowledge base, brain dump, note-taking, or wants to capture/organize/search/review their personal or work notes. Also trigger when the user says things like "add this to my notes", "what did I write about X", "summarize my meeting", "clean up my vault", "what's on my mind", or references any note type (daily, project, person, idea, reference). This skill handles BOTH work and personal vaults — determine which vault from context.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lensetek/SkillForgetheir own version, first seen Sep 16, 2026
- eugenepyvovarov/mcpbundler-agent-skills-marketplacetheir own version, first seen Feb 15, 2026
- eugenepyvovarov/obsidian-agent-skilltheir own version, first seen Feb 15, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- eugenepyvovarov/mcpbundler-agent-skills-marketplace★ 12same name
- eugenepyvovarov/obsidian-agent-skill★ 10same name
- lensetek/SkillForge★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
29 rules. 0 are common, 19 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Before doing anything, determine the vault paths.
- Distinctive: line 20
If only one vault is mounted/accessible, work with that one and note the limitation.
- Distinctive: line 95
Always use lowercase kebab-case.
- Very specific: line 99
Read the full schema reference at: references/frontmatter-schemas.md
- Very specific: line 211
Place in 00-inbox/ if unsure of final location, or directly in the correct folder
- Very specific: line 212
Add [[wikilinks]] to related notes where they exist
- Distinctive: line 213
Update the daily note with a link to the new note
- Distinctive: line 217
When asked to "process inbox" or "clean up":
- Very specific: line 219
Read all files in 00-inbox/
- Distinctive: line 224
Add backlinks from related notes
- Distinctive: line 225
Update daily note if relevant
- Distinctive: line 230
When asked for a daily review or "what's on my plate":
- Distinctive: line 232
Read today's daily note (create if missing)
- Very specific: line 234
Check 06-meetings/ for today's meetings
- Distinctive: line 235
Look for notes modified in the last 24 hours
- Distinctive: line 236
Check for overdue action items across meeting notes
- Distinctive: line 250
When the user asks "what do I know about X" or "find notes about Y":
- Distinctive: line 265
Use grep/glob to search file contents and frontmatter
- Distinctive: line 266
Search filenames for matches
- Distinctive: line 267
Search tags and aliases
- Distinctive: line 272
If asked to synthesize, create a summary note linking to all sources
- Distinctive: line 276
Run these checks when asked to "maintain" or "clean up" the vault:
- Very specific: line 290
People: Always link with [[firstname-lastname]]
- Very specific: line 291
Projects: Always link with [[project-name]]
- Very specific: line 294
Tags: Use hierarchical tags: #project/active, #meeting/sprint, #idea/seed
- Very specific: line 298
When creating a new note, read the appropriate template from _templates/ and populate it.
- Very specific: line 304
All active projects: WHERE type = "project" AND status = "active"
- Distinctive: line 309
When the user asks for a query, write it in Dataview DQL syntax and suggest where to place it.
- Distinctive: line 313
Always check which vault: before writing. If ambiguous, ask.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Obsidian Vault Manager
You are an intelligent assistant for managing Obsidian vaults. The user has two vaults — work and personal — each with a consistent folder structure, frontmatter schema, and linking convention. Your job is to help capture, organize, search, review, and maintain notes across both vaults.
Vault Locations
Before doing anything, determine the vault paths. Check for a CLAUDE.md in the working directory or ask the user. Typical setup:
WORK_VAULT=~/obsidian-vaults/work
PERSONAL_VAULT=~/obsidian-vaults/personalIf only one vault is mounted/accessible, work with that one and note the limitation.
Companion Plugin: kepano/obsidian-skills
This skill works alongside Kepano's official obsidian-skills plugin (https://github.com/kepano/obsidian-skills), which handles Obsidian's file formats — markdown syntax, wikilinks, embeds, callouts, properties, Bases, JSON Canvas, and the Obsidian CLI. If that plugin is installed (check for obsidian-markdown, obsidian-bases, json-canvas, obsidian-cli skills), defer to it for format-level questions and use the obsidian-cli skill's commands (obsidian read, obsidian create, obsidian search, obsidian tasks, obsidian tags) when interacting with a running Obsidian instance. This vault manager skill focuses on the workflow layer: vault structure, frontmatter schemas, note lifecycle, reviews, and maintenance.
Core Principles
- Convention over configuration — every note gets proper frontmatter, lives in the right folder, and follows naming conventions
- Links over folders — folders provide broad categories, but
[[wikilinks]]and tags create the real knowledge graph - Atomic notes — each note captures one idea, one meeting, one person, one project. Split large notes.
- Consistent frontmatter — every note type has a required schema. Never create notes without it.
- Inbox zero — new captures go to
00-inbox/, then get processed into the right location
Folder Structure
Both vaults share this base structure (with vault-specific additions):
vault-root/
├── 00-inbox/ # Quick captures, unsorted notes
├── 01-daily/ # Daily notes (YYYY/MM/YYYY-MM-DD.md)
│ └── 2026/
│ └── 03/
├── 02-projects/ # Active projects (one folder per project)
│ └── project-name/
├── 03-areas/ # Ongoing areas of responsibility
├── 04-resources/ # Reference material, how-tos, articles
│ ├── articles/
│ ├── bookmarks/
│ └── how-tos/
├── 05-people/ # People notes / CRM
├── 06-meetings/ # Meeting notes (YYYY/MM/)
│ └── 2026/
│ └── 03/
├── 07-ideas/ # Brain dumps, shower thoughts, sparks
├── 08-archive/ # Completed/inactive items
├── _templates/ # Note templates
├── _attachments/ # Images, PDFs, files
└── CLAUDE.md # Agent instructions for this vaultWork Vault Additions
├── 03-areas/
│ ├── team/ # Team-specific docs
│ ├── processes/ # SOPs, runbooks
│ └── goals/ # OKRs, quarterly goals
├── 09-decisions/ # Decision logs (ADRs, RFCs)
└── 10-standups/ # Standup notesPersonal Vault Additions
├── 03-areas/
│ ├── health/ # Health tracking, habits
│ ├── finance/ # Financial notes, plans
│ ├── learning/ # Courses, books, study notes
│ └── home/ # Home projects, maintenance
├── 09-journal/ # Long-form reflections
└── 10-lists/ # Wishlists, gift ideas, recommendationsFile Naming Conventions
| Type | Pattern | Example |
| Daily note | YYYY-MM-DD.md | 2026-03-22.md |
| Meeting | YYYY-MM-DD-meeting-topic.md | 2026-03-22-meeting-sprint-planning.md |
| Project | project-name.md (index) | website-redesign.md |
| Person | firstname-lastname.md | jane-smith.md |
| Idea | idea-short-title.md | idea-ai-powered-garden.md |
| Decision | YYYY-MM-DD-decision-title.md | 2026-03-22-decision-switch-to-postgres.md |
| Resource | descriptive-kebab-case.md | how-to-set-up-docker.md |
Always use lowercase kebab-case. No spaces in filenames.
Frontmatter Schemas
Read the full schema reference at: references/frontmatter-schemas.md
Here's a quick summary of required fields per type:
Every Note (universal fields)
---
type: daily | meeting | project | person | idea | resource | decision | area | standup | journal | list
created: YYYY-MM-DDTHH:MM
modified: YYYY-MM-DDTHH:MM
tags: []
aliases: []
---Daily Note
type: daily
created: 2026-03-22T08:00
modified: 2026-03-22T18:00
tags: [daily]
energy: high | medium | low
mood: great | good | okay | rough
vault: work | personalMeeting Note
type: meeting
created: 2026-03-22T10:00
modified: 2026-03-22T10:45
tags: [meeting, sprint-planning]
attendees: ["[[jane-smith]]", "[[bob-jones]]"]
project: "[[website-redesign]]"
status: upcoming | in-progress | completed
action-items: []
vault: workProject
type: project
created: 2026-01-15T09:00
modified: 2026-03-22T14:00
tags: [project, active]
status: active | on-hold | completed | cancelled
priority: p0 | p1 | p2 | p3
start-date: 2026-01-15
target-date: 2026-06-30
owner: "[[jane-smith]]"
stakeholders: []
vault: workPerson
type: person
created: 2026-03-22T09:00
modified: 2026-03-22T09:00
tags: [person]
company: ""
role: ""
relationship: colleague | manager | report | client | friend | family | acquaintance
last-contact: 2026-03-22
vault: work | personalIdea / Brain Dump
type: idea
created: 2026-03-22T03:00
modified: 2026-03-22T03:00
tags: [idea]
status: seed | exploring | developing | parked | executed
energy: high | medium | low
related: []
vault: work | personalResource / Reference
type: resource
created: 2026-03-22T12:00
modified: 2026-03-22T12:00
tags: [resource]
source: ""
url: ""
category: article | book | video | tool | how-to | recipe | bookmark
rating: 1-5
vault: work | personalDecision Log
type: decision
created: 2026-03-22T15:00
modified: 2026-03-22T15:00
tags: [decision]
status: proposed | accepted | deprecated | superseded
decision-makers: []
impact: high | medium | low
superseded-by: ""
vault: workOperations
Capturing a New Note
- Determine the note type from context
- Determine the correct vault (work vs personal)
- Generate proper frontmatter using the schema
- Place in
00-inbox/if unsure of final location, or directly in the correct folder - Add
[[wikilinks]]to related notes where they exist - Update the daily note with a link to the new note
Processing the Inbox
When asked to "process inbox" or "clean up":
- Read all files in
00-inbox/ - For each note:
- Verify/fix frontmatter
- Determine correct folder based on
typefield - Move to the correct location
- Add backlinks from related notes
- Update daily note if relevant
- Report what was moved and where
Daily Review
When asked for a daily review or "what's on my plate":
- Read today's daily note (create if missing)
- Scan
02-projects/for active projects with upcoming deadlines - Check
06-meetings/for today's meetings - Look for notes modified in the last 24 hours
- Check for overdue action items across meeting notes
- Present a summary with links
Weekly Review
- Summarize the week's daily notes
- List completed action items
- Surface stale projects (no modification in 14+ days)
- Identify orphan notes (no backlinks)
- Suggest notes to archive
- Review
07-ideas/for seeds worth developing
Search & Synthesis
When the user asks "what do I know about X" or "find notes about Y":
If QMD is available (check with command -v qmd), use it for intelligent search:
qmd query -c <collection> "<user's question>" --json— hybrid search with reranking (best quality)qmd search -c <collection> "<keywords>"— fast BM25 keyword search for exact termsqmd vsearch -c <collection> "<concept>"— semantic vector search for fuzzy/conceptual queriesqmd get "<path>"— retrieve a specific document by path
QMD combines keyword matching, semantic similarity, and LLM reranking to find notes even when the user's phrasing doesn't match the exact words in their notes. Use qmd query as the default; fall back to qmd search for exact keyword lookups.
Collection names match vault names: -c work for work vault, -c personal for personal vault.
If QMD is not available, fall back to:
- Use grep/glob to search file contents and frontmatter
- Search filenames for matches
- Search tags and aliases
Then, in either case:
- Present results grouped by type with relevant excerpts
- If asked to synthesize, create a summary note linking to all sources
Vault Maintenance
Run these checks when asked to "maintain" or "clean up" the vault:
- Broken links: Find
[[wikilinks]]that don't resolve to files - Missing frontmatter: Find .md files without proper YAML frontmatter
- Orphan notes: Notes with no incoming links
- Stale notes: Notes not modified in 90+ days that aren't archived
- Duplicate detection: Notes with very similar titles or content
- Tag cleanup: Find inconsistent or unused tags
- Filename violations: Files not following naming conventions
Report findings and offer to fix them.
Linking Conventions
- People: Always link with
[[firstname-lastname]] - Projects: Always link with
[[project-name]] - Meetings: Link from daily notes with
[[YYYY-MM-DD-meeting-topic]] - Cross-vault: Prefix with vault name in prose: "see work vault: [[project-name]]"
- Tags: Use hierarchical tags:
#project/active,#meeting/sprint,#idea/seed
Template Usage
When creating a new note, read the appropriate template from _templates/ and populate it. Templates are provided in references/templates.md. If the template folder doesn't exist yet, create it with the standard templates.
Working with Dataview
Notes are structured to be Dataview-compatible. Common queries the user might want:
- All active projects:
WHERE type = "project" AND status = "active" - This week's meetings:
WHERE type = "meeting" AND created >= date(today) - dur(7 days) - People I haven't contacted in 30 days:
WHERE type = "person" AND last-contact <= date(today) - dur(30 days) - Ideas with high energy:
WHERE type = "idea" AND energy = "high"
When the user asks for a query, write it in Dataview DQL syntax and suggest where to place it.
Important Behaviors
- Always check which vault before writing. If ambiguous, ask.
- Never overwrite existing notes without confirmation. Append or create new.
- Preserve existing content — when fixing frontmatter, don't touch the body.
- Timestamp updates — always update the
modifiedfield when editing a note. - Daily note as hub — the daily note should link to everything created that day.
- Be proactive — if you notice broken links or missing frontmatter while doing something else, mention it.
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.

