aiskillstore/marketplace / skills/23blocks-os/ai-maestro-documentation-search
ai-maestro-documentation-search
VerifiedPROACTIVELY 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.
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:
# IMMEDIATELY run:
docs-search.sh "PaymentService"
docs-find-by-type.sh class
Example - User mentions a function:
# IMMEDIATELY run:
docs-search.sh "validateUser"
docs-search.sh --keyword "authenticate"
Available Commands
All commands auto-detect your agent ID from the tmux session.
Search Commands
| Command | Description |
|---|---|
docs-search.sh <query> | Semantic search through documentation |
docs-search.sh --keyword <term> | Keyword/exact match search |
docs-find-by-type.sh <type> | Find docs by type (function, class, module, etc.) |
docs-get.sh <doc-id> | Get full document with all sections |
docs-list.sh | List all indexed documents |
docs-stats.sh | Get documentation index statistics |
Indexing Commands
| Command | Description |
|---|---|
docs-index.sh [project-path] | Index documentation from project |
What to Search Based on User Instruction
| User Says | IMMEDIATELY Search |
|---|---|
| "Create a service for X" | docs-search.sh "service", docs-find-by-type.sh class |
| "Call the Y function" | docs-search.sh "Y", docs-search.sh --keyword "Y" |
| "Implement authentication" | docs-search.sh "authentication", docs-search.sh "auth" |
| "Fix the Z method" | docs-search.sh "Z" --keyword, docs-find-by-type.sh function |
| Any API/function name | docs-search.sh "<name>" --keyword |
Usage Examples
Search for Documentation
# 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
docs-search.sh --keyword "authenticate"
docs-search.sh --keyword "UserController"
Find by Document Type
# Find all function documentation
docs-find-by-type.sh function
# Find all class documentation
docs-find-by-type.sh class
# Find all module/concern documentation
docs-find-by-type.sh module
# Find all interface documentation
docs-find-by-type.sh interface
Get Full Document
# After finding a doc ID from search results
docs-get.sh doc-abc123
# Shows full content including all sections
List and Stats
# List all indexed documents
docs-list.sh
# Get index statistics
docs-stats.sh
Index Documentation
# Index current project (auto-detected from agent config)
docs-index.sh
# Index specific project
docs-index.sh /path/to/project
Document Types
The following document types are recognized:
| Type | Description | Sources |
|---|---|---|
function | Function/method documentation | JSDoc, RDoc, docstrings |
class | Class documentation | Class-level comments |
module | Module/namespace documentation | Module comments |
interface | Interface/type documentation | TypeScript interfaces |
component | React/Vue component documentation | Component comments |
constant | Documented constants | Constant comments |
readme | README files | README.md, README.txt |
guide | Guide/tutorial documentation | docs/ folder |
Integration with Other Skills
Docs-search works best when combined with other skills:
Combined Search Pattern (RECOMMENDED)
When you receive ANY user instruction:
# 1. Search your memory first
memory-search.sh "topic"
# 2. Search documentation
docs-search.sh "topic"
# 3. Check code structure
graph-describe.sh ComponentName
This gives you complete context:
- Memory: What was discussed before?
- Docs: What does the documentation say?
- Graph: What is the code structure?
Why This Matters
Without searching docs first, you will:
- Use wrong function signatures (then get runtime errors)
- Miss existing implementations (then duplicate code)
- Violate documented patterns (then create inconsistency)
- Misunderstand APIs (then build the wrong thing)
Doc search takes 1 second. Redoing work takes hours.
Error Handling
Script not found:
- Check PATH:
which docs-search.sh - Verify scripts installed:
ls -la ~/.local/bin/docs-*.sh - Scripts are installed to
~/.local/bin/which should be in your PATH - If not found, run:
./install-docs-tools.sh
API connection fails:
- Ensure AI Maestro is running:
curl http://localhost:23000/api/agents - Ensure documentation has been indexed:
docs-stats.sh - If no docs indexed, run:
docs-index.sh
Documentation is empty:
- Check project has documented code (JSDoc, docstrings, comments)
- Verify project path is correct
- Re-index with:
docs-index.sh /path/to/project
No results found:
- Inform the user: "No documentation found for X - proceeding with code analysis, but documentation may need to be generated."
Installation
If commands are not found:
./install-docs-tools.sh
This installs scripts to ~/.local/bin/.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |