CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-orchestration

Dispatch and supervise parallel specialist agents with durable task state. Use for automated multi-agent execution, to coordinate agents step by step, or to hand a task to a named vendor or model.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a genuinely executable orchestration workflow: copy-paste-ready commands with flags, an explicit phase sequence, a validation-heavy agent-to-agent review loop with limits and recovery budgets, and tables for configuration and file ownership. Its weaknesses are repetition of the PHASE 4.5 material across three sections, some phase steps that direct without giving a mechanism, and a reference layer where most pointed-to files are missing from the bundle.

Suggestions

State the PHASE 4.5 verification loop once (in the Agent-to-Agent Review Loop section) and have the Canonical command path and Workflow Phases reference it, removing the duplicated supported-agent-type lists.

Make the abstract phase steps executable — for example, specify the concrete tool calls or memory-provider operations behind "initialize the task board and memory files" in PHASE 2.

Resolve the dangling references: either ship `resources/subagent-prompt-template.md`, `resources/memory-schema.md`, and the referenced `../_shared/*` and `config/` files in the bundle, or trim the References list to what is actually distributed and inline the essential content.

DimensionReasoningScore

Conciseness

The body is dense and mostly operational, but the PHASE 4.5 verification content is stated three times (Canonical command path step 7, Workflow Phases, and the Agent-to-Agent Review Loop section) with the supported-agent-type list repeated verbatim, and asides like "Reason: Self-evaluation bias causes agents to consistently overrate their own output (ref: Anthropic harness design research)" pad beyond what the executor needs. This matches anchor 3's "mostly efficient but includes some unnecessary explanation or could be tightened" rather than anchor 4, where only minor trimming would be needed.

3 / 5

Actionability

Concrete, executable commands are given throughout — `oma agent spawn <agent-type> <prompt-file> <session-id> --task-id <task.id> -w <workspace>` with documented flags, `oma verify agent {agent-type} --workspace {workspace} --json`, `oma agent batch ... --check "<command with {item}>"`, plus a config JSON example, settings table, and a filled-in review feedback template. It sits at anchor 4 rather than 5 because several phase steps remain directive but not executable (e.g., "set the session ID and initialize the task board and memory files" specifies no concrete mechanism), and the referenced `resources/` templates that would complete them are absent from the bundle.

4 / 5

Workflow Clarity

The canonical command path numbers steps 1–9 across named phases, the review loop flow diagram shows explicit PASS/FAIL branches back to step [1], `oma verify` exit codes (0 = proceed, 1 = feed back as correction) are specified, and loop limits, recovery budgets, and escalation outcomes are tabulated. This matches anchor 5's "clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes" — a batch/parallel dispatch skill whose validation coverage is thorough, so no cap applies.

5 / 5

Progressive Disclosure

The References section is clearly signaled with purpose annotations, but scored against the actual bundle only the three `scripts/*.sh` files exist; the `resources/subagent-prompt-template.md`, `resources/memory-schema.md`, `config/cli-config.yaml`, and every `../_shared/*` path are dangling, and the ~280-line body inlines substantial policy (review-loop step details, recovery budget rules) that could live one level deeper. This lands on anchor 3's "references present but not clearly signaled" territory in effect — structure exists, but organization and resolvability gaps keep it below anchor 4's "most content is appropriately placed".

3 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly and explicitly states both what the skill does and when to use it, with natural trigger phrasing and a distinct orchestration niche. Its only weaknesses are missing common trigger synonyms (notably "orchestrate" and "run in parallel") and a slightly abstract capability statement in "durable task state".

DimensionReasoningScore

Specificity

"Dispatch and supervise parallel specialist agents with durable task state" names the domain and several concrete actions (dispatch, supervise, coordinate step by step, hand off to a named vendor/model), matching anchor 4's "several specific actions; minor gaps". It falls short of anchor 5 because "durable task state" is abstract and the full capability set (retry, verification, QA cross-review) is not enumerated in the description.

4 / 5

Completeness

The what is explicit ("Dispatch and supervise parallel specialist agents with durable task state") and the when is explicit with concrete trigger phrases ("Use for automated multi-agent execution, to coordinate agents step by step, or to hand a task to a named vendor or model"), which directly matches anchor 5's "clearly and explicitly answers both what AND when with concrete trigger phrases". Anchor 4 would require the 'when' to be less explicit than the three distinct trigger conditions given here.

5 / 5

Trigger Term Quality

The "when" clause gives natural phrases users would say — "automated multi-agent execution", "coordinate agents step by step", "hand a task to a named vendor or model" — giving good keyword coverage per anchor 4. Common variations like "orchestrate", "run it automatically", and "run in parallel" are missing, keeping it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche — parallel specialist-agent supervision with durable state and named vendor/model handoff — is mostly distinct with only minor overlap risk against generic delegation or single-agent dispatch skills, matching anchor 4. It is not anchor 5 because "automated multi-agent execution" could still overlap with other orchestration/subagent skills without sharper distinguishing triggers.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

first-fluke/oh-my-agent

Path

.agents/skills/oma-orchestration/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.