Content
71%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.
A lean, actionable body with exact search commands, a concrete output template, and a clear five-step sequence. Its one real defect is a broken progressive-disclosure chain: the referenced docs/output-kit.md and /atlas-report are absent from the bundle, so the output-format and delivery instructions cannot be followed as written.
Suggestions
Fix the dangling reference: either include docs/output-kit.md in the bundle (with the 40-line CLI budget, box-drawing skeleton, and severity indicators it promises) or inline that format spec directly and drop the reference.
Document or inline the '/atlas-report' delivery mechanism — as written, the Delivery section depends on a skill that is neither bundled nor explained, leaving the overflow path unusable.
Add a brief failure-handling note to the workflow (e.g., what to do when a surge_agent search returns no results) to close the workflow-clarity validation gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is tight — three exact commands, a terse output template, and four one-line anti-patterns with no explanations of concepts Claude already knows — though the 'When to use' section restates the frontmatter description and the box-drawing template spends tokens on alignment characters. | 4 / 5 |
Actionability | Commands like 'python3 -m surge_agent.uiux search --domain landing --query "{product_type}" --limit 3' are copy-paste ready and the output skeleton is concrete, but there is no worked example of a filled-in output and step 5 ('Output experiment-friendly structure...') gestures at the template rather than demonstrating it. | 4 / 5 |
Workflow Clarity | Five clearly sequenced steps each carry a concrete command, and the workflow is non-destructive so heavy validation is unwarranted; the minor gap is no handling of failure cases such as empty search results, which keeps it below anchor 5. | 4 / 5 |
Progressive Disclosure | Sections are well-organized, but the pivotal reference 'Follow the output format defined in docs/output-kit.md' points to a file that does not exist in the bundle, and the '/atlas-report' dependency is similarly undocumented, leaving the navigation chain broken. | 3 / 5 |
Total | 15 / 20 Passed |