Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Coordinate assigned specialist tasks and handoffs manually. An agent skill from first-fluke/oh-my-agent.
Install Oma Coordination
$ npx skills add first-fluke/oh-my-agent --skill oma-coordination -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install first-fluke/oh-my-agent oma-coordination --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/oma-coordination .claude/skills/oma-coordination && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "oma-coordination" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-coordination into .claude/skills/oma-coordination/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-coordination", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-coordinationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add first-fluke/oh-my-agent --skill oma-coordination -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install first-fluke/oh-my-agent oma-coordination --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/oma-coordination .agents/skills/oma-coordination && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oma-coordination" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-coordination into .agents/skills/oma-coordination/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-coordination", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-coordination -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install first-fluke/oh-my-agent oma-coordination --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/oma-coordination .cursor/skills/oma-coordination && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oma-coordination" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-coordination into .cursor/skills/oma-coordination/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-coordination", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/first-fluke/oh-my-agent.git --path skills/oma-coordination--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add first-fluke/oh-my-agent --skill oma-coordination -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install first-fluke/oh-my-agent oma-coordination --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/oma-coordination .gemini/skills/oma-coordination && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oma-coordination" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-coordination into .gemini/skills/oma-coordination/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-coordination", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install first-fluke/oh-my-agent oma-coordinationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add first-fluke/oh-my-agent --skill oma-coordination -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/oma-coordination .github/skills/oma-coordination && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oma-coordination" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-coordination into .github/skills/oma-coordination/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-coordination", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-coordination -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install first-fluke/oh-my-agent oma-coordination --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/oma-coordination .opencode/skills/oma-coordination && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oma-coordination" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-coordination into .opencode/skills/oma-coordination/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-coordination", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
oma-coordination- GitHub stars
- 1.3k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 833 words
- Files
- 1
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- MIT
At a glance
Coordinate assigned specialist tasks and handoffs manually. An agent skill from first-fluke/oh-my-agent.
- Works in 4 steps: Plan with PM Agent → Spawn Agents by Priority → Monitor & Coordinate → …
- Supervising a multi-agent project step by step
- SKILL.md covers Scheduling, Structural Flow, Logical Operations and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Oma Coordination is an agent skill from first-fluke/oh-my-agent. Coordinate assigned specialist tasks and handoffs manually. Use when supervising a multi-agent project step by step.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: Mechanical verification for AI coding agents — skills pack or full harness (stop-hook gates, artifact checks, independent judges). The licence is MIT.
When your agent uses it
- Supervising a multi-agent project step by step
- Tasks that involve Multi-agent orchestration
Example prompts
- “/oma-coordination”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b364119. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Oma Coordination loads about 1.9k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 833 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from first-fluke/oh-my-agent at commit b364119, republished under its MIT licence (© first-fluke). 833 words, ~1,886 tokens.
Download SKILL.mdSave it as
.claude/skills/oma-coordination/SKILL.md (or your agent's skills folder).- name
- oma-coordination
- description
- Coordinate assigned specialist tasks and handoffs manually. Use when supervising a multi-agent project step by step.
Multi-Agent Workflow Guide
Scheduling
Goal
Guide manual multi-agent coordination for complex work that spans PM, frontend, backend, mobile, and QA responsibilities.
Intent signature
- User wants step-by-step coordination, manual agent spawning, or multi-domain work planning without full automation.
- Task spans multiple specialist agents and requires contract alignment.
When to use
- Complex feature spanning multiple domains (full-stack, mobile)
- Coordination needed between frontend, backend, mobile, and QA
- User wants step-by-step guidance for multi-agent coordination
When NOT to use
- Simple single-domain task -> use the specific agent directly
- User wants automated execution -> use orchestrator
- Quick bug fixes or minor changes
Expected inputs
- Complex feature or project goal
- Required domains and priority tiers
- Workspace/session constraints and API/data contract needs
Expected outputs
- Manual coordination sequence
- PM task decomposition, agent spawn order, monitoring guidance, and QA review step
- API/data contract alignment checkpoints
Dependencies
- PM, frontend, backend, mobile, QA, and orchestrator skills
- CLI
oma agent spawnand progress/result memory conventions
Control-flow features
- Branches by task complexity, priority tiers, dependency ordering, and whether automation is desired
- Spawns independent same-priority tasks in parallel when appropriate
- Monitors progress files and contract alignment
Structural Flow
Entry
- Confirm the task is complex enough for multi-agent coordination.
- Reuse a current plan and handoff state; use PM when task decomposition or contract changes are needed.
- Identify priority tiers and shared contracts.
Scenes
- PREPARE: Define session, domains, and task decomposition needs.
- ACT: Spawn agents by priority with separate workspaces.
- VERIFY: Monitor progress and API/data contract alignment.
- FINALIZE: Run QA review and coordinate remediation.
Transitions
- If task is simple, route to one specialist.
- If user wants automated execution, use orchestrator.
- If QA reports a blocking defect or required verification gap, route the affected work to the responsible agent within the existing recovery budget.
Failure and recovery
- If contracts diverge, pause downstream frontend/mobile work until backend/API contract is reconciled.
- If agent workspaces conflict, split ownership boundaries.
- If progress stalls, inspect progress files and reissue focused instructions.
Exit
- Success: specialist outputs are coordinated and QA-reviewed.
- Partial success: blocked agents, contract conflicts, or QA failures are explicit.
Logical Operations
Actions
| Action | SSL primitive | Evidence |
|---|---|---|
| Read request and domains | READ | User prompt and project context |
| Select agent plan | SELECT | PM decomposition and priority tiers |
| Spawn agents | CALL_TOOL | oma agent spawn |
| Monitor progress | READ | injected task/run-scoped progress, claims, and receipts |
| Validate contracts | VALIDATE | API/data model alignment |
| Notify coordination status | NOTIFY | Final coordination summary |
Tools and instruments
oma agent spawn, PM/frontend/backend/mobile/QA agents- Memory/progress/result files
- Configured code intelligence, with native fallback per
../_shared/core/code-intelligence.md
Canonical command path
# If planning is required, dispatch the declared PM task first; otherwise reuse the current plan.
oma agent spawn pm <pm-prompt-file> <session-id> --task-id <plan.pm_task.id> -w ./pm
oma agent spawn backend <backend-prompt-file> <session-id> --task-id <plan.backend_task.id> -w ./backend &
oma agent spawn frontend <frontend-prompt-file> <session-id> --task-id <plan.frontend_task.id> -w ./frontend &
waitWhen native runtime dispatch is available (per-agent target vendor equals the current runtime vendor), prefer the runtime's native subagent path and use oma agent spawn as the cross-vendor fallback — same resolution rule as oma-orchestration.
Useful agent spawn options: --vendor <vendor> (CLI vendor override), --isolation worktree (git worktree per spawn, prevents file conflicts), --read-only (non-destructive tools only, e.g. for review/QA passes).
Resource scope
| Scope | Resource target |
|---|---|
LOCAL_FS | Progress/result files and workspaces |
PROCESS | Agent spawn commands |
MEMORY | Session state and task board |
CODEBASE | Shared contracts and implementation areas |
Show full SKILL.md (329 more words)Show less
Preconditions
- Task requires multiple domains.
- A current plan identifies task ownership, acceptance checks, dependencies, and priority tiers.
Effects and side effects
- Spawns or guides multiple agents.
- Coordinates workspace ownership and QA feedback.
Guardrails
- Reuse a valid plan; call PM only when decomposition or contract changes are required
- Spawn independent tasks in parallel (same priority tier)
- Reuse or update contracts for changed API boundaries before dependent frontend/mobile work
- QA review is always the final step
- Assign separate workspaces to avoid file conflicts (or use
--isolation worktreefor a git worktree per spawn) - Follow
../_shared/core/code-intelligence.md: discover configured tools, do not auto-install or track, and use native search only for paths outside this project or ignored paths when unavailable or timed out - Resume from the current handoff state and execute applicable steps in dependency order; record why a branch is not applicable
Workflow
Step 1: Plan with PM Agent
Reuse an existing valid plan. Otherwise, PM analyzes requirements and creates the task breakdown, acceptance checks, contracts, and priorities. Preserve injected session/task/run IDs; do not regenerate a plan already frozen by dispatch.
Step 2: Spawn Agents by Priority
Resolve the dispatch path per agent, then spawn:
- Resolve the per-agent target vendor from oma-config.yaml (
agents:override, elsemodel_preset) - If the target vendor equals the current runtime vendor and a native subagent path exists, use native dispatch
- Otherwise use
oma agent spawnfor that agent - Spawn all same-priority tasks in parallel using background processes
# Example: spawn backend and frontend in parallel
oma agent spawn backend backend-prompt.md session-id --task-id plan.backend_task.id -w ./backend &
oma agent spawn frontend frontend-prompt.md session-id --task-id plan.frontend_task.id -w ./frontend &
waitStep 3: Monitor & Coordinate
- Read injected run artifacts and receipts. Human-readable progress/results use
{memoryConfig.basePath}/progress-{agentId}-{taskId}-{runId}-{sessionId}.mdand the correspondingresult-name; see../_shared/runtime/memory-protocol.md. Keep the structured claim path unchanged. - Verify API contracts align between agents
- Ensure shared data models are consistent
Step 4: QA Review
Review the coordinated deliverables with QA. Resolve blocking defects and required verification gaps through the responsible agents; rerun affected checks before finalizing.
Automated Alternative
For fully automated execution without manual spawning, use the orchestrator skill instead.
References
© first-fluke, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/oma-coordination of first-fluke/oh-my-agent.
Open the folder on GitHubat commit b364119
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in first-fluke/oh-my-agent, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Oma Coordination next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oma Coordination this skillfirst-fluke/oh-my-agent | 1.3k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Orca CLIstablyai/orca | 88k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Mission Control Agent APIbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Mission Control Agent API
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
More from first-fluke/oh-my-agent
All 57 skills in this repoOMA Multi-Agent Orchestration
first-fluke/oh-my-agent
Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.
OMA Multi-Agent Orchestrator
first-fluke/oh-my-agent
Splits a complex feature into prioritized tasks, spawns specialist CLI subagents in parallel, tracks them through shared memory and verifies each result.
Architecture Decisions and ADRs
first-fluke/oh-my-agent
Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.
OMA Backend Agent
first-fluke/oh-my-agent
Backend specialist for APIs, database work, authentication and migrations that follows clean architecture with router, service and repository layers.
oma Bootstrap
first-fluke/oh-my-agent
Installs or checks the oma CLI and its runtimes (bun, uv, serena) in a fresh workspace so that oma-* skills can run their commands.
Design-First Brainstorm
first-fluke/oh-my-agent
Explores intent, constraints and alternative approaches before any planning, working through questions one at a time and saving an approved design for later steps.
Related
Categories
Questions about Oma Coordination
What does Oma Coordination do?
Coordinate assigned specialist tasks and handoffs manually. An agent skill from first-fluke/oh-my-agent. Oma Coordination is an agent skill from first-fluke/oh-my-agent. Coordinate assigned specialist tasks and handoffs manually.
When should I use Oma Coordination?
Oma Coordination fits situations like: supervising a multi-agent project step by step; tasks that involve Multi-agent orchestration.
How do I install Oma Coordination in Claude Code?
Run `npx skills add first-fluke/oh-my-agent --skill oma-coordination -a claude-code`. Or copy the skill folder (skills/oma-coordination in first-fluke/oh-my-agent) into .claude/skills/oma-coordination in your project. Claude Code loads it when a task matches its description.
How do I install Oma Coordination in Codex?
Run `npx skills add first-fluke/oh-my-agent --skill oma-coordination -a codex`. Or copy the skill folder (skills/oma-coordination in first-fluke/oh-my-agent) into .agents/skills/oma-coordination in your project. Codex loads it when a task matches its description.
Can I use Oma Coordination in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add first-fluke/oh-my-agent --skill oma-coordination -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oma-coordination, .gemini/skills/oma-coordination, .github/skills/oma-coordination and .opencode/skills/oma-coordination in your project.
What does Oma Coordination need to run?
SKILL.md names no scripts, command-line tools or credentials: Oma Coordination is instructions for the agent only.
Does Oma Coordination access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Oma Coordination safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Oma Coordination use?
Oma Coordination is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Oma Coordination use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Oma Coordination?
Skills that share tags, products or a category with Oma Coordination: Orca CLI (stablyai/orca, 88k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oma Coordination?
first-fluke (a GitHub organization) maintains it in first-fluke/oh-my-agent, which has 1,338 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 9, 2026.
Source: first-fluke/oh-my-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.