Obsidian Vault Init
Initialises an Obsidian vault for Claude Code workflows. Sets up folder structure, frontmatter conventions, templates, starter .base views, and a CLAUDE.md that describes the vault so future sessions understand it instantly. Activates on "set up obsidian", "init vault", "new vault", or first contact with an Obsidian project that has no CLAUDE.md.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill obsidian-vault-initgit clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/obsidian-vault-init ~/.claude/skills/obsidian-vault-initPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Obsidian Vault Init <purpose> The cold start problem. You open a fresh vault (or an existing one with no structure) and Claude Code has zero context — what folders exist, what templates to use, what frontmatter properties matter, how notes link together. This skill bootstraps the vault with sensible structure and leaves a map (CLAUDE.md) so every future session starts oriented, not lost. </purpose> ## When To Activate <triggers> - User says "set up obsidian", "init vault", "new vault", "bootstrap vault" - User says "make my vault work with Claude Code" - Vault exists but has no CLAUDE.md and user asks Claude to create/manage notes - User says "organise my vault" or "structure my vault" - Beginning of session where vault has no CLAUDE.md </triggers> Do NOT trigger for: - Vaults that already have a CLAUDE.md (read it instead) - Single note creation (use obsidian-note-create) - User explicitly says they don't want structure changes ## Instructions ### Step 1: Detect the Environment <detect> Before anything, figure out what you're working with: ```bash # Where is the vault? # WSL: vault is likely on Windows filesystem ls /mnt/c/Users/*/Documents/*vault* 2>/dev/null ls /mnt/c/Users/*/Obsidian* 2>/dev/null # Direct Linux/Mac ls ~/Documents/*vault* 2>/dev/null ls ~/Obsidian* 2>/dev/null # If user gave a path, use that ls "$VAULT_PATH" ``` Check what already exists:
Details
- Skill name
obsidian-vault-init- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/obsidian-vault-init/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Obsidian Vault Init skill do?
Initialises an Obsidian vault for Claude Code workflows. Sets up folder structure, frontmatter conventions, templates, starter .base views, and a CLAUDE.md that describes the vault so future sessions understand it instantly. Activates on "set up obsidian", "init vault", "new vault", or first contact with an Obsidian project that has no CLAUDE.md.
How do I install the Obsidian Vault Init skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill obsidian-vault-init. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Obsidian Vault Init popular?
It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.
Related skills
Agent Audit
62ElliotJLT/Claude-Skill-Potions
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
Battle Plan
62ElliotJLT/Claude-Skill-Potions
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Obsidian Vault Search
62ElliotJLT/Claude-Skill-Potions
Searches an Obsidian vault intelligently — combines CLI search, frontmatter filtering, content grep, and wikilink traversal. Goes beyond keyword search to find notes by property, by link, by folder, and by content. Activates on "find in vault", "search vault", "which note has", "where did I write about", or when looking for specific notes in Obsidian.
Obsidian Session Sync
62ElliotJLT/Claude-Skill-Potions
End-of-session ritual that syncs Claude Code session artifacts to an Obsidian vault. Chains breadcrumbs, retrospective, note creation, and daily driver into a single flow. Creates session notes, updates daily note, and leaves breadcrumbs. Activates on "sync to obsidian", "save session", "end session", or when user wraps up significant work in a vault-connected project.
Retrospective
62ElliotJLT/Claude-Skill-Potions
After completing a significant task or experiment, documents what worked, what failed, and key learnings. Activates when a multi-step task finishes or when user says "done", "finished", "that worked", or asks for a summary. Failed attempts get documented first - they're read more than successes.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.