Search Tools
- 472 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
search-tools is a Claude Code skill that routes agent code searches to LEANN semantic search, AST-grep structure queries, Morph text search, or built-in Grep via a decision tree.
About
search-tools is a continuous-claude-v3 skill defining a search tool hierarchy for agent-assisted development. Conceptual or architectural questions route to LEANN embedding-based semantic search with PreToolUse auto-redirect from semantic Grep queries. Structural lookups—function calls, class usages, refactor patterns—use AST-grep. Plain text search prefers Morph, described as 20x faster than Grep, with Grep as fallback when no Morph API key exists. Developers reach for search-tools when agents waste tokens on the wrong search primitive or need a consistent decision tree for codebase exploration.
- Enables Claude to perform live web searches during conversations
- Provides structured access to current events, documentation, and research sources
- Reduces hallucination by grounding responses in fresh external data
- Supports multiple search backends and result processing modes
- Designed as a reusable capability inside Continuous Claude v3 workflows
Search Tools by the numbers
- 472 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #776 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill search-toolsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 472 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
Which search tool should agents use for code?
Give their Claude agent reliable web search, knowledge retrieval, and real-time information gathering capabilities.
Who is it for?
Developers configuring Claude agents who need a consistent hierarchy for semantic, structural, and text codebase search.
Skip if: Teams needing web search, documentation crawling, or production log analytics rather than in-repo code navigation.
When should I use this skill?
Agent needs conceptual search, structural code lookup, fast text search, or a simple one-off Grep across the codebase.
What you get
Correct search tool selection with LEANN, AST-grep, Morph, or Grep invoked for the matching query type.
- search routing decision
- tool-specific query results
By the numbers
- Morph text search described as 20x faster than Grep
Files
Search Tool Hierarchy
When searching code, use this decision tree:
Decision Tree
Need CONCEPTUAL/SEMANTIC search?
(how does X work, find patterns, understand architecture)
→ Use LEANN (/leann-search) - embedding-based semantic search
→ PreToolUse hook auto-redirects semantic Grep queries
Need to understand code STRUCTURE?
(find function calls, class usages, refactor patterns)
→ Use AST-grep (/ast-grep-find)
Need to find TEXT in code?
→ Use Morph (/morph-search) - 20x faster
→ If no Morph API key: fall back to Grep tool
Simple one-off search?
→ Use built-in Grep tool directlyTool Comparison
| Tool | Best For | Requires |
|---|---|---|
| LEANN | Semantic search: "how does caching work", "error handling patterns", conceptual queries | Index built |
| AST-grep | Structural patterns: "find all calls to foo()", refactoring, find usages by type | MCP server |
| Morph | Fast text search: "find files mentioning error", grep across codebase | API key |
| Grep | Literal patterns, class/function names, regex | Nothing (built-in) |
Examples
LEANN (semantic/conceptual):
- "how does authentication work"
- "find error handling patterns"
- "where is rate limiting implemented"
AST-grep (structural):
- "Find all functions that return a Promise"
- "Find all React components using useState"
- "Refactor all imports of X to Y"
Morph (text search):
- "Find all files mentioning 'authentication'"
- "Search for TODO comments"
Grep (literal):
class ProviderAdapterdef __init__- Regex patterns
LEANN Commands
# Search with semantic query
leann search opc-dev "how does blackboard communication work" --top-k 5
# List available indexes
leann list
# Rebuild index (when code changes)
leann build opc-dev --docs dir1 dir2 --no-recompute --no-compact --forceRelated skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Pick search-tools to standardize in-repo agent search routing; use web-search skills when the target is live documentation or SERP results.
FAQ
When should agents use LEANN in search-tools?
search-tools directs agents to LEANN for conceptual or semantic questions—how something works, pattern discovery, architecture understanding—with PreToolUse hooks auto-redirecting semantic Grep queries to LEANN.
What is Morph used for in search-tools?
search-tools recommends Morph for fast plain-text code search, described as 20x faster than Grep; if no Morph API key is configured, agents fall back to the built-in Grep tool.