Back to skills
SKILL.md
Agent Conductor
ASecurityOrchestrate coding sub-agents (Claude Code, Codex, Cursor, Gemini Code, or any CLI-based coding agent) for maximum throughput on implementation tasks. Use when: (1) writing or modifying code files, (2) running scripts or data pipelines, (3) batch processing large datasets, (4) multi-stage workflows requiring parallel execution. Covers agent-agnostic dispatch templates, task decomposition, parallel coordination, and acceptance criteria. NOT for: simple file reads, config-only changes, or sendi...
- 33 stars
- 0 votes
- 0 copies
- 0 views
- Added September 5, 2026
Works with
Security analysis
100/100Pro scans all 2 files and shows the line behind each finding
npx -y skills add dvcrn/openclaw-skills-marketplace --skill agent-conductor --agent claude-codeAre you the author of Agent Conductor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/dvcrn-agent-conductor)---
name: agent-conductor
description: "Orchestrate coding sub-agents (Claude Code, Codex, Cursor, Gemini Code, or any CLI-based coding agent) for maximum throughput on implementation tasks. Use when: (1) writing or modifying code files, (2) running scripts or data pipelines, (3) batch processing large datasets, (4) multi-stage workflows requiring parallel execution. Covers agent-agnostic dispatch templates, task decomposition, parallel coordination, and acceptance criteria. NOT for: simple file reads, config-only changes, or sending messages. Core principle β the orchestrator plans; the coding agents execute."
---
# Agent Conductor πΌ
**You conduct. Agents perform.**
Route all implementation work β file changes, scripts, data processing β to coding sub-agents. The orchestrating session stays lean: it plans, decides, and validates. Agents do the execution.
## Supported Agents
Agent-agnostic. Set your invoke command once:
| Agent | Invoke Command |
|-------|---------------|
| Claude Code | `claude '<task>'` |
| OpenAI Codex | `codex '<task>'` |
| Cursor Agent | `cursor-agent '<task>'` |
| Gemini Code | `gemini-code '<task>'` |
| Any other | `your-agent-cmd '<task>'` |
Use `AGENT_CMD` as a placeholder in the examples below.
## When to Dispatch
Dispatch when the task involves **any** of:
- Writing or modifying files (even one line)
- Running scripts or processing data
- Execution time > 10 seconds
- Batch operations over multiple items
*If it produces file changes β dispatch it.*
## Dispatch Template
```
## Task: [name]
### Requirement
[One sentence: what to produce and where]
### Context
- Project: [name and purpose]
- Relevant files: [paths]
- Data format: [brief description of inputs/outputs]
### Acceptance Criteria
- [ ] Output file exists at [path]
- [ ] Contains [N] records / passes [specific check]
- [ ] No errors in [error field / log]
### Gotchas
- [Known pitfall 1]
- [Known pitfall 2]
### Environment
- Language/runtime: [python3 / node / go / etc.]
- Working directory: [path]
- Special config: [proxy, auth, env vars if needed]
When done, notify with:
[your completion notification command]
```
## Execution Mechanism
| Duration | Mechanism |
|----------|-----------|
| < 5 min | Foreground: `exec pty:true command:"AGENT_CMD '...'"` |
| 5β30 min | Background: `exec pty:true background:true timeout:1800 command:"AGENT_CMD '...'"` |
| > 30 min | Agent writes script β run in `screen` / `tmux` |
> Use `pty:true` if your platform requires it (needed for Claude Code; check other agents' docs).
## Task Decomposition
Split large projects by **stage**, not by feature. Each stage must be independently verifiable.
**Split when any of these apply:**
- Runtime > 30 minutes
- More than one script needed
- Batch > 100 items
- Output of one step feeds the next
```
Stage 1: Prepare data β clean_data.csv (< 2 min)
Stage 2: Process β results.json (needs Stage 1)
Stage 3: Report β report.md (needs Stage 2)
```
See [references/patterns.md](references/patterns.md) for parallel coordination, checkpoint/resume, and domain examples.
## Acceptance Checklist
After any "done" signal, always verify:
1. **File exists** β confirm output path
2. **Count correct** β expected N vs. actual N records
3. **Non-empty** β spot-check 2β3 outputs
4. **No silent errors** β check error fields and null rates
*A completion signal β acceptance. Run the checklist.*
## Error Handling
| Symptom | Action |
|---------|--------|
| Timeout, no output | Check process log β kill and re-dispatch with more context |
| File missing after "done" | Read execution log β add context β re-dispatch |
| Partial completion | Check `progress.json` β resume from checkpoint |
| Fails twice in a row | Stop re-dispatching β debug in orchestrator session |
## What NOT to Dispatch
- Simple reads β use read tools directly
- Orchestrator config changes β orchestrator session only
- Messages/notifications β use messaging tools directly
- Design decisions β orchestrator decides first, agent implements
Files in this skill
- SKILL.md
- references/patterns.md
Attribution
Comments
Loading commentsβ¦