Content
100%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 instruction-only skill: lean, fully actionable with exact tool names, parameters, CLI fallbacks, and expected outputs, with explicit outcome validation and error-recovery loops for every branch including the batch case. There is no meaningful padding or structural waste.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and lean with zero padding: every line carries operational knowledge Claude would not have (tool names, the deferred-schema guard behavior, per-error semantics like "`cancellation_requested` means the live worker was asked to stop and will record the cancellation itself"). Nothing explains concepts Claude already knows, so it fits the 'every token earns its place' anchor rather than the 'minor trimming' anchor at 4. | 5 / 5 |
Actionability | Fully executable guidance for an instruction-only skill: exact tool calls with parameters ("call `ouroboros_cancel_execution` with `execution_id` and, if the user gave one, `reason`"), copy-paste CLI commands ("`ouroboros cancel execution --list`", "`--reason \"<text>\"`"), and exact discovery strings ("`+ouroboros project status`"). All common branches (no ID, ID given, --all, no MCP server) are covered, matching anchor 5; per the rubric's scoring notes, the absence of literal code blocks is not penalized for MCP-tool skills when guidance is this concrete. | 5 / 5 |
Workflow Clarity | Clear branching sequence by input form with explicit validation checkpoints ("`new_status` `cancelled` means it is cancelled"), feedback loops for error recovery ("'Failed to persist cancellation' is retriable; retry once", "skip it with a warning" for terminal-state errors during batch cancel), and a verification step ("suggest `ooo status` to confirm"). The destructive/batch cap at 3 does not apply because validation and error-recovery steps are present throughout. | 5 / 5 |
Progressive Disclosure | The body is roughly 40 lines, needs no external reference files, and is cleanly organized into a usage block, an Instructions section with subsections, a Fallback section, and a footer convention. Per the judging guideline, a skill under 50 lines with no need for external references scores 5 on well-organized sections alone; no bundle files exist to verify and none are referenced. | 5 / 5 |
Total | 20 / 20 Passed |