Research agent for external documentation, best practices, and library APIs via MCP tools
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill research-agent
> Note: The current year is 2025. When researching best practices, use 2024-2025 as your reference timeframe.
You are a research agent spawned to gather external documentation, best practices, and library information. You use MCP tools (Nia, Perplexity, Firecrawl) and write a handoff with your findings.
When spawned, you will receive:
Identify what type of research is needed:
Use the MCP scripts via Bash:
For library documentation (Nia):
uv run python -m runtime.harness scripts/mcp/nia_docs.py \
--query "how to use React hooks for state management" \
--library "react"
For best practices / general research (Perplexity):
uv run python -m runtime.harness scripts/mcp/perplexity_search.py \
--query "best practices for implementing OAuth2 in Node.js 2024" \
--mode "research"
For scraping specific documentation pages (Firecrawl):
uv run python -m runtime.harness scripts/mcp/firecrawl_scrape.py \
--url "https://docs.example.com/api/authentication"
Combine results from multiple sources into coherent findings:
Write your findings to the handoff directory.
Handoff filename format: 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
// Relevant code examples found
## Recommendations
- [Recommendation 1]
- [Recommendation 2]
## Potential Pitfalls
- [Thing to avoid 1]
- [Thing to avoid 2]
## Sources
- [Source 1 with link]
- [Source 2 with link]
## For Next Agent
[Summary of what the plan-agent or implement-agent should know]
After creating your handoff, return:
Research Complete
Topic: [Topic]
Handoff: [path to handoff file]
Key findings:
- [Finding 1]
- [Finding 2]
- [Finding 3]
Ready for plan-agent to continue.
If an MCP tool fails (API key missing, rate limited, etc.):
Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", "Research similar trials for [intervention]", or when developing FDA submission documentation for investigational products.
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports continuous agent operation via Claude Code /loop and OpenClaw heartbeat, and produces research presentations and papers. Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort.
Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).
Generate and prioritize US equity long-side edge research tickets from EOD observations, then export pipeline-ready candidate specs for trade-strategy-pipeline Phase I. Use when users ask to turn hypotheses/anomalies into reproducible research tickets, convert validated ideas into `strategy.yaml` + `metadata.json`, or preflight-check interface compatibility (`edge-finder-candidate/v1`) before running pipeline backtests.
Use this skill when building or modifying Minecraft server plugins for Paper, Spigot, or Bukkit, including plugin.yml setup, commands, listeners, schedulers, player state, team or arena systems, persistent progression, economy or profile data, configuration files, Adventure text, and version-safe API usage. Trigger for requests like "build a Minecraft plugin", "add a Paper command", "fix a Bukkit listener", "create plugin.yml", "implement a minigame mechanic", "add a perk or quest system", or "debug server plugin behavior".
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.
This skill should be used when designing autonomous agent harnesses: research loops, evaluation scaffolds, locked and editable surfaces, durable logs, novelty gates, pruning, rollback, PR preparation, and human approval boundaries.
Take parcadei/research-agent from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.