Agent skill

Enable Semantic Search

by davekilleen in davekilleen/Dex

Turn on local AI-powered semantic (meaning-based) search over the vault, with smart collection discovery.

MITAuto-check: notesData & Analytics

Install Enable Semantic Search

skills CLI
$ npx skills add davekilleen/Dex --skill enable-semantic-search -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davekilleen/Dex enable-semantic-search --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davekilleen/Dex.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/enable-semantic-search .claude/skills/enable-semantic-search && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
enable-semantic-search
GitHub stars
494
Token cost
~4.5k tokens
SKILL.md length
846 words
Files
1
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Turn on local AI-powered semantic (meaning-based) search over the vault, with smart collection discovery.

  • Works in 9 steps: Explain What We're Installing → Get User Consent → Install Dependencies → …
  • The user says enable semantic search
  • SKILL.md covers What You're Enabling, Pre-Flight Checks, Step 1: Explain What We're… and Step 2: Get User Consent, plus 11 more sections
  • Calls brew, bun and node; reaches bun.sh

What it does

Enable Semantic Search is an agent skill from davekilleen/Dex. Turn on local AI-powered semantic (meaning-based) search over the vault, with smart collection discovery. Use when the user says 'enable semantic search', 'search by meaning', 'set up QMD', or search keeps missing obvious matches. Not for scraping the web; use scrape.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Data & Analytics, covering Web scraping. It works with Model Context Protocol. The repository describes itself as: Your AI Chief of Staff — a personal operating system starter kit that adapts to your role. No coding required. The licence is MIT.

When your agent uses it

  • The user says enable semantic search
  • Search by meaning
  • Search keeps missing obvious matches

Example prompts

  • “enable semantic search”
  • “search by meaning”
  • “set up QMD”
  • “/enable-semantic-search”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Explain What We're Installing
  2. Get User Consent
  3. Install Dependencies
  4. Download Models
  5. 5: Register the QMD MCP Server
  6. Smart Collection Discovery (THE CONCIERGE)
  7. Configure MCP Server
  8. Create Availability Check
  9. Show Success Summary

What it can do on your machine

Read from SKILL.md and the folder at commit d0ffc6b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • brew
    • bun
    • node
    • curl
    • bash
    • python3
    • just
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • bun.sh

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Enable Semantic Search loads about 4.5k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 846 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePipes a well-known installer script into a shellSKILL.md:139
    curl -fsSL https://bun.sh/install | bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davekilleen/Dex at commit d0ffc6b, republished under its MIT licence (© davekilleen). 846 words, ~4,465 tokens.

Download SKILL.mdSave it as .claude/skills/enable-semantic-search/SKILL.md (or your agent's skills folder).
name
enable-semantic-search
description
Turn on local AI-powered semantic (meaning-based) search over the vault, with smart collection discovery. Use when the user says 'enable semantic search', 'search by meaning', 'set up QMD', or search keeps missing obvious matches. Not for scraping the web; use `scrape`.
<!-- Generated from `.claude/skills/enable-semantic-search/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. -->

Set up local AI-powered semantic search for your vault. This is a concierge experience — it analyzes your vault, discovers what collections make sense, and creates a tailored search setup.

What You're Enabling

Semantic search finds content by meaning, not just keywords:

  • Search "product-led growth" → finds notes saying "PLG", "self-serve motion", "freemium adoption"
  • Search "customer churn" → finds notes about "retention problems", "users leaving", "cancellation patterns"

Your skills (/daily-plan, /meeting-prep, /triage, etc.) automatically use semantic search when available, finding more relevant context than keyword matching alone.

Pre-Flight Checks

Run these checks before proceeding:

bash
# Check if qmd is already installed
which qmd

# Check if Bun is available (required)
which bun

# macOS only: Check SQLite via Homebrew
brew list sqlite 2>/dev/null && echo "SQLite OK" || echo "Need: brew install sqlite"

# Check available disk space (need ~2.5GB)
df -h ~ | tail -1

If qmd is already installed, run qmd status to check existing setup. If collections already exist, skip to the Collection Health Check section at the bottom.

Step 1: Explain What We're Installing

Present this to the user:

═══════════════════════════════════════════════════════════════════════
                    SEMANTIC SEARCH FOR YOUR VAULT
═══════════════════════════════════════════════════════════════════════

What is this?
─────────────
Right now, finding notes requires knowing the exact words used.
Search "product-led growth" — won't find notes saying "PLG" or
"self-serve motion".

Semantic search understands meaning, not just keywords. It finds
conceptually related content even when terminology differs.


How does it work?
─────────────────
Your notes get converted to "embeddings" — mathematical
representations of meaning. When you search, your query becomes
an embedding too. The system finds notes whose meaning is close
to your query's meaning.

Think of it like: instead of matching letters, we're matching ideas.


What gets installed?
────────────────────
Three small AI models run locally on your machine:

  MODEL                      PURPOSE                    SIZE
  ─────────────────────────────────────────────────────────────
  EmbeddingGemma-300M        Converts text to meaning   ~300MB
                             vectors. The core
                             "understanding" model.

  Qwen3-Reranker-0.6b       Re-orders results by       ~640MB
                             true relevance. Improves
                             result quality.

  QMD-Query-Expansion-1.7B   Expands your search to     ~1.1GB
                             include related terms.
                             "PLG" → also searches
                             "product-led", "freemium"

  Total: ~2GB one-time download


Privacy & Security
──────────────────
- Everything runs locally — your notes never leave your machine
- No API keys required
- No cloud services
- Models downloaded from HuggingFace (open source)
- Index stored in ~/.cache/qmd/ (not in your vault)


What changes in your workflow?
──────────────────────────────
Enabling semantic search silently upgrades these skills:

  /daily-plan    — Enriches meeting prep with thematically
                   related past discussions

  /meeting-prep  — Discovers past discussions related by
                   meaning, not just name matching

  /triage        — Matches inbox items to goals by meaning,
                   catches semantic duplicates

  Person Lookup  — Finds "the VP of Sales mentioned..." even
                   without a name

  Search & Recall — All vault searches use hybrid retrieval
                    (BM25 + vectors + LLM reranking)


System Requirements
───────────────────
  ~2.5GB disk space (for models + index)
  macOS: Homebrew SQLite required (brew install sqlite)
  Bun runtime (will install if missing)

Ask: "Ready to enable semantic search? This will download ~2GB of models. [Y/n]"

If no, exit gracefully: "No problem. Run /enable-semantic-search anytime."

Step 3: Install Dependencies

bash
# Install Bun if missing
if ! command -v bun &> /dev/null; then
    echo "Installing Bun runtime..."
    curl -fsSL https://bun.sh/install | bash
fi

# macOS: Install SQLite if missing
if [[ "$OSTYPE" == "darwin"* ]]; then
    if ! brew list sqlite &> /dev/null; then
        echo "Installing SQLite via Homebrew..."
        brew install sqlite
    fi
fi

# Install qmd globally
echo "Installing qmd..."
bun install -g github:tobi/qmd

Step 4: Download Models

bash
echo "Downloading AI models (~2GB)..."
echo "This happens once. Future searches are instant."
echo ""
echo "Models downloading:"
echo "  EmbeddingGemma-300M  — Converts text to meaning vectors"
echo "  Qwen3-Reranker-0.6b  — Improves result relevance"
echo "  QMD-Query-Expansion   — Expands searches with related terms"
echo ""

# Trigger model download with a simple embed operation
cd "$VAULT_PATH" && qmd embed --help 2>/dev/null || true

Step 4.5: Register the QMD MCP Server

qmd is intentionally NOT pre-registered in .mcp.json — a registered server whose binary is missing shows the user a failing MCP server every session. Now that qmd is installed, add the registration to the vault's .mcp.json:

bash
python3 - <<'EOF'
import json, pathlib
p = pathlib.Path(".mcp.json")
cfg = json.loads(p.read_text()) if p.exists() else {"mcpServers": {}}
cfg.setdefault("mcpServers", {})["qmd"] = {"command": "qmd", "args": ["mcp"]}
p.write_text(json.dumps(cfg, indent=2) + "\n")
print("qmd registered in .mcp.json")
EOF

Tell the user to restart their coding harness (Claude Code/Cursor) after setup completes so the new MCP server is picked up.

Step 5: Smart Collection Discovery (THE CONCIERGE)

This is what makes Dex's semantic search better than generic indexing. Instead of dumping everything into one blob, we analyze the vault and create purpose-built collections.

Run the Vault Scanner

Execute the vault scanner script to discover collection candidates:

bash
node "$VAULT_PATH/.scripts/semantic-search/scan-vault.cjs"

The scanner returns a JSON structure like:

json
{
  "candidates": [
    {
      "name": "people",
      "path": "05-Areas/People",
      "glob": "**/*.md",
      "fileCount": 23,
      "context": "Person pages with meeting history, relationship notes, action items, and role context",
      "benefit": "Person lookup finds references by role/title, not just name",
      "example": "Search 'VP of Sales' finds the person even if their name isn't mentioned"
    },
    {
      "name": "accounts",
      "path": "05-Areas/Companies",
      "glob": "**/*.md",
      "fileCount": 8,
      "context": "Company and account pages with deal status, relationship notes, and interaction history",
      "benefit": "Deal prep pulls account-specific context without inbox noise",
      "example": "Search 'renewal risk' finds accounts with churn signals"
    }
  ],
  "skipped": [
    {
      "name": "career",
      "reason": "Folder not set up (run /career-setup)",
      "path": "05-Areas/Career"
    }
  ],
  "totalFiles": 156,
  "totalCandidates": 6
}
Present Discovery Results

Format the scanner output as a concierge recommendation:

I scanned your vault and found candidates for [N] smart collections:

  COLLECTION     FILES   WHAT IT ENABLES
  ─────────────────────────────────────────────────────────────────
  people         23      Person lookup finds references by
                         role/title, not just name. Search
                         "VP of Sales" finds the person even
                         if their name isn't mentioned.

  meetings       47      "What was discussed about X?" searches
                         meeting notes specifically, not your
                         entire vault.

  tasks          1       Smart task matching for triage. Catches
                         semantic duplicates like "Review metrics"
                         ≈ "Check quarterly numbers".

  projects       8       Project health pulls related docs
                         without inbox noise.

  goals          1       Goal alignment finds thematically
                         related work across your vault.

  priorities     1       Weekly planning discovers patterns
                         in past priority choices.

  Skipped (not enough content yet):
  - accounts  — No company pages found (create some first)
  - content   — No content files yet
  - career    — Career folder not set up (run /career-setup)

  Create all [N] collections? [Y]
  Pick specific ones?         [P]
  Just create a basic index?  [B]
Handle User Choice

If [Y] - Create all: Create every candidate collection using qmd collection add with context.

If [P] - Pick specific: Present each candidate individually with a Y/N toggle. Create only selected ones.

If [B] - Basic index: Create a single "vault" collection that indexes everything. This works but misses the precision of targeted collections.

Create Collections

For each accepted candidate, run:

bash
# Create the collection
qmd collection add "$VAULT_PATH/<path>" --name <name> --mask "<glob>"

# Add semantic context (helps the reranker understand what's in the collection)
qmd context add <name> "<context description>"

Collection definitions (full list):

NamePathGlobContextMin Files
people05-Areas/People**/*.mdPerson pages with meeting history, relationship notes, action items, and role context3
accounts05-Areas/Companies**/*.mdCompany and account pages with deal status, relationship notes, and interaction history1
accounts (alt)05-Areas/Relationships/Key_Accounts**/*.mdKey Account pages with deal status, MEDDPICC, and engagement history1
meetings00-Inbox/Meetings**/*.mdMeeting notes with attendees, key discussion points, decisions made, and action items5
tasks03-Tasks**/*.mdTask backlog with priorities (P0-P3), pillar alignment, status tracking, and linked goals1
projects04-Projects**/*.mdActive project tracking with status, stakeholders, timelines, and related decisions1
goals01-Quarter_Goals**/*.mdQuarterly strategic goals with success criteria, milestones, and progress tracking1
priorities02-Week_Priorities**/*.mdWeekly priorities linked to quarterly goals with completion tracking1
content05-Areas/Content**/*.mdContent ideas, articles, LinkedIn posts, and thought leadership material1
career05-Areas/Career**/*.mdCareer development evidence, feedback received, skills tracking, and growth goals1
prdsSystem/PRDs**/*.mdProduct requirement documents, feature specs, and technical design docs1
resources06-Resources**/*.mdReference material, learnings, system documentation, and guides5

After all collections are created, embed the vectors:

bash
echo "Creating embeddings for all collections..."
qmd embed

Show progress to the user — this may take a few minutes for larger vaults.

Show full SKILL.md (289 more words)Show less

Step 6: Configure MCP Server

Add qmd MCP server to the user's Claude/Cursor config.

For Claude Code (~/.claude.json):

json
{
  "mcpServers": {
    "qmd": {
      "type": "stdio",
      "command": "qmd",
      "args": ["mcp"]
    }
  }
}

For Cursor (.cursor/mcp.json in vault root):

json
{
  "mcpServers": {
    "qmd": {
      "command": "qmd",
      "args": ["mcp"]
    }
  }
}

Tell the user: "You'll need to restart your editor for the MCP server to be available. After restart, I can use semantic search automatically."

Step 7: Create Availability Check

Create .scripts/semantic-search/check-availability.cjs (see companion file). This lets other skills check if semantic search is available before using it.

Step 8: Show Success Summary

═══════════════════════════════════════════════════════════════════════
                    SEMANTIC SEARCH ENABLED
═══════════════════════════════════════════════════════════════════════

Your vault now has smart, meaning-aware search.

Collections created:
  [list each collection with file count]

Try it:
  qmd query "product led growth strategies"
  qmd query "customer churn patterns" -c accounts
  qmd search "meeting with Sarah" -c meetings

What's different now:
  /daily-plan    — meeting context enriched with thematic connections
  /meeting-prep  — attendee lookup finds role/title references
  /triage        — semantic routing with goal-aware matching
  Person Lookup  — finds "the VP of Sales" without needing the name
  Search & Recall — hybrid retrieval (BM25 + vectors + reranking)

Index updates automatically when you run: qmd update
To check status anytime:                  qmd status
To force full rebuild:                     qmd embed -f

As your vault grows, I'll suggest new collections when there's
enough content to benefit. Run this skill again anytime to check.

Collection Health Check (Returning Users)

If the user already has qmd installed and collections exist, this skill switches to health-check mode.

Run Health Check
bash
node "$VAULT_PATH/.scripts/semantic-search/scan-vault.cjs" --health-check

This compares existing collections against current vault state and returns:

json
{
  "existing": ["people", "meetings", "tasks"],
  "newCandidates": [
    {
      "name": "accounts",
      "path": "05-Areas/Companies",
      "fileCount": 5,
      "reason": "You've created 5 company pages since last check"
    }
  ],
  "staleCollections": [
    {
      "name": "meetings",
      "lastUpdated": "12 days ago",
      "currentFiles": 52,
      "indexedFiles": 47,
      "drift": 5
    }
  ],
  "pendingEmbeddings": 8,
  "suggestions": [
    "Run 'qmd update' to re-index changed files",
    "Run 'qmd embed' to embed 8 pending documents"
  ]
}
Present Health Report
SEMANTIC SEARCH HEALTH CHECK
─────────────────────────────────────────────────────────────────

Active Collections:
  people      54 files    Updated 2h ago     Healthy
  meetings    47 files    Updated 12d ago    ⚠ Stale (5 new files)
  tasks        4 files    Updated 1d ago     Healthy

New Collection Candidates:
  accounts    5 files     You've built enough company pages for
                          a dedicated collection. This means deal
                          prep will pull account context specifically.

                          → Create accounts collection? [Y/n]

Maintenance:
  8 documents need embedding (run 'qmd embed')
  meetings collection is 12 days stale (run 'qmd update')

Quick fix: qmd update && qmd embed
Handle New Candidates

For each new candidate:

  1. Explain what it enables (use the benefit text from the scanner)
  2. Ask if they want to create it
  3. If yes, create collection + context + embed
Growth Suggestions (Called by Other Skills)

Other skills can call the scanner in suggestion mode during workflows:

During /daily-plan:

node "$VAULT_PATH/.scripts/semantic-search/scan-vault.cjs" --suggestions-only

If new candidates are found, append to the daily plan:

💡 Semantic search suggestion: You now have 5 company pages.
   Want me to create an 'accounts' collection? This means deal
   prep will search account context specifically.
   Run /enable-semantic-search to set it up.

Skills should check availability before using semantic search:

javascript
// In your skill or hook
const { execSync } = require('child_process');

function isSemanticSearchAvailable() {
  try {
    execSync('which qmd', { stdio: 'pipe' });
    const status = execSync('qmd status', { stdio: 'pipe' }).toString();
    return status.includes('Documents');
  } catch {
    return false;
  }
}

// Use in search logic
if (isSemanticSearchAvailable()) {
  // Use qmd query for semantic search
  const results = execSync(`qmd query "${query}" -c people`, { stdio: 'pipe' });
} else {
  // Fall back to grep/file search
}

Or use the check-availability script:

javascript
const { checkSemanticSearch } = require('.scripts/semantic-search/check-availability.cjs');
const status = checkSemanticSearch();
if (status.available) {
  // Use semantic search
}

Troubleshooting

If setup fails:

  1. Bun install fails: Try npm install -g bun or download from bun.sh
  2. SQLite missing (macOS): Run brew install sqlite
  3. Model download fails: Check internet, retry with qmd embed -f
  4. Index takes too long: Large vaults (5000+ files) may take 10+ minutes first time
  5. Collections empty: Check paths match your vault structure — run the scanner to verify
  6. MCP not connecting: Restart your editor after adding the config

Disabling

To remove semantic search:

bash
# Remove index
qmd cleanup

# Remove the qmd binary
bun remove -g qmd

# Remove MCP config (manual — delete the "qmd" entry from your config)

Your vault files are never modified — removing qmd just removes the search index.

© davekilleen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/enable-semantic-search of davekilleen/Dex.

Open the folder on GitHubat commit d0ffc6b

Compare with similar skills

Enable Semantic Search next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Enable Semantic Search compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Enable Semantic Search this skilldavekilleen/Dex494—~4.5kAutomated safety check: NotesMIT
Ketch1broseidon/ketch7021 repos~3.9kAutomated safety check: PassMIT
Querying Indonesian Gov Datasuryast/indonesia-gov-apis172—~997Automated safety check: PassMIT
Media Crawlertsingyuai/growth-lab2k—~731Automated safety check: PassApache-2.0
Octocode Scrapingbgauryy/octocode949—~1.3kAutomated safety check: PassMIT
Apify Ashby Jobs Scraperapify/awesome-skills266—~3.7kAutomated safety check: PassMIT

Similar skills

  • Ketch

    1broseidon/ketch

    Research skill for ketch — a fast stateless CLI for web search, OSS code search, curated library docs, page scraping, and site crawling; an optional MCP server exists for operators who want it, but…

    702 GitHub starsUsed in 1 repo~3.9k tokens
    Data & AnalyticsAuto-check passed
  • Querying Indonesian Gov Data

    suryast/indonesia-gov-apis

    Query 57 Indonesian government APIs and data sources — BPJPH halal certification, BPOM food safety, OJK financial legality, BPS statistics, BMKG weather/earthquakes, Bank Indonesia exchange rates…

    172 GitHub stars~997 tokensUpdated yesterday
    Data & AnalyticsAuto-check passed
  • Media Crawler

    tsingyuai/growth-lab

    Install, authenticate, configure, operate, and troubleshoot the external MediaCrawler client shared by Douyin, Kuaishou, Bilibili, Weibo, Tieba, and Zhihu collectors.

    2k GitHub stars~731 tokensUpdated 12 days ago
    Data & AnalyticsAuto-check passed
  • Octocode Scraping

    bgauryy/octocode

    A skill your agent uses when extracting or mapping public web content into a local cited corpus: scrape or crawl a URL/docs site, pull tables/pricing/product fields, diagnose blocked or thin pages…

    949 GitHub stars~1.3k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed
  • Apify Ashby Jobs Scraper

    apify/awesome-skills

    Official

    Scrape Ashby jobs or discover companies using Ashby with the Apify Ashby Job Board API Actor (johnvc/ashby-job-board-scraper).

    266 GitHub stars~3.7k tokensUpdated 18 days ago
    Data & AnalyticsAuto-check passed
  • SEO Firecrawl

    seranking/seo-skills

    Ad-hoc web scraping, site mapping, and full-site crawling via Firecrawl MCP.

    161 GitHub stars~2.3k tokensUpdated 3 mo ago
    Data & AnalyticsAuto-check passed

More from davekilleen/Dex

All 61 skills in this repo
  • Dspy Ruby

    davekilleen/Dex

    This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications.

    494 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Diff Adopt Profile

    davekilleen/Dex

    Adopt a full published Heydex profile by handle ('set me up like @davekilleen').

    494 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Diff Generate

    davekilleen/Dex

    Package one workflow — how you use Dex for a specific job — into a shareable DexDiff methodology doc.

    494 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Creating Agent Skills

    davekilleen/Dex

    Expert guidance for creating, writing, and refining Claude Code Skills.

    494 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Feedback

    davekilleen/Dex

    Report a Dex bug to the Dex team with zero homework — Dex investigates locally, builds a privacy-safe report, shows it to you (or auto-sends if you've chosen that), and tracks the ticket until it's…

    494 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Dhh Rails Style

    davekilleen/Dex

    This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style.

    494 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Questions about Enable Semantic Search

What does Enable Semantic Search do?

Turn on local AI-powered semantic (meaning-based) search over the vault, with smart collection discovery. Enable Semantic Search is an agent skill from davekilleen/Dex. Turn on local AI-powered semantic (meaning-based) search over the vault, with smart collection discovery.

When should I use Enable Semantic Search?

Enable Semantic Search fits situations like: the user says enable semantic search; search by meaning; search keeps missing obvious matches.

How do I install Enable Semantic Search in Claude Code?

Run `npx skills add davekilleen/Dex --skill enable-semantic-search -a claude-code`. Or copy the skill folder (.agents/skills/enable-semantic-search in davekilleen/Dex) into .claude/skills/enable-semantic-search in your project. Claude Code loads it when a task matches its description.

How do I install Enable Semantic Search in Codex?

Run `npx skills add davekilleen/Dex --skill enable-semantic-search -a codex`. Or copy the skill folder (.agents/skills/enable-semantic-search in davekilleen/Dex) into .agents/skills/enable-semantic-search in your project. Codex loads it when a task matches its description.

Can I use Enable Semantic Search in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davekilleen/Dex --skill enable-semantic-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/enable-semantic-search, .gemini/skills/enable-semantic-search, .github/skills/enable-semantic-search and .opencode/skills/enable-semantic-search in your project.

What does Enable Semantic Search need to run?

Going by SKILL.md and its folder, Enable Semantic Search needs the command-line tools its instructions call (brew, bun, node, curl, bash and python3). Our summary lists: Python 3.

Does Enable Semantic Search access the network?

SKILL.md names 1 domain. In commands or code: bun.sh; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Enable Semantic Search safe to install?

Our automated static check of SKILL.md found notes only (pipes a well-known installer script into a shell), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Enable Semantic Search use?

Enable Semantic Search is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Enable Semantic Search use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Enable Semantic Search?

Skills that share tags, products or a category with Enable Semantic Search: Ketch (1broseidon/ketch, 702 stars), Querying Indonesian Gov Data (suryast/indonesia-gov-apis, 172 stars), Media Crawler (tsingyuai/growth-lab, 2k stars) and Octocode Scraping (bgauryy/octocode, 949 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Enable Semantic Search?

davekilleen (a GitHub user) maintains it in davekilleen/Dex, which has 494 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 9, 2026.

Source: davekilleen/Dex on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.