agentleFS
chipoto69chipoto69/claude-skills/vaultage-search/SKILL.md

vaultage-search

Skill2 starsChanged 10 months agoMITView on GitHub

Search the Obsidian vault using semantic embeddings or SQL queries on frontmatter. Set your vault path via environment variable: Options: - --query: Search query text - --n-results: Number of results (default 10) - --folder: Filter to specific folder - --where: JSON filter for metadata Available columns: path, folder, filename, title, status, priority, due, tags, created, modified The search scripts require: - Python 3.10+ - sqlite-vec or chromadb for embeddings - sentence-transformers for embedding generation Install dependencies:

  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search the Obsidian vault using semantic embeddings or SQL queries on frontmatter.

    line 3

≈ “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

Vaultage Search Skill

Search the Obsidian vault using semantic embeddings or SQL queries on frontmatter.

Configuration

Set your vault path via environment variable:

export VAULTAGE_PATH="$HOME/Documents/Vaultage"  # Customize to your vault location

Trigger Phrases

  • "search vault for"
  • "find in vaultage"
  • "query vault notes"
  • "semantic search"

Usage

Semantic Search (embeddings-based)

python "$VAULTAGE_PATH/.claude/skills/vault-search/scripts/search.py" --query "your search query" --n-results 10

Options:

  • --query: Search query text
  • --n-results: Number of results (default 10)
  • --folder: Filter to specific folder
  • --where: JSON filter for metadata

SQL Query (frontmatter database)

python "$VAULTAGE_PATH/.claude/skills/vault-search/scripts/dataview.py" "SELECT path, title FROM notes WHERE status = 'active' ORDER BY modified DESC LIMIT 20"

Available columns: path, folder, filename, title, status, priority, due, tags, created, modified

Rebuild Index

python "$VAULTAGE_PATH/.claude/skills/vault-search/scripts/index.py"

Setup

The search scripts require:

  • Python 3.10+
  • sqlite-vec or chromadb for embeddings
  • sentence-transformers for embedding generation

Install dependencies:

pip install chromadb sentence-transformers pyyaml

PARA Structure

  • 00_Inbox: Unprocessed items
  • 01_Projects: Active projects with deadlines
  • 02_Areas: Ongoing responsibilities
  • 03_Resources: Reference materials
  • 04_Archive: Completed/inactive items

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.