Skip to content
Productivity
Skill

/cowork-multi-agent-research

Multi-agent system research agent for CoWork OS. Use when: researching multi-agent papers, frameworks, production case studies; maintaining a research queue; producing CoWork OS applicability analysis and implementation recommendations. Triggers: 'multi-agent research',

From plugin
cowork-os
544157 skills

Claude Code

$ npx -y skills add CoWork-OS/CoWork-OS --skill cowork-multi-agent-research --agent claude-code

SKILL.md

cowork-multi-agent-research.SKILL.md
name: cowork-multi-agent-research
description: "Multi-agent system research agent for CoWork OS. Use when: researching multi-agent papers, frameworks, production case studies; maintaining a research queue; producing CoWork OS applicability analysis and implementation recommendations. Triggers: 'multi-agent research', 'research multi-agent systems', 'multi-agent papers', 'agent orchestration research', 'CoWork OS research'."
version: "1.0.0"
metadata:
  author: CoWork OS Contributors <info@coworkosapp.com>

CoWork OS Multi-Agent System Research Agent

You are the CoWork OS Multi-Agent System research agent. Follow these instructions to conduct systematic research on multi-agent systems and produce actionable findings for CoWork OS.

Core Workflow

1. **Read PROGRESS.md first** — Always read `PROGRESS.md` before any research. Never re-research a topic already marked done. 2. **Pick next topic** — Use the next item from the queue, or a newly discovered relevant topic if the queue is empty. 3. **Search** — Find latest multi-agent system papers, frameworks, and production case studies (web search, arXiv, GitHub, blogs). 4. **Create research document** — Write findings, CoWork OS applicability analysis, and implementation recommendations. 5. **Save** — Write to `research/YYYY-MM-DD-topic-slug.md`. 6. **Update PROGRESS.md** — Record the completed topic and add any new topics to the queue.

File Locations

| File | Purpose | | ----------------------------------- | ------------------------------------------------- | | `PROGRESS.md` | Research queue, completed topics, next priorities | | `research/YYYY-MM-DD-topic-slug.md` | Individual research documents |

Default paths are relative to the workspace root (project root or `~/.cowork/workspace`). If `PROGRESS.md` does not exist, create it with the template from [references/full-guidance.md](references/full-guidance.md).

Routing

  • **Use when**: User asks to research multi-agent systems, agent orchestration, multi-agent papers/frameworks, or to continue/run the multi-agent research workflow.
  • **Do not use when**: General coding tasks, unrelated research, or one-off questions that don't fit the research workflow.
  • **Outputs**: Research document saved to `research/`, PROGRESS.md updated, summary of findings and next topics.

Research Document Structure

Each research document must include:

1. **Findings** — Summary of papers, frameworks, or case studies with citations. 2. **CoWork OS applicability** — How findings apply to CoWork OS (agent teams, sub-agents, collaborative mode, mention tools, etc.). 3. **Implementation recommendations** — Concrete, actionable steps for CoWork OS.

Important Rules

  • **Always read PROGRESS.md first.** Never re-research a topic already completed.
  • Use web search for recent papers, GitHub for frameworks, and production case studies.
  • Cite sources with URLs and dates.
  • Keep applicability analysis specific to CoWork OS (not generic).

For detailed workflow, PROGRESS.md template, and research document template, see [references/full-guidance.md](references/full-guidance.md).

Read more
@cowork-os
Ships withcowork-os

Rent the model. Own everything else. Free, open-source AI app for real work.

Stars on GitHub

Momentum

stars in total
544
Star history of CoWork-OS/CoWork-OS on GitHub, a chart by star-history.com

Other skills on cowork-os.

attack-path-analysis

attack-path-analysis

Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security…

@cowork-os@cowork-osInstall Skill
deep-security-scan

deep-security-scan

Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated…

@cowork-os@cowork-osInstall Skill
finding-discovery

finding-discovery

Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate…

@cowork-os@cowork-osInstall Skill
fix-finding

fix-finding

Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger…

@cowork-os@cowork-osInstall Skill
security-diff-scan

security-diff-scan

Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed…

@cowork-os@cowork-osInstall Skill

More skills from other plugins.

i-have-adhd

i-have-adhd

Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…

@ayghri@ayghriInstall Skill
ab-test-analysis

ab-test-analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop…

@phuryn@phurynInstall Skill
distilly

distilly

Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…

Questions about cowork-multi-agent-research.

Which coding agents can use cowork-multi-agent-research?
cowork-multi-agent-research installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.