research-orchestration
Parallel research agent orchestration dispatching 5-10 concurrent agents for comprehensive multi-source research with synthesis and validation.
npx skills add a5c-ai/babysitter --skill research-orchestration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Process Flow 1. **Plan**: Decompose query into independent sub-queries 2. **Dispatch**: Run 5-10 research agents in parallel 3. **Synthesize**: Merge findings, identify consensus and conflicts 4. **Validate**: Cross-reference against codebase for accuracy ## Sources - Codebase: source files, patterns, implementations - Documentation: README, JSDoc, inline comments - Configuration: package.json, tsconfig, CI/CD configs ## Confidence Scoring Overall confidence is a weighted average of individual agent confidence scores, adjusted by validation results. Below 70% triggers human review. ## When to Use - `/research [query]` slash command - Before specification creation - When investigating unfamiliar parts of the codebase ## Processes Used By - `claudekit-research` (primary consumer)
- Process Flow
- Sources
- Confidence Scoring
- When to Use
- Processes Used By
What does the research-orchestration skill do?
Parallel research agent orchestration dispatching 5-10 concurrent agents for comprehensive multi-source research with synthesis and validation.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill research-orchestration --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 a5c-ai/babysitter, a repository with 1,642 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.