Skip to content
Skills Library
AI & agents · Automation

using-orchestration

/using-orchestration

Use when user has complex multi-agent workflows, needs to coordinate sequential or parallel agent execution, wants workflow visualization and control, or mentions automating repetitive multi-agent processes - guides discovery and usage of the orchestration system

Licence
MIT
Last repository change
01.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when user has complex multi-agent workflows, needs to coordinate sequential or parallel agent execution, wants workflow visualization and control, or mentions automating repetitive multi-agent processes - guides discovery and usage of the orchestration system

Original author description

Use when user has complex multi-agent workflows, needs to coordinate sequential or parallel agent execution, wants workflow visualization and control, or mentions automating repetitive multi-agent processes - guides discovery and usage of the orchestration system

How it works

  1. When to Suggest
  2. How to Introduce
  3. Quick Syntax Reference
  4. When NOT to Suggest
  5. Integration Pattern
Original SKILL.md headings · 77 lines, 325 words
SKILL.md preview
---
name: using-orchestration
description: Use when user has complex multi-agent workflows, needs to coordinate sequential or parallel agent execution, wants workflow visualization and control, or mentions automating repetitive multi-agent processes - guides discovery and usage of the orchestration system
---

# Using the Orchestration System

## When to Suggest

Proactively suggest `/orchestrate` when user describes:

**Clear Triggers:**
- Multiple agents needed in sequence: "explore then review then implement"
- Parallel operations: "run tests and lint at the same time"
- Conditional workflows: "if tests pass, deploy; if failed, fix and retry"
- Retry logic: "keep trying until it works"
- Workflow automation: "I do this same process often"
- Multiple checkpoints: "I want to review before deploying"

**Specific Phrases:**
- "coordinate multiple agents"
- "workflow", "pipeline", "orchestrate"
- "run these in parallel"
- "if X then Y"
- "retry until success"
- "automate this process"

## How to Introduce

When triggers detected, suggest proactively:

```
This workflow would benefit from orchestration. I can use `/orchestrate` to:
- Visualize the workflow graph
- Execute agents in parallel where possible
- Handle retries and conditionals
- Provide interactive control at checkpoints

Would you like me to use `/orchestrate [workflow-syntax]` or create a reusable template?
```

**First-time setup reminder:**

If user mentions custom agents (like `expert-code-implementer`, `code-optimizer`, etc.) that aren't in the orchestration namespace:

```
I notice you have custom agents in your environment.
Would you like to import them to orchestration first?

Run: /orchestration:init

This will make your custom agents available in workflows as:
- orchestration:expert-code-implementer
- orchestration:code-optimizer
- etc.
```

## Quick Syntax Reference

Show relevant syntax based on user's needs:

**Sequential:** `explore:"task" -> review -> implement`
**Parallel:** `[test || lint || security]`
**Conditional:** `test (if passed)~> deploy`
**Retry:** `@try -> fix -> test (if failed)~> @try`

## When NOT to Suggest

- Single agent task (no coordination needed)
- Simple sequential tasks (<3 steps, no conditionals)
- User explicitly requests manual coordination
- Task already in progress without orchestration

## Integration Pattern

When user agrees to orchestration:
1. Parse their requirements into workflow syntax
2. Invoke `/orchestrate [workflow-syntax]`
3. Let the orchestration system handle execution
4. Don't manually coordinate agents - let orchestrator do it

Versions

The database has no other skills named using-orchestration.

Database snapshot: 13.11.2026 · package version 51790c12559d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100workflow-orchestration
    Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow",…
  • 100agent-chaining
    Use when designing or reviewing multi-agent systems, subagent orchestration, parallel vs sequential agent execution, context passing between agents, tool delegation, and agent memory patterns. Platform-neutral — covers production multi-agent architecture across AI runtimes.
  • 100agenticx-workflow-designer
    Guide for designing and running AgenticX workflows including sequential pipelines, parallel execution, graph-based orchestration, conditional routing, and trigger services. Use when the user wants to create workflows, orchestrate multiple agents, design agent pipelines, or set…
  • 93orchestration
    Multi-agent workflow orchestration with state tracking, checkpointing, and cross-pollinated pipelines. Use when coordinating parallel agent pipelines, managing sync barriers, or tracking complex workflow execution state across sessions.
  • 100orchestration-workflow
    Guide for working with the multi-agent orchestration system in DEVS. Use this when asked to modify task orchestration, agent coordination, or workflow execution.
  • 95agentic-orchestration
    Patterns for multi-agent coordination, task decomposition, handoffs, and workflow orchestration. Best practices for building and managing agent systems. Use when designing how multiple agents coordinate — splitting up tasks, defining handoffs, or choosing an orchestration topology.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.