multiagent-research-coordinator

Designs and runs coordinator-worker research workflows with evidence contracts and provenance tracking.

Updated May 28, 2026
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill multiagent-research-coordinator-changfengpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multiagent-research-coordinator
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/multiagent-research-coordinator
Command: npx skills add https://github.com/changfengpro/agent-skills --skill multiagent-research-coordinator-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding when to split a research task across multiple AI agents is hard: delegating too eagerly wastes tokens and adds coordination overhead, while doing everything solo can miss coverage or blow the context budget. This Skill provides a disciplined gate, delegation design, and synthesis process for coordinator-worker research. ## Core Features & Use Cases - Delegation Gate: Applies explicit criteria to decide whether a task should be delegated or kept with a single strong agent, avoiding uneconomic fan-out. - Worker Brief & Output Schema: Provides templates for bounded worker assignments and compact evidence rows with status values like supported, conflicting, or not found. - Provenance-Aware Synthesis: Builds claim tables and evidence matrices before writing conclusions, preserving retrieval dates and unresolved uncertainty. - Use Case: When asked to verify 30 claims across dozens of sources, use this Skill to decide the split, assign 4-12 workers with source policies, then synthesize an auditable claim table with cost and latency comparison against a solo baseline. ## Quick Start Use the multiagent-research-coordinator skill to decide whether my research task should be delegated to workers and, if so, draft the worker briefs and synthesis plan.

Frequently Asked Questions about multiagent-research-coordinator

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

FAQPage Schema
When should I use multi-agent research instead of a single agent?

Use multi-agent research when the task is coverage-shaped with many independent sources, files, or claims that workers can check in parallel. Avoid it for narrow questions, tightly coupled subtasks, or when delegation overhead exceeds the reading cost.

How do I design worker prompts for delegated research?

Give each worker one bounded sub-question, an explicit source policy, a verification standard, and a required output format with evidence, retrieval dates, and status values. Tell workers not to answer the broader user question.

Should research workers use cheaper models or frontier models?

Use cheaper models for retrieval, extraction, and scanning where outputs are compact evidence rows. Reserve stronger models for ambiguous interpretation, conflicting sources, or final synthesis where nuance matters.

How do I measure cost savings from multi-agent research?

Measure wall-clock time, input and output tokens, model prices, and coordinator overhead against a solo baseline on the same task and source policy. Report whether savings come from cheaper workers, fewer tokens, lower latency, or better evidence quality.

When should I not delegate a research task to workers?

Do not delegate when fewer than four small independent units exist, subtasks share mutable state, the work needs one unified judgment, or worker setup would cost more than the reading it saves. Keep the work with a single strong agent instead.