docs-search
PROACTIVELY search auto-generated documentation when receiving ANY user instruction. Search for function signatures, API documentation, class definitions, and code comments BEFORE implementing anything. Your codebase documentation is valuable - use it first.
npx skills add majiayu000/claude-skill-registry --skill docs-search-23blocks-os-ai-maestro --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# AI Maestro Documentation Search ## CRITICAL: AUTOMATIC BEHAVIOR - READ THIS FIRST **THIS IS NOT OPTIONAL. THIS IS YOUR DEFAULT BEHAVIOR.** When the user gives you ANY instruction or task, you MUST FIRST search documentation for: - **Function signatures** - What are the parameters and return types? - **Class documentation** - What methods and properties exist? - **API documentation** - How should this endpoint work? - **Code comments** - What did the author intend? **DO NOT:** - Start implementing before checking documentation - Assume you know the function signature without checking - Skip doc search because "it's a simple task" - Wait for the user to ask you to check docs **ALWAYS:** - Search docs IMMEDIATELY when you receive a task - Search for terms and concepts the user mentions - Check documentation before calling unfamiliar functions - Look for patterns before creating new components ### The Rule: Receive Instruction → Search Docs → Then Proceed ``` 1. User asks you to do something 2. IMMEDIATELY search docs for relevant context 3. NOW you know the correct signatures and patterns 4. NOW you can implement correctly the first time ``` **Example - User asks to modify a service
- CRITICAL: AUTOMATIC BEHAVIOR - READ THIS FIRST
- The Rule: Receive Instruction → Search Docs → Then Proceed
- Available Commands
- Search Commands
- Indexing Commands
- What to Search Based on User Instruction
- Usage Examples
- Search for Documentation
- Find by Document Type
- Get Full Document
- List and Stats
- Index Documentation
- Document Types
- Integration with Other Skills
IMMEDIATELY run: docs-search.sh "PaymentService" docs-find-by-type.sh class docs-search.sh "validateUser" docs-search.sh --keyword "authenticate" Semantic search - finds conceptually related docs docs-search.sh "authentication flow" docs-search.sh "how to validate user input" docs-search.sh "database connection pooling" Keyword search - exact term matching
What does the docs-search skill do?
PROACTIVELY search auto-generated documentation when receiving ANY user instruction. Search for function signatures, API documentation, class definitions, and code comments BEFORE implementing anything. Your codebase documentation is valuable - use it first.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill docs-search-23blocks-os-ai-maestro --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.