Content
82%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 concise, well-structured, and gives mostly executable bash guidance with a clear sequenced workflow. The main gaps are parameterized (non-copy-paste) commands, absent validation checkpoints, and a referenced setup script that is not bundled.
Suggestions
Add an explicit validation checkpoint after 'git checkout' and after reading results.tsv (e.g., if the branch or file is missing, fall back to setup_experiment.py) to support error recovery and raise workflow clarity.
Replace parameterized placeholders with concrete examples or note how {skill_path}, {domain}, and {name} are resolved, so commands are closer to copy-paste ready.
Either bundle the referenced scripts/setup_experiment.py or rephrase the Step 1 command so the body does not point to a non-existent bundle file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-organized into Usage and a 4-step 'What It Does' with tight bash/example blocks; it assumes Claude's competence and avoids explaining what experiments or git are, matching the score-5 'lean and efficient' anchor. | 5 / 5 |
Actionability | Quotes concrete executable commands ('python {skill_path}/scripts/setup_experiment.py --list', 'git checkout autoresearch/{domain}/{name}', 'cat .autoresearch/{domain}/{name}/results.tsv', 'git log --oneline -20'); not 5 because placeholders ({skill_path}, {domain}/{name}) prevent direct copy-paste and the /ar:run and /ar:loop handoffs are described rather than given as commands. | 4 / 5 |
Workflow Clarity | A clear numbered 4-step sequence (list → load context → report state → ask next action) matches the score-4 anchor 'clear sequence with most checkpoints present'; not 5 because there are no explicit validation/error-recovery checkpoints (e.g., what to do if the branch or results.tsv is missing). | 4 / 5 |
Progressive Disclosure | Content is a single well-organized self-contained file with clear sections and only one-level sibling-skill references (/ar:run, /ar:loop); not 5 because the body references {skill_path}/scripts/setup_experiment.py yet no scripts/ bundle directory exists, leaving a dangling reference. | 4 / 5 |
Total | 17 / 20 Passed |