obsidian-vault-manager

Name: obsidian-vault-manager
Author: raja-patnaik

73stars6forks

How to install obsidian-vault-manager?

raja-patnaik/obsidian-agent/obsidian-vault-manager

$npx -y skills add raja-patnaik/obsidian-agent --skill obsidian-vault-manager

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Obsidian Vault Manager
2
3	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.
4
5	## Vault Locations
6
7	Before doing anything, determine the vault paths. Check for a `CLAUDE.md` in the working directory or ask the user. Typical setup:
8
9	```
10	WORK_VAULT=~/obsidian-vaults/work
11	PERSONAL_VAULT=~/obsidian-vaults/personal
12	```
13
14	If only one vault is mounted/accessible, work with that one and note the limitation.
15
16	## Companion Plugin: kepano/obsidian-skills
17
18	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.
19
20	## Core Principles
21
22	1. Convention over configuration — every note gets proper frontmatter, lives in the right folder, and follows naming conventions
23	2. Links over folders — folders provide broad categories, but `[[wikilinks]]` and tags create the real knowledge graph
24	3. Atomic notes — each note captures one idea, one meeting, one person, one project. Split large notes.
25	4. Consistent frontmatter — every note type has a required schema. Never create notes without it.
26	5. Inbox zero — new captures go to `00-inbox/`, then get processed into the right location
27
28	## Folder Structure
29
30	Both vaults share this base structure (with vault-specific additions):
31
32	```
33	vault-root/
34	├── 00-inbox/ # Quick captures, unsorted notes
35	├── 01-daily/ # Daily notes (YYYY/MM/YYYY-MM-DD.md)
36	│ └── 2026/
37	│ └── 03/
38	├── 02-projects/ # Active projects (one folder per project)
39	│ └── project-name/
40	├── 03-areas/ # Ongoing areas of responsibility
41	├── 04-resources/ # Reference material, how-tos, articles
42	│ ├── articles/
43	│ ├── bookmarks/
44	│ └── how-tos/
45	├── 05-people/ # People notes / CRM
46	├── 06-meetings/ # Meeting notes (YYYY/MM/)
47	│ └── 2026/
48	│ └── 03/
49	├── 07-ideas/ # Brain dumps, shower thoughts, sparks
50	├── 08-archive/ # Completed/inactive items
51	├── _templates/ # Note templates
52	├── _attachments/ # Images, PDFs, files
53	└── CLAUDE.md # Agent instructions for this vault
54	```
55
56	### Work Vault Additions
57	```
58	├── 03-areas/
59	│ ├── team/ # Team-specific docs
60	│ ├── processes/ # SOPs, runbooks
61	│ └── goals/ # OKRs, quarterly goals
62	├── 09-decisions/ # Decision logs (ADRs, RFCs)
63	└── 10-standups/ # Standup notes
64	```
65
66	### Personal Vault Additions
67	```
68	├── 03-areas/
69	│ ├── health/ # Health tracking, habits
70	│ ├── finance/ # Financial notes, plans
71	│ ├── learning/ # Courses, books, study notes
72	│ └── home/ # Home projects, maintenance
73	├── 09-journal/ # Long-form reflections
74	└── 10-lists/ # Wishlists, gift ideas, recommendations
75	```
76
77	## File Naming Conventions
78
79	\| Type \| Pattern \| Example \|
80	\|------\|---------\|---------\|
81	\| Daily note \| `YYYY-MM-DD.md` \| `2026-03-22.md` \|
82	\| Meeting \| `YYYY-MM-DD-meeting-topic.md` \| `2026-03-22-meeting-sprint-planning.md` \|
83	\| Project \| `project-name.md` (index) \| `website-redesign.md` \|
84	\| Person \| `firstname-lastname.md` \| `jane-smith.md` \|
85	\| Idea \| `idea-short-title.md` \| `idea-ai-powered-garden.md` \|
86	\| Decision \| `YYYY-MM-DD-decision-title.md` \| `2026-03-22-decision-switch-to-postgres.md` \|
87	\| Resource \| `descriptive-kebab-case.md` \| `how-to-set-up-docker.md` \|
88
89	Always use lowercase kebab-case. No spaces in filenames.
90
91	## Frontmatter Schemas
92
93	Read the full schema reference

People who liked this also viewed

6 picks

Type

obsidian-vault-manager

73stars6forks

View on GitHub

How to install obsidian-vault-manager?

raja-patnaik/obsidian-agent/obsidian-vault-manager

$npx -y skills add raja-patnaik/obsidian-agent --skill obsidian-vault-manager

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Obsidian Vault Manager
2
3	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.
4
5	## Vault Locations
6
7	Before doing anything, determine the vault paths. Check for a `CLAUDE.md` in the working directory or ask the user. Typical setup:
8
9	```
10	WORK_VAULT=~/obsidian-vaults/work
11	PERSONAL_VAULT=~/obsidian-vaults/personal
12	```
13
14	If only one vault is mounted/accessible, work with that one and note the limitation.
15
16	## Companion Plugin: kepano/obsidian-skills
17
18	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.
19
20	## Core Principles
21
22	1. Convention over configuration — every note gets proper frontmatter, lives in the right folder, and follows naming conventions
23	2. Links over folders — folders provide broad categories, but `[[wikilinks]]` and tags create the real knowledge graph
24	3. Atomic notes — each note captures one idea, one meeting, one person, one project. Split large notes.
25	4. Consistent frontmatter — every note type has a required schema. Never create notes without it.
26	5. Inbox zero — new captures go to `00-inbox/`, then get processed into the right location
27
28	## Folder Structure
29
30	Both vaults share this base structure (with vault-specific additions):
31
32	```
33	vault-root/
34	├── 00-inbox/ # Quick captures, unsorted notes
35	├── 01-daily/ # Daily notes (YYYY/MM/YYYY-MM-DD.md)
36	│ └── 2026/
37	│ └── 03/
38	├── 02-projects/ # Active projects (one folder per project)
39	│ └── project-name/
40	├── 03-areas/ # Ongoing areas of responsibility
41	├── 04-resources/ # Reference material, how-tos, articles
42	│ ├── articles/
43	│ ├── bookmarks/
44	│ └── how-tos/
45	├── 05-people/ # People notes / CRM
46	├── 06-meetings/ # Meeting notes (YYYY/MM/)
47	│ └── 2026/
48	│ └── 03/
49	├── 07-ideas/ # Brain dumps, shower thoughts, sparks
50	├── 08-archive/ # Completed/inactive items
51	├── _templates/ # Note templates
52	├── _attachments/ # Images, PDFs, files
53	└── CLAUDE.md # Agent instructions for this vault
54	```
55
56	### Work Vault Additions
57	```
58	├── 03-areas/
59	│ ├── team/ # Team-specific docs
60	│ ├── processes/ # SOPs, runbooks
61	│ └── goals/ # OKRs, quarterly goals
62	├── 09-decisions/ # Decision logs (ADRs, RFCs)
63	└── 10-standups/ # Standup notes
64	```
65
66	### Personal Vault Additions
67	```
68	├── 03-areas/
69	│ ├── health/ # Health tracking, habits
70	│ ├── finance/ # Financial notes, plans
71	│ ├── learning/ # Courses, books, study notes
72	│ └── home/ # Home projects, maintenance
73	├── 09-journal/ # Long-form reflections
74	└── 10-lists/ # Wishlists, gift ideas, recommendations
75	```
76
77	## File Naming Conventions
78
79	\| Type \| Pattern \| Example \|
80	\|------\|---------\|---------\|
81	\| Daily note \| `YYYY-MM-DD.md` \| `2026-03-22.md` \|
82	\| Meeting \| `YYYY-MM-DD-meeting-topic.md` \| `2026-03-22-meeting-sprint-planning.md` \|
83	\| Project \| `project-name.md` (index) \| `website-redesign.md` \|
84	\| Person \| `firstname-lastname.md` \| `jane-smith.md` \|
85	\| Idea \| `idea-short-title.md` \| `idea-ai-powered-garden.md` \|
86	\| Decision \| `YYYY-MM-DD-decision-title.md` \| `2026-03-22-decision-switch-to-postgres.md` \|
87	\| Resource \| `descriptive-kebab-case.md` \| `how-to-set-up-docker.md` \|
88
89	Always use lowercase kebab-case. No spaces in filenames.
90
91	## Frontmatter Schemas
92
93	Read the full schema reference

People who liked this also viewed

6 picks

Type