/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',
$ npx -y skills add CoWork-OS/CoWork-OS --skill cowork-multi-agent-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/cowork-multi-agent-research
Context preview
The summary Claude sees to decide when to auto-load this skill.
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',
SKILL.md
cowork-multi-agent-research.SKILL.mdname: 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'."
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
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'."
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).
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /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 finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /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 for full PR, commit, branch, patch, or repository scans.
Open skill - /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 change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill