Content
88%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 strong pointer-style skill body: every line carries Commonly-specific rules and exact values, workflows are sequenced with real verification steps (screenshot proof, test re-pinning, browser preview), and referenced files are clearly signaled one level deep. The main improvements are moving dated identity-decision details into a deprecation/history note and trimming the inline system summary that duplicates the README.
Suggestions
Move time-sensitive details like "(Signal, chosen 2026-09-03)" into an 'old patterns' or history section so current guidance stays evergreen, and drop the stale "SF font" trigger from the description to match the body's note that the SF-first stack is gone.
Trim or restructure the "What the system says" summary so it holds only the values needed for quick decisions, leaving full spec content to the README it already points to — this reduces duplication with the referenced source of truth.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with project-specific facts Claude cannot know (exact hexes, font weights, radii, motion timings) and never explains general concepts, so it mostly earns its tokens. However, time-sensitive details — "(Signal, chosen 2026-09-03)" and the dated identity references — sit outside any 'old patterns'/'deprecated' section, and the "What the system says" section duplicates content the workflow already directs to the README, so it fits 'efficient; minor instances that could be trimmed' rather than the lean anchor at 5. | 4 / 5 |
Actionability | As an instruction-only skill it carries no code, but the guidance is fully concrete: exact values (cobalt `#1d3fd1`, ink `#101828`, radius 4/6, "80ms hover, 120ms card hover, 300ms layout"), exact file paths for every source of truth, an executable rule ("Apply through `var(--v2-*)` — never hardcode hex values"), and a "When in doubt" section prescribing specific behavior for the three common cases (mocks, production v2 code, new component types). This is the copy-paste-equivalent of executable guidance for a design skill. | 5 / 5 |
Workflow Clarity | Multiple clearly sequenced processes with explicit validation checkpoints: the read-first workflow orders files ("Read this FIRST"), shipping requires proof ("the PR carries 1440 and 390 screenshots... load-bearing CSS is re-pinned in `v2-layout-invariants.test.ts`"), and "Preview before merge" plus the drift rule ("If they drift... fix it immediately") provide error-recovery feedback loops. Design work is neither destructive nor batch, so the validation cap does not apply. | 5 / 5 |
Progressive Disclosure | The skill self-describes as a "thin pointer" and delivers: a table maps each referenced file to its purpose, references are one level deep (SKILL.md → repo files), and navigation is easy across nine well-organized sections. The minor gap is the inline "What the system says" summary, which restates spec content that lives in the README/tokens.css — matching 'good structure; most content appropriately placed; minor organization gaps' rather than the fully-split anchor at 5. | 4 / 5 |
Total | 18 / 20 Passed |