Agent skill · AI & Agents

oma-orchestrator

Automated multi-agent orchestrator that spawns CLI subagents in parallel, coordinates via MCP Memory, and monitors progress. Use for orchestration, parallel execution, and automated multi-agent workflows.

first-flukegithub.com/first-flukeGitHub ↗
claude-codecodexcursorships scriptsMIT
Install
npx skills add first-fluke/oh-my-agent --skill oma-orchestrator --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 13
SKILL.md size: 16 KB
Bundled scripts: yes
Path: .agents/skills/oma-orchestrator/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,204
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Orchestrator - Automated Multi-Agent Coordinator ## Scheduling ### Goal Automatically orchestrate multi-agent execution with task decomposition, native/fallback dispatch, memory coordination, progress monitoring, verification, QA cross-review, retry, and result collection. ### Intent signature - User asks to orchestrate, run in parallel, automate multi-agent execution, or coordinate full-stack work end to end. - Task requires multiple specialist agents and a persistent review/remediation loop. ### When to use - Complex feature requires multiple specialized agents working in parallel - User wants automated execution without manually spawning agents - Full-stack implementation spanning backend, frontend, mobile, and QA - User says "run it automatically", "run in parallel", or similar automation requests ### When NOT to use - Simple single-domain task -> use the specific agent directly - User wants step-by-step manual control -> use oma-coordination - Quick bug fixes or minor changes ### Expected inputs - Complex feature or workflow request - Project config, model/vendor routing, agent types, task constraints, and workspace/session needs - Acceptance criteria and verification expect

What's inside
Steps it walks through
  1. Scheduling
  2. Goal
  3. Intent signature
  4. When to use
  5. When NOT to use
  6. Expected inputs
  7. Expected outputs
  8. Dependencies
  9. Control-flow features
  10. Structural Flow
  11. Entry
  12. Scenes
  13. Transitions
  14. Failure and recovery
Ships with 12 files
  • config/cli-config.yaml
  • resources/memory-schema.md
  • resources/subagent-prompt-template.md
  • scripts/parallel-run.sh
  • scripts/spawn-agent.sh
  • scripts/verify.sh
  • templates/backend-task.md
  • templates/debug-task.md
  • templates/frontend-task.md
  • templates/mobile-task.md
  • templates/qa-task.md
  • templates/tasks-example.yaml
Commands it runs
oma agent:spawn <agent-type> "<task>" <session-id> -w <workspace>
oma verify <agent-type> --workspace <workspace> --json
oma verify {agent-type} --workspace {workspace} --json
More from oh-my-agent
All skills →
About this skill
What does the oma-orchestrator skill do?

Automated multi-agent orchestrator that spawns CLI subagents in parallel, coordinates via MCP Memory, and monitors progress. Use for orchestration, parallel execution, and automated multi-agent workflows.

How do I install it?

Run `npx skills add first-fluke/oh-my-agent --skill oma-orchestrator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going