- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-coordination -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-coordination -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-coordination -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add first-fluke/oh-my-agent --skill oma-coordination -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/first-fluke/oh-my-agent/tree/HEAD/.agents/skills/oma-coordinationFrom the publisher
Supply the coordination rules every multi-agent run shares (plan reuse, contract alignment, workspace ownership, QA handoff), and guide manual step-by-step coordination when the user drives each dispatch.
/work, /orchestrate, /ultrawork) loads this skill and applies its Guardrails.oma-orchestration owns execution; this skill supplies only the rules it appliesoma-pm for decomposition, oma-qa for review, and oma-orchestration for dispatch resolution, the parallelism limit, the recovery budget, and the review loopoma agent spawn and the progress/result conventions in ../_shared/runtime/memory-protocol.mdoma-orchestration; the Guardrails below still apply.oma-orchestration defines: the runtime's native subagent path when the agent's target vendor equals the current runtime vendor, otherwise oma agent spawn.
# One spawn per ready task; agent, task ID, and workspace come from the current plan.
oma agent spawn <agent-id> <prompt-file> <session-id> --task-id <task.id> -w <workspace>
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).../_shared/core/execution-policy.md for the execution deadline, resource ownership, and cancellation. Read injected task/run-scoped progress, claims, run artifacts, and receipts; progress and result file names are defined in ../_shared/runtime/memory-protocol.md.Starts agent processes through the native subagent path or oma agent spawn, or guides the user through each dispatch. Reads progress and result files, session state, and the task board. Spawned agents edit shared contracts and implementation areas in their assigned workspaces; this skill coordinates workspace ownership and QA feedback.
oma-orchestration resolves from project configuration.oma-orchestration defines (verify, QA cross-review, fix, review again within the recovery budget), not a single final pass.--isolation worktree for a git worktree per spawn).../_shared/core/collaboration-policy.md (before assigning parallel work or coordinating peer issues, ownership handoffs, and result collection)../_shared/core/execution-policy.md (while agents run)../_shared/runtime/memory-protocol.md (when reading run artifacts)../oma-orchestration/SKILL.md (when dispatching or reviewing)Shared coordination rules for multi-agent work: plan reuse, contract alignment, workspace ownership, and QA handoff. Loaded by the /work, /orchestrate, and /ultrawork workflows; also use for manual st
---name: oma-coordinationdescription: Shared coordination rules for multi-agent work: plan reuse, contract alignment, workspace ownership, and QA…---# .agents/skills/oma-coordination/SKILL.mdOverview
Shared coordination rules for multi-agent work: plan reuse, contract alignment, workspace ownership, and QA handoff. Loaded by the /work, /orchestrate, and /ultrawork workflows; also use for manual step-by-step coordination.
FAQ
Download .agents/skills/oma-coordination/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/first-fluke/oh-my-agent.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.