Stats
Actions
Tags
From obsidian
Searches the Obsidian vault and returns matching notes. Triggers on phrases like "find my notes on X", "what did I write about Y", "search obsidian for Z", "do I have any notes about", "find in vault", "look up in obsidian".
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian:find-notesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Searches the vault for notes matching a query.
Searches the vault for notes matching a query.
Resolve the config path dynamically, then read vault_path:
CONFIG="$(bash "${CLAUDE_PLUGIN_ROOT}/scripts/lib/resolve-config.sh")"
VAULT_PATH=$(grep '^vault_path:' "$CONFIG" | sed 's/vault_path: //')
If the resolver prints nothing (no config at $OBSIDIAN_LOCAL_MD, ${XDG_CONFIG_HOME:-$HOME/.config}/claude-obsidian/obsidian.local.md, or ${CLAUDE_PLUGIN_ROOT}/obsidian.local.md), tell the user to run /obsidian:setup first and stop.
find "$VAULT_PATH" -name "*<query>*" -type fgrep -r -l -i "<query>" "$VAULT_PATH" --include="*.md" --exclude-dir=".obsidian"grep -r -l "tags:.*<query>" "$VAULT_PATH" --include="*.md"Combine and deduplicate results. Rank by:
For each match, show:
**[[Note Title]]**
Path: Projects/Domain/Note-Title.md
Last modified: YYYY-MM-DD
Preview: ...first 2-3 relevant lines...
VAULT.md exists at the vault root, read it for vault-specific structure conventions (e.g., index files, special folders to prioritize in search)bash ${CLAUDE_PLUGIN_ROOT}/scripts/open-in-obsidian.sh <path>Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub nhangen/claude-obsidian-plugin --plugin obsidian