Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Multi Agent Researcher

ASecurity

Conduct comprehensive research on any topic by coordinating 2-4 specialized researcher agents in parallel, then synthesizing findings into a detailed report via mandatory report-writer agent delegation (Full workflow documentation at docs/workflows/research-workflow.md)

11 stars
0 votes
0 copies
8 views
Added 12/19/2025
ai-agentsgoapidocumentation

Works with

api

Security Analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned 2/12/2026

$npx -y skills add ahmedibrahim085/Claude-Multi-Agent-Research-System-Skill --skill multi-agent-researcher --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Multi Agent Researcher?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Multi Agent Researcher
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ahmedibrahim085-multi-agent-researcher/badge)](https://www.skillsdirectory.com/skills/ahmedibrahim085-multi-agent-researcher)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: multi-agent-researcher
description: Conduct comprehensive research on any topic by coordinating 2-4 specialized researcher agents in parallel, then synthesizing findings into a detailed report via mandatory report-writer agent delegation (Full workflow documentation at docs/workflows/research-workflow.md)
allowed-tools: Task, Read, Glob, TodoWrite
version: 2.1.2
---

# Multi-Agent Research Coordinator

## Purpose

Transform complex research questions into comprehensive reports by:
1. Decomposing broad topics into 2-4 focused subtopics
2. Spawning specialized researcher agents in parallel
3. Synthesizing findings into cohesive final report
4. Saving structured outputs for reference

## When to Use

Auto-invoke when user asks:
- **Search/Discovery**: "Search what is [topic]", "Find information about [subject]", "Look up [technology]", "Discover [patterns]"
- **Investigation**: "Research [topic]", "Investigate [subject]", "Analyze [phenomenon]", "Study [field]", "Explore [domain]"
- **Collection**: "Gather information about [subject]", "Collect data on [topic]", "Compile resources for [area]"
- **Learning**: "Learn about [subject]", "Tell me about [topic]", "Dig into [technology]", "Delve into [concept]"
- **Contextual**: "What are the latest developments in [field]?", "Comprehensive analysis of [topic]", "Deep dive into [subject]", "State of the art in [domain]", "Best practices for [area]"

Do NOT invoke for:
- Simple factual questions ("What is the capital of France?")
- Decision evaluation ("Should I use X or Y?")
- Code-related tasks ("Debug this function", "Write a script")

## Orchestration Workflow

### Phase 1: Query Analysis & Decomposition

**Step 1.1: Understand the Research Question**
Analyze user's query to identify core topic, scope, and intent.

**Step 1.2: Decompose into Subtopics**
Break topic into 2-4 focused subtopics that are:
- Mutually exclusive (minimal overlap)
- Collectively exhaustive (cover whole topic)
- Independently researchable
- Together provide comprehensive coverage

**Decomposition Patterns:**

**Temporal**: Past → Current → Future
**Categorical**: Category 1, 2, 3
**Stakeholder**: Technical → Business → Policy → User
**Problem-Solution**: Problem → Solutions → Gaps → Future
**Geographic**: Region A → Region B → Comparison

**Step 1.3: Create Research Plan**
Use TodoWrite to track:
```
- [ ] Decompose query into subtopics
- [ ] Spawn researcher 1: [subtopic]
- [ ] Spawn researcher 2: [subtopic]
- [ ] Spawn researcher 3: [subtopic]
- [ ] Synthesize findings
- [ ] Save final report
```

---

### Phase 2: Parallel Research Execution

**Step 2.1: Spawn Researcher Agents in Parallel**

For each subtopic, create a Task tool call with:
```
subagent_type: "researcher"
description: "Research {subtopic name}"
prompt: "Research the following subtopic in depth:

**Subtopic**: {Subtopic name}
**Context**: Part of research on '{original topic}'
**Focus**: {Specific guidance}

Conduct thorough web research, gather authoritative sources, extract key findings, and save results to files/research_notes/{subtopic-slug}.md"
```

**Critical**: Spawn ALL researchers in parallel (multiple Task calls in same message), not sequentially.

**Step 2.2: Monitor Completion**
Update TodoWrite as researchers complete.

**Step 2.3: Verify All Complete**
Use Glob to confirm all files exist: `files/research_notes/*.md`

---

### Phase 3: Synthesis & Report Generation

**⚠️ CRITICAL: ARCHITECTURAL ENFORCEMENT ACTIVE ⚠️**

**YOU DO NOT HAVE WRITE TOOL ACCESS** when this skill is active. The `allowed-tools` frontmatter explicitly EXCLUDES the Write tool to enforce proper workflow delegation.

**YOU CANNOT**:
- ❌ Write synthesis reports yourself
- ❌ Create files in files/reports/ directory
- ❌ Bypass the report-writer agent

**YOU MUST**:
- ✅ Spawn report-writer agent via Task tool
- ✅ Delegate all synthesis and report writing to the agent
- ✅ Read the completed report and deliver to user

---

**Step 3.1: Verify Research Completion**

1. Use Glob to confirm all research notes exist: `files/research_notes/*.md`
2. Verify count matches number of spawned researchers
3. If any missing: investigate and complete before synthesis

**Step 3.2: Spawn Report-Writer Agent (MANDATORY)**

**This is the ONLY synthesis approach** - there is no "Option A" or "Option B". You MUST use the report-writer agent because you lack Write tool permissions.

```
Task:
subagent_type: "report-writer"
description: "Synthesize research findings into comprehensive report"
prompt: "Synthesize research into comprehensive report:

**Original Question**: {user query}
**Subtopics Researched**: {list all subtopics}
**Notes Location**: files/research_notes/

## Your Tasks:
1. Read ALL research notes from files/research_notes/
2. Identify themes, patterns, and contradictions across notes
3. Synthesize findings into cohesive narrative
4. Cite sources from research notes
5. Add cross-cutting insights beyond individual notes
6. Save comprehensive report to files/reports/{topic-slug}_{timestamp}.md

## Report Structure:
- Executive Summary
- Key Findings (with evidence from research notes)
- Detailed Analysis by subtopic
- Cross-Cutting Themes
- Contradictions and Debates
- Gaps and Limitations
- Source Bibliography

Use the timestamp format: $(date +\"%Y%m%d-%H%M%S\") for the filename."
```

**Step 3.3: Monitor Agent Completion**

After spawning report-writer agent, wait for completion. The agent will:
- Read all research notes
- Synthesize findings
- Write comprehensive report to files/reports/
- Return completion message with file path

---

### Phase 4: Deliver Results

**Step 4.1: Create User Summary**
```markdown
# Research Complete: {Topic}

Comprehensive research completed with {N} specialized researchers.

## Key Findings
1. {Finding 1}
2. {Finding 2}
3. {Finding 3}

## Research Scope
{N} subtopics investigated:
- {Subtopic 1}
- {Subtopic 2}
- {Subtopic 3}

## Files Generated
**Research Notes**: `files/research_notes/`
- {file1}.md
- {file2}.md
- {file3}.md

**Final Report**: `files/reports/{filename}.md`

## Next Steps
{Optional suggestions}
```

**Step 4.2: Update TodoWrite**
Mark all items complete.

---

## Best Practices

### Good Decomposition
✅ 2-4 subtopics (sweet spot: 3)
✅ Distinct but related
✅ Comprehensive coverage
✅ Independently researchable

❌ Too many (>5)
❌ Too few (1)
❌ Significant overlap
❌ Too narrow or too broad

### Parallel Execution
- Always spawn researchers simultaneously
- Never sequential unless dependent
- Provide context to each researcher
- Reasonable scope (10-15 min each)

### Synthesis Quality
- Read ALL notes
- Find connections across subtopics
- Note contradictions explicitly
- Cite sources
- Add insights beyond individual notes

---

## Error Handling

**Researcher Fails**: Try replacement, proceed with others, note gap
**No Results Found**: Accept partial, note limitation
**Contradictory Findings**: Document all perspectives explicitly
**Unclear Query**: Ask clarifying questions first

---

## Examples

**Query**: "Research quantum error correction"
**Decomposition**:
1. Theoretical foundations
2. Hardware implementations
3. Commercial viability
**Researchers**: 3 parallel
**Synthesis**: report-writer agent (MANDATORY)

**Query**: "Investigate cryptocurrency market 2025"
**Decomposition**:
1. Market metrics & players
2. Regulatory landscape
3. Technology evolution
4. Institutional trends
**Researchers**: 4 parallel
**Synthesis**: report-writer agent (MANDATORY)

---

**Remember**: Quality depends on good decomposition, thorough researchers, insightful synthesis, and clear user communication.

Attribution

ahmedibrahim085ahmedibrahim085
View sourceSee grades on GitHubMore from ahmedibrahim085 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →