Obsidian Vault Search
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.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill obsidian-vault-searchgit 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-search ~/.claude/skills/obsidian-vault-searchPersonal 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 Search <purpose> Raw grep on a vault is noisy. You search "API" and get 200 hits across daily notes, templates, meeting notes, and the actual design doc you wanted. Obsidian vaults are structured — frontmatter, wikilinks, folders, tags — and search should use that structure. This skill searches smart: by property, by link graph, by folder scope, not just by keyword. </purpose> ## When To Activate <triggers> - User says "find in vault", "search vault", "search obsidian" - User says "which note has...", "where did I write about..." - User says "find all meetings about...", "show notes tagged..." - User needs to locate a specific note or set of notes - Before creating a note (to check if it exists) - Any vault-level search that isn't just opening a known file </triggers> Do NOT trigger for: - Searching code repositories (use zero-in) - Web search (different skill entirely) - Single file content search (just read the file) ## Instructions ### Step 1: Classify the Search <classify> Determine what kind of search before running anything: | Request | Search Type | Method | |---------|------------|--------| | "Find note about X" | Content search | grep + frontmatter | | "All meetings with Sarah" | Property search | frontmatter scan | | "Notes tagged #project" | Tag search | frontmatter scan | | "What links to [[Note]]" | Backlink search | wikilink grep | | "Notes in Projects/ folder" | Folder search | find |
Details
- Skill name
obsidian-vault-search- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/obsidian-vault-search/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Obsidian Vault Search skill do?
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.
How do I install the Obsidian Vault Search skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill obsidian-vault-search. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Obsidian Vault Search 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.
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.
Obsidian Vault Init
62ElliotJLT/Claude-Skill-Potions
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.
Skill Gate
62ElliotJLT/Claude-Skill-Potions
Before starting any significant task, force explicit evaluation of available skills. For each potentially relevant skill, state YES/NO with reasoning. Only proceed to implementation after skills have been consciously evaluated and activated. Prevents the ~50% "coin flip" activation rate that occurs when skills are passively available but not deliberately considered.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.