⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

claude-research-skill

@altmbr⭐ 20 stars

Decompose a research question into parallel agent workstreams, launch them, monitor progress, and synthesize results.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 20 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

/research — Multi-Agent Research Orchestrator for Claude Code

A Claude Code skill that decomposes any research question into parallel agent workstreams, launches them simultaneously, monitors progress, and synthesizes results into a single coherent document.

One command. Multiple agents. Deeply sourced research in minutes.

What It Does

Type /research [any question] and the skill will:

  1. Decompose your question into 2-4 non-overlapping research workstreams
  2. Present a plan for your approval before doing anything
  3. Launch parallel agents — each writes to its own markdown file in real-time
  4. Monitor progress — checks in at escalating intervals, kills stuck agents, relaunches automatically
  5. Synthesize — a final agent reads all research outputs and produces a unified document with cross-cutting insights, contradictions, and confidence assessments

Example

> /research Help me understand the psychology of dating to find a life partner in your mid-30s

## Research Plan: Dating Psychology (Mid-30s)

### Agent 1: Decision Science & Optimal Stopping
Sections: Secretary problem, satisficing vs maximizing, paradox of choice...

### Agent 2: Relationship Science & Compatibility
Sections: Gottman's research, attachment theory, compatibility factors...

### Agent 3: Dating Channels & Strategy
Sections: Apps vs community, meeting method vs quality, cognitive biases...

### Synthesis Agent
Runs after all agents complete → unified playbook with actionable framework

Output: 4 markdown files, ~1,700+ lines of deeply sourced research with inline citations — produced in ~10 minutes.

Install

Copy the skill file to your Claude Code commands directory:

# Clone the repo
git clone https://github.com/altmbr/claude-research-skill.git

# Copy to Claude Code
cp claude-research-skill/SKILL.md ~/.claude/commands/research.md

Or manually: download SKILL.md and save it as ~/.claude/commands/research.md.

That's it. Type /research in Claude Code and it works.

How It Works

The skill uses Claude Code's built-in Task tool to launch multiple general-purpose subagents in parallel. Each agent:

  • Gets a strict write protocol — must write findings to its file after every single search (no two searches in a row without writing)
  • Works through sections in order, citing every claim with inline source URLs
  • Marks its file Status: COMPLETE when done

The orchestrator monitors all agents at escalating intervals (30s, 2min, 5min, then every 5min). If an agent gets stuck (line count unchanged between check-ins), it's automatically killed and relaunched with any data it already found pre-loaded.

After all research agents complete, a synthesis agent reads every output file and produces:

  • Executive summary (3-5 bullets)
  • Key findings by theme (cross-cutting, not per-agent)
  • Contradictions & tensions
  • Confidence assessment (well-supported vs. speculative)
  • Recommended next steps

Key Design Decisions

  • Write-after-every-search protocol — Agents that research without writing get stuck in loops. The strict alternating pattern (search → write → search → write) prevents this entirely.
  • Stuck agent recovery — Rather than waiting for agents to self-correct (they won't), the orchestrator kills and relaunches with pre-loaded data. No wasted time.
  • Skeleton files first — Creating output files with section headers before launching agents gives them structure and makes progress monitoring trivial (just check line counts).
  • User approval before launch — The plan is always shown first. No wasted compute on the wrong decomposition.

Output Structure

research/
└── [topic]/
    ├── agent-1.md          # First research workstream
    ├── agent-2.md          # Second research workstream
    ├── agent-3.md          # Third research workstream (if needed)
    └── synthesis.md        # Cross-cutting synthesis

Each file is a standalone, deeply sourced markdown document with inline citations.

Requirements

  • Claude Code (CLI)
  • No API keys or external dependencies — uses Claude Code's built-in tools

License

MIT — see LICENSE.

Author

Bryan Altman — GitHub

// HOW IT'S BUILT

KEY FILES

SKILL.mdREADME.md

// REPO STATS

20 stars

// SHARE

Share on XShare on LinkedIn