Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From indexed
Search the codebase using semantic search via the indexed MCP server. ALWAYS prefer this over Grep/Glob when looking for code by meaning, intent, or concept (e.g. "where is authentication handled", "find retry logic"). Only fall back to Grep for exact literal patterns.
How this skill is triggered — by the user, by Claude, or both
Slash command
/indexed:index-useThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the indexed MCP server for semantic codebase search instead of Grep/Glob.
Use the indexed MCP server for semantic codebase search instead of Grep/Glob.
!indexed index inspect 2>/dev/null || echo "No collections indexed yet. Run /index-create first."
Call the MCP tool directly:
mcp__indexed__search(query="$ARGUMENTS")
mcp__indexed__search_collection(collection="<name>", query="$ARGUMENTS")
| Goal | Tool |
|---|---|
| "Where is X handled?" / concept search | mcp__indexed__search |
| Finding related implementations | mcp__indexed__search |
| Understanding code intent | mcp__indexed__search |
| Exact regex or literal string match | Grep |
| Finding files by name/glob pattern | Glob |
Results are ranked by relevance (lowest L2 distance = best match). Each result contains:
rank — position in result listrelevance_score — similarity scorecollection — source collectiondocument_id / document_url — source referencechunk_number — matched chunk positiontext — the actual matched contentmcp__indexed__search(query="...") with a natural-language queryRead to open the source files for the top hitsnpx claudepluginhub lennardzuendorf/indexedGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.