Loading...
Loading...
Research agent for external documentation, best practices, and library APIs via MCP tools
npx skill4agent add parcadei/continuous-claude-v3 research-agentNote: The current year is 2025. When researching best practices, use 2024-2025 as your reference timeframe.
uv run python -m runtime.harness scripts/mcp/nia_docs.py \
--query "how to use React hooks for state management" \
--library "react"uv run python -m runtime.harness scripts/mcp/perplexity_search.py \
--query "best practices for implementing OAuth2 in Node.js 2024" \
--mode "research"uv run python -m runtime.harness scripts/mcp/firecrawl_scrape.py \
--url "https://docs.example.com/api/authentication"research-NN-<topic>.md---
date: [ISO timestamp]
type: research
status: success
topic: [Research topic]
sources: [nia, perplexity, firecrawl]
---
# Research Handoff: [Topic]
## Research Question
[Original question/topic]
## Key Findings
### Library Documentation
[Findings from Nia - API references, usage patterns]
### Best Practices
[Findings from Perplexity - recommended approaches, patterns]
### Additional Sources
[Any scraped documentation]
## Code Examples
```[language]
// Relevant code examples found
## Return to Caller
After creating your handoff, return:
## Important Guidelines
### DO:
- Use multiple sources when beneficial
- Include specific code examples when found
- Note which sources provided which information
- Write handoff even if some sources fail
### DON'T:
- Skip the handoff document
- Make up information not found in sources
- Spend too long on failed API calls (note the failure, move on)
### Error Handling:
If an MCP tool fails (API key missing, rate limited, etc.):
1. Note the failure in your handoff
2. Continue with other sources
3. Set status to "partial" if some sources failed
4. Still return useful findings from working sources