Skip to content
Back to skills

Agent Orchestration

ASecurity

AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions.

  • 1,641 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsgosecurity

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add codeaholicguy/ai-devkit --skill agent-orchestration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Orchestration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Orchestration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/codeaholicguy-agent-orchestration/badge)](https://www.skillsdirectory.com/skills/codeaholicguy-agent-orchestration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-orchestration
description: "AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions."
---

# Agent Orchestration

Use only for multi-agent supervision: coordinating dependencies, polling progress, unblocking waiting agents, relaying outputs, resolving conflicts, and verifying completion across agents. For one-off list/detail/send/start/kill work, use `$agent-management` or `$agent-communication`.

Use `$agent-management` for safe agent selection and lifecycle actions. Use `$agent-communication` for list/detail/send mechanics. Use `$verify` before accepting any agent's completion claim.

## Rules

- Own the loop until assigned work is complete, blocked, or stopped.
- Run `agent list --json` before each pass; never assume names/statuses.
- Inspect waiting, idle, unknown, missing, or stale agents before acting.
- Send self-contained instructions and avoid duplicate follow-ups.
- Sequence agents that touch the same files; relay only relevant upstream output.
- Escalate only for repeated failures, unresolved conflicts, product/business decisions, or destructive/shared/production/security-sensitive actions.

## Loop

If the goal or agent ownership is unclear, run one scan/detail pass. Ask the user once only if context is still insufficient.

1. Scan agents.
2. Assess agents needing attention with `detail --tail 10`.
3. Act: approve, clarify, correct, delegate, relay, verify, or escalate.
4. Report one brief status line.
5. Sleep 10-60s and repeat.

## Completion

Finish when all assigned work is verified, blocked with a clear reason, or stopped by the user. Summarize per-agent outcomes, verification, unresolved issues, and next step.

Files in this skill

  • SKILL.md1.9 KB
  • agents/openai.yaml406 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.