semantic-search — Claude Code skill for note search
The semantic-search Claude Code skill searches an Obsidian vault by meaning using local embeddings. It runs for finding related notes or recalling what you wrote about a topic.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill semantic-search -a claude-codeWhat semantic-search does
The skill finds notes in an Obsidian vault by meaning rather than relying on matching keywords. It creates embeddings with the local all-MiniLM-L6-v2 model, so searches make no API calls. search-vault.js runs queries; embed-vault.js builds the index and refreshes it after vault changes.
Installation and indexing use bash and node. The setup script takes the vault path: bash install.sh --target <vault>. Paths listed in index-deny.json are filtered out during indexing and checked again during searches. Without that file, both scripts process the entire vault; if the file cannot be read or parsed, they exit with an error.
What it helps with
- find a note by meaning instead of exact keywords
- locate notes covering a related subject
- refresh the index after vault edits
- keep selected folders out of search
Example prompts for the agent
- Use
/searchto find notes about local embeddings. - Use
/searchto locate related Obsidian setup notes. - Use
/searchto recall what I wrote about semantic search.
How to install semantic-search
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill semantic-search -a claude-code2Manually: put the files in place
~/.claude/skills/semantic-search/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/semantic-search/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill semantic-search -a codex2Manually: put the files in place
.agents/skills/semantic-search/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill semantic-search -a cursor2Manually: put the files in place
.cursor/skills/semantic-search/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/semantic-search2Manually: put the files in place
.github/skills/semantic-search/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill semantic-search -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/semantic-searchManually: put the files in place
.devin/skills/semantic-search/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill semantic-search -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about semantic-search
How do I install semantic-search in Claude Code?
Run npx skills add wrg32786/aigent-os --skill semantic-search -a claude-code. The skill installs at ~/.claude/skills/semantic-search/SKILL.md.
What does semantic-search do?
It searches an Obsidian vault by meaning with the local all-MiniLM-L6-v2 model. Queries use embeddings generated from the notes.
How can I exclude confidential notes from search?
Copy index-deny.example.json to index-deny.json and add vault-relative folder paths under deny_prefixes. Run embed-vault.js again to purge files from those folders that were already indexed.
Source text
SKILL.md · MIT
--- name: semantic-search description: "Search vault notes by meaning with local embeddings. Use when finding similar notes, searching notes semantically, or recalling what you wrote about." trigger: /search --- # Vault Semantic Search Search the Obsidian vault by meaning, not just keywords. Uses local `all-MiniLM-L6-v2` model — no API calls, no data leaves your machine. ## Usage ```bash # Search by meaning node daemons/semantic-search/search-vault.js "your query here" # Re-index (run after significant vault changes) node daemons/semantic-search/embed-vault.js # Re-index only changed files node daemons/semantic-search/embed-vault.js --changed-only ``` ## Setup ```bash bash install.sh --target <vault> # installs or repairs the dependencies safely cd daemons/semantic-search && node embed-vault.js # Initial index (~30 seconds) ``` ## Confidential-class deny list If your vault also holds client work, deal notes, or anything under NDA, keep it out of the index: ```bash cd daemons/semantic-search cp index-deny.example.json index-deny.json # then edit index-deny.json and list your own folders ``` Each entry in `deny_prefixes` is a vault-relative path prefix, matched case-insensitively and with either slash style. `embed-vault.js` drops matching files before they are embedded, so their text never reaches `embeddings.json` (which stores note excerpts in plaintext). `search-vault.js` re-checks the same list at query time, so an index built before you added a prefix still can't return one. Only `index-deny.example.json` is tracked by git. Your `index-deny.json` is gitignored, because the names of your confidential folders are themselves confidential. With no `index-deny.json` at all, both scripts index and search everything and print a notice on stderr saying so. If the file exists but can't be read or parsed, they exit non-zero instead of falling back to an unfiltered index. Add a prefix the same session confidential material enters your vault, then re-run `embed-vault.js`: it also purges anything already indexed under a newly added prefix.
© wrg32786 · MIT · wrg32786/aigent-os