agentleFS
c-ibarrac-ibarra/ObsidianKnowledgeCurator/.agents/skills/vault-search/SKILL.md

vault-search

Skill0 starsChanged 44 days agoMITView on GitHub

Use this skill when the user wants to find, retrieve, or locate notes in their Obsidian vault. Triggers include "find notes about", "search my vault for", "what do I have on", "do I have anything on".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If still empty: "No notes found about X.

    line 41
  2. Distinctive:

    Read top 3–5. Rank by: title match → recency → note type (analysis > video > article).

    line 54
  3. Very specific:

    Never surface results from dswok

    line 72
  4. Distinctive:

    If >20 results, ask for refinement before reading all

    line 73
  5. Very specific:

    Prefer obsidian search over grep/find

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vault Search Skill

Goal

Locate the most relevant notes in the vault using the obsidian CLI, rank them by relevance, and present actionable results with excerpts.

Prerequisites

pgrep -x Obsidian > /dev/null && echo "open" || echo "CLOSED"
# Read obsidian-cli skill before operating

⚠️ Never read or surface content from: dataScienceKnowledgeBase/dswok

Step 1 — Choose search strategy

Query typeCommand
Keyword / exact phraseobsidian search query="<term>" limit=10
Concept with contextobsidian search:context query="<term>" limit=5
By tagobsidian tag name="<tag>"
Recent notesobsidian recents limit=10
Folder-scopedobsidian files folder="<folder>" total
Notes with no linksobsidian orphans

For vague queries: run search:context first; if thin results, try search with synonyms.

Step 2 — Execute search

obsidian search query="<query>" limit=10

If empty results:

  1. Try a broader synonym
  2. Remove qualifiers
  3. If still empty: "No notes found about X. Do you want me to create one?"

Fallback (if search times out — Obsidian in background):

find "." \
  -name "*.md" ! -path "*/dswok/*" \
  -exec grep -il "<query>" {} \; 2>/dev/null | head -10

Step 3 — Read and rank top results

obsidian read file="<note name>"

Read top 3–5. Rank by: title match → recency → note type (analysis > video > article).

Step 4 — Present results

📄 [[Note Title]]
Path: <RootFolder>/<folder>/<file>.md
Tags: #tag1 #tag2
Excerpt: "…relevant sentence from the note…"

Max 7 results. After listing, offer:

  • Open in Obsidian: obsidian open file="<name>"
  • Synthesize the found results → skill knowledge-synthesis
  • Capture something new about this topic → skill note-capture

Constraints

  • Excerpts only in initial results — full content only if user asks
  • Never surface results from dswok
  • If >20 results, ask for refinement before reading all
  • Prefer obsidian search over grep/find

Examples

"What do I have on LangGraph?"

obsidian search query="LangGraph" limit=10
obsidian search:context query="LangGraph agents" limit=5

"Show me everything tagged #no-read-yet"

obsidian tag name="no-read-yet"

"Do I have notes on Claude Code?"

obsidian search query="Claude Code" limit=10
obsidian files folder="dataScienceKnowledgeBase/AI Engineer/Claude Code" total

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.