Content
88%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an exemplary lean orchestration skill: a clear A–F phase sequence with explicit verification, error-recovery loops, dropout handling, and tie-break rules, all written for a competent reader with no padding. The only soft spot is the long multi-provider routing paragraph inlined in Phase A, which is the sole candidate for extraction to a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean throughout and explains only operational specifics Claude would not know, e.g. "an unset mode resolves to `disabled` and all candidates would share one checkout". Even the intro rationale ("agreement across independent attempts is high-signal, and divergence exposes what the brief under-specified") directly drives Phase E behavior, so every token earns its place — anchor 5, above 4 (no trimmable over-explanation found). | 5 / 5 |
Actionability | Provides a copy-paste command (`OMC_TEAM_WORKTREE_MODE=detached omc team --no-decompose 1:claude,1:codex,1:gemini "<brief>"`), concrete config paths (`.claude/omc.jsonc`, `omc config`), and explicit failure-handling branches (dropout replacement, cross-family fallback). Some directives remain abstract ("Fold grafts in by hand so the result stays coherent"), matching anchor 4 — mostly executable with minor gaps — below 5. | 4 / 5 |
Workflow Clarity | Phases A–F are clearly sequenced with explicit validation and feedback loops: Phase F requires verification under "real command output, fresh evidence. Do not paper over it", and failures route backward ("either the rubric was wrong (reframe and rerun) or a graft was missed (back to Phase E)"). Phase D adds tie-break rules and Phase B dropout handling — anchor 5. | 5 / 5 |
Progressive Disclosure | A well-sectioned, self-contained single file (~107 lines) with no nested or buried references; external skill references (`verify`, `execute`, `research`) are clearly signaled. The dense multi-provider routing block in Phase A step 3 is the one stretch of config detail inlined where a separate reference file could sit — anchor 4, above 3 but short of the ideal split. | 4 / 5 |
Total | 18 / 20 Passed |