Content
68%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, well-sectioned design brief with unusually concrete styling direction for an instruction-only skill, and the "Avoid" and "Tuning knobs" sections add genuine calibration value. Its key defects are the entirely empty "Workflow" section and the verbatim duplication of the description under "Use When", which undermine both workflow clarity and organization.
Suggestions
Either delete the empty "## Workflow" section or populate it with an actual sequence (e.g. 1. choose paper tones, 2. establish orange signal usage, 3. build form panel, 4. build illustration panel, 5. check contrast against the Avoid list).
Replace the verbatim-repeated "Use When" bullet with genuinely additional trigger guidance (SaaS onboarding, landing pages, product mockups) instead of duplicating the frontmatter description.
Add a small set of concrete token-level anchors — a handful of hex values for the paper surfaces and orange, and a radius/shadow scale — so the guidance can be executed without further specification.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is composed of terse, directive bullets ("Use orange as the primary signal and action color for steps, buttons, active states...") with no explanation of concepts Claude already knows. It is not a 5 because the "Use When" section duplicates the frontmatter description verbatim and the empty "Workflow" header wastes tokens. | 4 / 5 |
Actionability | As an instruction-only design skill, the guidance is genuinely concrete: named surface tones ("warm off-white, cream, parchment, and pale stone"), specific application targets ("step markers, primary CTAs, highlight icons, link text, micro-badges"), and recommended layouts ("Split onboarding card with a form panel on one side..."). It is not a 5 because nothing is specified at an executable level — no actual color values, type scale, radius/shadow tokens, or a worked example that could be applied directly. | 4 / 5 |
Workflow Clarity | The "## Workflow" section (line 11) is completely empty, so no sequence of steps is ever articulated — the body reads as a style brief, not a process. It is not a 2 because the surrounding sections (Visual target → Implementation guidance → Recommended patterns) provide a rough implicit progression, and not a 4+ because an explicitly labeled workflow exists but contains nothing. | 3 / 5 |
Progressive Disclosure | At under 50 lines with no bundle files, the skill needs no external references, and it is organized into clearly labeled, scannable sections (Scope, Visual target, Implementation guidance, Recommended patterns, Tuning knobs, Avoid). It is not a 5 because of two organization defects: the empty "Workflow" header and the "Use When" section that restates the description verbatim. | 4 / 5 |
Total | 15 / 20 Passed |