Content
78%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 well-structured, opinionated framework skill: lean sectioned overview, concrete thresholds and checklists, a gated 6-step workflow, and correctly offloaded detail in two real one-level-deep reference files. It sits just below the top anchors on actionability and workflow clarity where guidance is judgment-level and validation checkpoints are implied rather than explicit.
Suggestions
Trim generalities Claude already knows (e.g., 'Type is the second-most-recognizable element of a brand after the logo', 'Imagery direction is often underspecified') to tighten conciseness.
Make workflow validation checkpoints explicit and testable — e.g., concrete pass/fail criteria for the stress-test step ('every mark legible at 16px', 'every text color pairing passes 4.5:1') instead of 'Where does it break? Iterate'.
Add one worked example of applying the framework (e.g., a filled-in mini color-system entry or a do/don't pairing) to raise actionability from judgment-level to executable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and prescriptive — specific numbers ("Legible at 16 pixels", "5 to 8 carefully chosen colors", "100ms / 200-300ms / 500ms+") rather than padded explanation. A few lines restate general design knowledge Claude already has ("Type is the second-most-recognizable element of a brand after the logo", "Imagery direction is often underspecified"), keeping it below the lean-and-efficient 5 anchor. | 4 / 5 |
Actionability | For an instruction-only skill the guidance is concrete: per-element component checklists, hard thresholds (4.5:1 contrast, 24x24 icon grid, 8 percent color-blind prevalence), a 6-step workflow, and an explicit output file tree (`identity/logo/`, `identity/colors.md`, ...). Not 5 because several directives are judgment-level rather than executable ("Squint at it", "they must work together") and there are no worked good/bad examples inline — minor gaps remain. | 4 / 5 |
Workflow Clarity | The workflow is a clearly sequenced 6-step process with an entry gate ("Confirm brand direction... If unclear, return to `brand-ideation`"), an explicit feedback loop ("Stress-test... Where does it break? Iterate"), and a final checkpoint ("Get sign-off before broad rollout"). Not 5 because validation checkpoints are stated as principles rather than explicit pass/fail criteria per step, and the destructive/batch cap does not apply since no destructive operations are involved. | 4 / 5 |
Progressive Disclosure | The body is a well-sectioned overview (~195 lines) with two clearly signaled one-level-deep references (both verified to exist: `references/identity-system-spec.md`, `references/contrast-and-accessibility.md`) that appropriately pull the spec template and contrast math out of the main file. References are listed in a dedicated section with descriptions, and the spec templates contain no nested references — matching the clear-overview-with-well-signaled-references anchor. | 5 / 5 |
Total | 17 / 20 Passed |