oma-coordination

Guide for coordinating PM, Frontend, Backend, Mobile, and QA agents on complex projects via CLI. Use for manual step-by-step coordination and workflow guidance.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-coordination/SKILL.md

Quality

Content

67%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 clear, actionable multi-agent coordination workflow with concrete commands, sequencing, checkpoints, and recovery handling. Its main weakness is conciseness, with redundant template-style sections and duplicated command blocks that could be consolidated.

Suggestions

Consolidate the duplicated oma agent spawn command blocks (Logical Operations canonical path and Step 2) into one location, referencing it from the other.

Trim or remove abstract template tables (SSL primitives, Resource scope) that do not add executable guidance beyond the surrounding prose.

Merge the overlapping Scheduling subsections (Intent signature, When to use, Expected inputs/outputs) into a single concise block to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is well sectioned but contains redundant/abstract template-filling (the SSL-primitive Actions table, Resource-scope table, duplicated spawn command blocks, and overlapping When-to-use/Intent-signature/Expected-inputs sections) that could be tightened.	3 / 5
Actionability	Provides concrete executable commands (oma agent spawn with workspace flags), documents spawn options (-m/--model, --isolation worktree, --read-only), and gives the progress-{agent}[-{sessionId}].md naming convention; a few steps remain abstract ("Select agent plan", "Validate contracts").	4 / 5
Workflow Clarity	Clear sequenced flow (Entry, PREPARE/ACT/VERIFY/FINALIZE scenes, Steps 1-4) with monitoring and QA review checkpoints plus failure-recovery feedback (contract divergence pauses downstream work; CRITICAL issues re-spawn agents), with only minor validation gaps.	4 / 5
Progressive Disclosure	A single self-contained file organized into clearly signaled sections (Scheduling, Structural Flow, Logical Operations, Workflow); no external bundle references exist or are needed, and the empty References section introduces no nested navigation.	4 / 5
	Total	15 / 20 Passed

Description

70%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.

The description clearly names the domain, roles, and both the what and when, with good natural trigger terms. It is held back from a top score by somewhat generic action verbs and a when clause that could be more explicitly tied to concrete trigger phrases.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete roles (PM, Frontend, Backend, Mobile, QA) plus a couple actions ("coordinating...agents", "manual step-by-step coordination and workflow guidance"), but the actions remain generic rather than comprehensive.	3 / 5
Completeness	Explicitly answers both what ("Guide for coordinating...agents on complex projects via CLI") and when ("Use for manual step-by-step coordination and workflow guidance"), but the when clause could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ("multi-agent coordination", "step-by-step coordination", "workflow guidance", role names, "CLI") with good coverage, though a few synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (CLI-based manual multi-agent coordination across specific specialist roles) with mostly distinct triggers; minor overlap risk with the related orchestrator skill.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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-coordination/SKILL.md
Commit: 7721120

Reviewed: ~15 hours ago

Table of Contents

Discovery Implementation Validation

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.