| name | research-docs |
| description | Triggered when user asks to research library documentation, look up API references, find framework docs, or needs technical documentation. Uses Context7 MCP. Automatically delegates to the docs-researcher agent. Use when this capability is needed. |
| metadata | {"author":"dobroslavradosavljevic"} |
Research Docs Skill
Trigger Phrases
This skill is automatically triggered when the user:
- Asks to "look up documentation" or "find docs"
- Requests library or framework documentation
- Wants to "research API" or "check documentation"
- Mentions "documentation", "API reference", or "library docs"
- Asks how to use a library or framework
Delegation Instructions
When this skill is triggered:
- Delegate immediately to the
docs-researcher agent
- Specify what documentation is needed
- Include library/framework name
- Provide specific questions or use cases
- Include any version requirements
Context to Pass
- Library/Framework: Name of library or framework
- Query: Specific documentation question or topic
- Use Case: What the user is trying to accomplish
- Version: Library version if specified
- Context: Project context or related code
- Previous Research: Any previous documentation found
Agent Responsibilities
The docs-researcher agent will:
- Resolve library ID using Context7 MCP
- Query documentation for specific information
- Find code examples and usage patterns
- Provide comprehensive documentation summaries
- Include practical examples
- Verify information accuracy
Usage Examples
Example 1: Library Usage
User: "How do I use React hooks?"
Delegation: Delegate to docs-researcher with:
- Library: React
- Query: Hooks usage
- Use Case: Using React hooks
Example 2: API Reference
User: "What are the parameters for the fetch API?"
Delegation: Delegate to docs-researcher with:
- Library: Fetch API
- Query: API parameters
- Context: API usage
Example 3: Framework Documentation
User: "Find documentation for Next.js routing"
Delegation: Delegate to docs-researcher with:
- Library: Next.js
- Query: Routing documentation
- Use Case: Implementing routing
Best Practices
- Always use Context7 MCP for documentation
- CRITICAL: Resolve library ID FIRST (Step 1), then query docs (Step 2)
- Never skip the resolve-library-id step
- Never call query-docs without a resolved library ID
- Query specific topics
- Provide code examples
- Include version information
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
