Content
92%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.
Excellent operational content: exact executable commands, sequenced flows with explicit validation and error-recovery loops, and a well-structured bundle whose referenced files all exist. The single deduction is duplicated retry/fallback guidance repeated across three sections, which inflates token cost without adding information.
Suggestions
State the retry-once policy in one authoritative place (e.g., the fallback ladder) and have the 'Free models are not always up' section and the anti-patterns table reference it instead of restating it.
Merge the overlapping escalation rules — the swarm flow's 'escalate to your own Sonnet … fails twice' and the fallback ladder's step 2 'orchestrator performs that subtask inline' — into a single, consistent escalation path.
Consider moving the Windows-specific resolver notes ('Windows notes (hard-won)') into a short reference file, keeping SKILL.md to the one-line OPENCODE_GIT_BASH_PATH prerequisite.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and table-driven with no explanations of concepts Claude already knows, but retry-once guidance is stated redundantly in three places ("Free models are not always up", the "Fallback ladder", and the "Retrying a failing worker indefinitely" anti-pattern row), which is trimmable duplication. This fits anchor 4 ('minor instances that could be trimmed') rather than anchor 5, where every token would earn its place. | 4 / 5 |
Actionability | Invocations are copy-paste ready with exact flags, return shapes, and env vars: "node \"<skill-dir>\\scripts\\oc-worker.mjs\" [--agent scout|coder|tester] [--dir <path>] …", "git worktree add ../<repo>-wt-N -b swarm/N", and "node scripts/oc-verify.mjs --dir <same dir the worker saw> --claims findings.json --run <id>". Specific commands cover the common cases, matching the anchor-5 'fully executable' example. | 5 / 5 |
Workflow Clarity | The swarm flow is a numbered 1-6 sequence with explicit validation checkpoints ("Review every diff yourself", "YOU are the only merger", "run tests"), and the fallback ladder plus the oc-verify stage provide explicit error-recovery feedback loops for batch operations. This matches anchor 5's 'clear sequence with explicit validation steps; feedback loops for error recovery' — no checkpoint is missing or implicit. | 5 / 5 |
Progressive Disclosure | The body is an overview with a components table routing to every bundle file (all verified to exist on disk), with command definitions split into assets/commands/ and worker personas into assets/agents/ — one level deep and clearly signaled. Nothing that belongs in a separate file is inlined, matching anchor 5 rather than anchor 4's 'minor organization gaps'. | 5 / 5 |
Total | 19 / 20 Passed |