deep-research

Orchestrates multi-round web research with parallel synthesis and claim verification.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill deep-research-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-research
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/deep-research
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill deep-research-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Answering complex questions from memory alone risks hallucinated facts and missing sources. This Skill runs a structured, evidence-grounded research protocol that decomposes a question, retrieves real web sources, verifies every claim, and delivers a cited report. ## Core Features & Use Cases - Iterative Retrieval Loop: Decomposes the question into subtopics and runs up to 4 rounds of web_search and web_fetch, maintaining an evidence ledger keyed by subtopic. - Parallel Synthesis & Verification: Dispatches parallel sme workers to synthesize findings, then two reviewers verify each claim against its cited evidence, and a critic challenges high-stakes claims. - Cited Report Output: Produces a report or brief with per-subtopic sections, source citations, honest disagreement surfacing, and explicit UNVERIFIED markers for ungrounded topics. - Use Case: Ask "What are the current best practices for RAG chunking strategies?" and receive a fact-checked report where every load-bearing claim links to a fetched primary source. ## Quick Start Ask the agent to run deep research on your question, for example: run deep research on the trade-offs between vector databases for self-hosted RAG systems.

Frequently Asked Questions about deep-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run deep research with web search on a complex question?▼

Trigger the deep-research mode with your question; the orchestrator decomposes it into subtopics, runs iterative web_search and web_fetch rounds, and synthesizes a cited report. You can tune depth, rounds, and researcher count in the mode header.

What search API keys does deep research require?▼

Deep research requires a Tavily or Brave search API key configured via council.general.searchApiKey or the TAVILY_API_KEY / BRAVE_SEARCH_API_KEY environment variables. Without a key, the protocol stops rather than producing ungrounded answers.

How are research claims verified before appearing in the report?▼

Each claim passes dual-reviewer verification against its cited evidence ref, with verdicts of SUPPORTED, UNSUPPORTED, OVERSTATED, or CONTRADICTED. High-stakes or contested claims also face a critic challenge that can downgrade or reject them.

Can deep research modify my code or write project files?▼

No. The protocol is read-only: it does not mutate source code, delegate to coder, or write user-visible files. Evidence is cached under .swarm/evidence-cache/ by the tools, and the report is delivered directly in chat.

What happens when a subtopic cannot be grounded in sources?▼

If retrieval fails or sources are insufficient for a subtopic, it is explicitly marked UNVERIFIED in the report rather than answered from training memory. Conflicting sources are surfaced honestly with both sides presented.