Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →onewave-ai/sub-agent-orchestrator
Manages parent/child agent relationships with task delegation and result aggregation. Supports sequential chains, parallel fans, conditional routing, retry logic, timeout handling, and YAML-based visual workflow definition.
Passed 19 of 22 test cases with the skill, and 17 of 22 without it.
3 fixed18 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
The user submits: `Can you parse the structure of ./workflows/audit-pipeline.yaml and draw a diagram of the steps without executing it?` Which operational mode should be selected?
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies the mode as inspect. | Missed | Passed |
The instructions your model reads when the skill loads.
Design and execute multi-agent pipelines where each step is a different agent that depends on the previous one. Define roles, dependencies, and handoffs in YAML, then run sequential, parallel, conditional, loop, and map-reduce workflows with retry, timeout, and validation.
Unlike Agent Army (homogeneous parallel code changes) and Agent Swarm (homogeneous parallel data processing), this orchestrator coordinates heterogeneous pipelines where the output of A feeds the input of B.
references/patterns.md -- The six workflow patterns and the comparison to Agent Army/Swarm.references/workflow-schema.md -- Full YAML workflow definition language.references/examples.md -- Complete worked workflows (research-to-proposal, lead scoring).references/execution-engine.md -- Per-step execution model, retry, timeout, validation, edge cases.references/templates.md -- Reusable workflow scaffolds.references/visual-and-reporting.md -- Text diagrams and the execution report template.Determine the mode from the request:
references/workflow-schema.md), then show it for approval.references/visual-and-reporting.md).Parse and validate the workflow: confirm required fields, that agent IDs resolve, and that there are no circular dependencies. Report syntax or reference errors with the offending line. See references/execution-engine.md.
Resolve inputs: collect every required input from the user before starting; apply defaults for optional inputs.
Build the execution DAG and run each step in topological order using the matching execution model (sequential, parallel, conditional, loop, map). See references/execution-engine.md.
After each agent completes, validate its output against the agent's schema and rules. On failure, apply the retry/timeout/failure policy (skip, abort, or fallback).
On completion, present results using the execution report template in references/visual-and-reporting.md. For partial or failed runs, report what completed, what failed, and any collected partial output.
Match the task shape to a pattern, then scaffold from references/templates.md:
test cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.