search-router▌
parcadei/continuous-claude-v3 · updated Apr 8, 2026
Use the most token-efficient search tool for each query type.
Search Tool Router
Use the most token-efficient search tool for each query type.
When to Use
- Searching for code patterns
- Finding where something is implemented
- Looking for specific identifiers
- Understanding how code works
Decision Tree
Query Type?
├── CODE EXPLORATION (symbols, call chains, data flow)
│ → TLDR Search - 95% token savings
│ DEFAULT FOR ALL CODE SEARCH - use instead of Grep
│ Examples: "spawn_agent", "DataPoller", "redis usage"
│ Command: tldr search "query" .
│
├── STRUCTURAL (AST patterns)
│ → AST-grep (/ast-grep-find) - ~50 tokens output
│ Examples: "def foo", "class Bar", "import X", "@decorator"
│
├── SEMANTIC (conceptual questions)
│ → TLDR Semantic - 5-layer embeddings (P6)
│ Examples: "how does auth work", "find error handling patterns"
│ Command: tldr semantic search "query"
│
├── LITERAL (exact text, regex)
│ → Grep tool - LAST RESORT
│ Only when TLDR/AST-grep don't apply
│ Examples: error messages, config values, non-code text
│
└── FULL CONTEXT (need complete understanding)
→ Read tool - 1500+ tokens
Last resort after finding the right file
Token Efficiency Comparison
| Tool | Output Size | Best For |
|---|---|---|
| TLDR | ~50-500 | DEFAULT: Code symbols, call graphs, data flow |
| TLDR Semantic | ~100-300 | Conceptual queries (P6, embedding-based) |
| AST-grep | ~50 tokens | Function/class definitions, imports, decorators |
| Grep | ~200-2000 | LAST RESORT: Non-code text, regex |
| Read | ~1500+ | Full understanding after finding the file |
Examples
# CODE EXPLORATION → TLDR (DEFAULT)
tldr search "spawn_agent" .
tldr search "redis" . --layer call_graph
# STRUCTURAL → AST-grep
/ast-grep-find "async def $FUNC($$$):" --lang python
# SEMANTIC → TLDR Semantic
tldr semantic search "how does authentication work"
# LITERAL → Grep (LAST RESORT - prefer TLDR)
Grep pattern="check_evocation" path=opc/scripts
# FULL CONTEXT → Read (after finding file)
Read file_path=opc/scripts/z3_erotetic.py
Optimal Flow
1. AST-grep: "Find async functions" → 3 file:line matches
2. Read: Top match only → Full understanding
3. Skip: 4 irrelevant files → 6000 tokens saved
Related Skills
/tldr-search- DEFAULT - Code exploration with 95% token savings/ast-grep-find- Structural code search/morph-search- Fast text search
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★32 reviews- ★★★★★Ama Shah· Dec 20, 2024
Solid pick for teams standardizing on skills: search-router is focused, and the summary matches what you get after install.
- ★★★★★Ren Anderson· Dec 8, 2024
Registry listing for search-router matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sofia Sethi· Nov 27, 2024
search-router reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Rahul Santra· Nov 15, 2024
search-router fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Omar Jackson· Nov 11, 2024
I recommend search-router for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Isabella Khan· Nov 3, 2024
search-router is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Lucas Reddy· Oct 22, 2024
Solid pick for teams standardizing on skills: search-router is focused, and the summary matches what you get after install.
- ★★★★★Sofia Malhotra· Oct 18, 2024
We added search-router from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Pratham Ware· Oct 6, 2024
search-router has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Omar Patel· Oct 2, 2024
Keeps context tight: search-router is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 32