Agent skill · AI & Agents

deep-research-team

This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds, with the lead triaging findings and creating targeted follow-up tasks. Scales from Focused (2 researchers, 1-2 rounds) to Comprehensive (4 researchers, 3-4 rounds with cross-verification). Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill deep-research-team --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 23 KB
Bundled scripts: none
Path: skills/analysis/deep-research-team/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Deep Research Team (Lead Orchestrator) Conduct thorough, iterative research by coordinating a persistent team of researcher agents across multiple rounds. This architecture enables mid-investigation steering, targeted follow-up based on emerging findings, and cross-agent verification. ## Architecture Overview ``` Round 1: Investigation Round 2: Follow-up Synthesis ┌──────────┐ ┌──────────┐ ┌────────┐ │Researcher│ sends findings │Researcher│ sends findings │ │ │ A ├─────────┬───────>│ A ├─────────┬───────>│ │ └──────────┘ │ └──────────┘ │ │ │ │ │ │ │ v dispatches v │ │ ┌──────────┐ ┌────────┐ ┌──────────┐ ┌────────┐ │ Lead │ │Researcher├───>│ Lead │───>│Researcher├───>│ Lead │───>│ synth │ │ B │ │triages │ │ B │ │triages │ │ esizes│ └──────────┘ └────────┘ └──────────┘ └────────┘ │ │ ^ ^ │ │ ┌──────────┐ │ ┌──────────┐ │ │ │ │Researcher├─────────┴───────>│Researcher├─────────┴───────>│ │ │ C │ sends findings │ C │ sends findings │ │ └──────────┘ └──────────┘ └────────┘ ``` **Key principles:** 1. **No peer-to-peer researcher communication.** All coordination goes through the lead. This preserves the independence that accounts for 87% of multi-agent gains (Choi et al.) and avoids sy

What's inside
Steps it walks through
  1. Architecture Overview
  2. When to Use
  3. Effort Calibration
  4. Output Directory
  5. Calibrated Confidence Language
  6. Process
  7. Phase 0: Classify Question Type
  8. Phase 1: Clarify and Plan
  9. Phase 2: Calibrate Effort
  10. Phase 3: Team Setup
  11. Phase 4: Investigation Loop
  12. Phase 5: Synthesize (Type-Aware)
  13. Phase 6: Persist Report
  14. Phase 7: Cleanup
Ships with 1 file
  • metadata.json
Commands it runs
if [ -d "$(pwd)/deep-research" ]; then
echo "$(pwd)/deep-research"
elif [ -n "$CLAUDE_DEEP_RESEARCH_DIR" ]; then
eval echo "$CLAUDE_DEEP_RESEARCH_DIR"
else
mkdir -p "$(pwd)/deep-research"
fi
mkdir -p {output_dir}/{topic-slug}
prettier --write --prose-wrap preserve "{output_dir}/{topic-slug}/**/*.md"
More from claude-skill-registry
All skills →
About this skill
What does the deep-research-team skill do?

This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds, with the lead triaging findings and creating targeted follow-up tasks. Scales from Focused (2 researchers, 1-2 rounds) to Comprehensive (4 researchers, 3-4 rounds with cross-verification). Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill deep-research-team --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going