Content
65%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 a tight, well-structured overview that routes to a production stack and catalogs failure modes and recovery moves, scoring well on conciseness and organization. Its weaknesses are missing execution details for the loop modes themselves and absent validation checkpoints in the recovery workflow.
Suggestions
Add a minimal invocation example or command for at least the default `sequential` loop mode so the reader knows how to start a loop, not just which one to pick.
Insert an explicit validation checkpoint in the recovery workflow (e.g. 'after `/harness-audit`, confirm the root cause is identified before reducing scope') and mark the recovery steps as an ordered sequence.
Move the 'v1.8+ canonical name / supersedes autonomous-loops' note into a short 'Deprecated aliases' section so version-sensitive details don't decay the main guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no over-explanation of known concepts, but the opening 'This is the v1.8+ canonical loop skill name. It supersedes `autonomous-loops` while keeping compatibility for one release' is time-sensitive version information outside any 'old patterns'/'deprecated' section, incurring the rubric's minor penalty. | 4 / 5 |
Actionability | There are some concrete anchors (a decision tree with explicit criteria, named tools like `ralphinho-rfc-pipeline`, `eval-harness`, `nanoclaw-repl`, and the `/harness-audit` command), but the skill never explains how to actually start or invoke any of the loop modes — the core execution detail is missing. | 3 / 5 |
Workflow Clarity | Sequences are present (the selection flow and the recovery ordering of freeze → audit → reduce scope → replay), but validation checkpoints are absent or implicit, and loop automation is a batch-style repeated operation where the rubric caps workflow clarity at 3 without explicit validation steps. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines, has no bundle files, and has no need for external references; its sections (Loop Selection Flow, Combined Pattern, Failure Modes, Recovery) are well-organized and easy to navigate, satisfying the rubric's simple-skill exception. | 5 / 5 |
Total | 15 / 20 Passed |