Content
80%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 concise, well-structured follow-up skill with unusually concrete anti-slop guidance (specific AI tells and harden targets). Its weakness is workflow sequencing: the operating rules are principles rather than an ordered pass, and validation of fixes is implicit rather than an explicit checkpoint.
Suggestions
Turn the Operating Rules into an ordered pass with an explicit validation checkpoint, e.g. '1. Inspect the artifact in a browser; 2. Fix the top issues; 3. Re-open the page and verify overflow, contrast, and states before finishing'.
Add measurable criteria to the harden and accessibility guidance, such as a WCAG contrast threshold (e.g. 4.5:1 body text) and a motion-duration bound, so fixes are verifiable rather than judgment calls.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and efficient: short mode bullets, a tight numbered rule list, and no explanation of concepts Claude already knows. Every section earns its place; the only near-fluff phrase ('closer to something a designer would ship') still conveys the intent of the pass. | 5 / 5 |
Actionability | Concrete, specific guidance throughout: named AI tells ('purple-blue glow gradients with no product reason', 'generic 3-card feature rows', 'oversized rounded cards everywhere') and named harden targets ('mobile overflow, text clipping, contrast problems, missing states, broken links'). Falls short of anchor 5 because it gives no operational criteria or commands — e.g. no contrast threshold, motion duration bounds, or a way to verify fixes — leaving some judgment calls open. | 4 / 5 |
Workflow Clarity | The Operating Rules imply a sequence (inspect first, preserve intent, make decisive fixes, remove AI tells, preserve accessibility, end runnable), but it reads as principles rather than a sequenced pass. Validation checkpoints are implicit — 'final visual QA' appears only under the Live mode, and there is no explicit verify step (e.g. re-check contrast or test the page in a browser) between fixing and finishing. | 3 / 5 |
Progressive Disclosure | The body is under 50 lines, well organized into clear sections (Follow-Up Modes, Operating Rules, Best Pairings), and no bundle files exist or are needed — verified that references/, scripts/, and assets/ are absent and all body pointers are to other skills by name, not to files. Per the simple-skill guideline, well-organized sections alone warrant anchor 5. | 5 / 5 |
Total | 17 / 20 Passed |