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 a lean, fully executable runbook for delegating a task to Hermes: concrete commands, exact exit-code semantics, and explicit safety guards for one-shot mode's auto-YOLO behavior. Every step has a validation checkpoint or error-recovery path, and the short single-file length needs no progressive disclosure structure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every sentence carries operational specifics ("Exit zero means success, exit one means failure", "automatically enables YOLO and hook acceptance", "inspect the diff afterward") with no padding and no explanations of concepts Claude already knows — a lean, token-efficient runbook. | 5 / 5 |
Actionability | Fully executable guidance: `command -v hermes`, `hermes -z "<prompt>"`, exact exit-code semantics, and a concrete worked example for an approved edit ("touch only named files, run it in that project, require exit zero, and inspect the resulting diff"). | 5 / 5 |
Workflow Clarity | Clear numbered sequence with explicit validation checkpoints at every step — availability check ("If it is missing, stop and ask the user"), exit-zero requirement, and post-run diff inspection — plus explicit error-recovery paths for auth/config failures; the destructive-operation cap does not apply because validation for the YOLO risk is present. | 5 / 5 |
Progressive Disclosure | The body is under 50 lines with no need for external references; it is organized into two clear sections (Run, Authentication And Permissions) and no bundle files exist to disclose, so well-organized sections fully satisfy the rubric. | 5 / 5 |
Total | 20 / 20 Passed |