Content
93%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.
An exemplary lean skill body: concrete copy-paste commands with non-obvious behavioral notes (exit codes, prompt behavior, read-only guarantees) and a well-sequenced decision workflow covering found, not-found, and stuck-session outcomes. The only minor gaps are unhandled recovery paths for an unreadable EventStore or a missing Seed file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every token is operational detail Claude cannot know: "Exit code 2 means the EventStore exists but could not be read", "--list prints the table and exits without the interactive prompt, which aborts when no terminal is attached", and the read-only guarantees. Only the one-line naming rationale ("The name avoids shadowing Claude Code's built-in /resume") is trimmable, which is too minor for the anchor-4 'minor instances of over-explanation'. | 5 / 5 |
Actionability | Fully executable, copy-paste-ready commands with flags: "ouroboros resume --list", "ouroboros status execution <exec_id> --events", "ouroboros tui monitor", "ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>", plus follow-ups "ooo evaluate" and "ooo cancel <session_id>". Placeholders are explicitly sourced ("Each row carries the session_id, exec_id, and Seed id"), and the found/not-found/stuck cases are all covered. | 5 / 5 |
Workflow Clarity | Clear three-step sequence (list → ask the user which session → give the matching re-attach path) with outcome branches for "No in-flight sessions found" and exit code 2, and explicit next actions ("ooo evaluate once the execution completes, or ooo cancel <session_id> if it is stuck"). Not 5 because recovery for an unreadable EventStore (exit code 2) and a missing Seed file is explained-but-not-handled — minor validation gaps per anchor 4; the operations are read-only/non-destructive so the destructive-cap does not apply. | 4 / 5 |
Progressive Disclosure | A single-purpose skill under 50 lines with no external reference files needed (no references/, scripts/, or assets/ exist), organized into clear sections (usage, Instructions with the three re-attach paths, breadcrumb footer). Per the rubric's simple-skill scoring note, well-organized sections alone merit 5 here. | 5 / 5 |
Total | 19 / 20 Passed |