Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid design system reference skill with clear constraints using MUST/SHOULD/NEVER language and well-organized tables of design tokens. Its main weaknesses are the lack of executable code examples showing how to apply these tokens in practice (e.g., CSS variables, Tailwind config, or component snippets) and some redundancy in the reference data. The content would benefit from being split into a concise overview with links to detailed reference files.
Suggestions
Add a quick-start code example showing how to set up the design tokens (e.g., CSS custom properties block or Tailwind config snippet) to improve actionability.
Remove redundant entries: border-radius scale is listed twice, multiple near-identical text-16px rows could be consolidated, and 'detected lightness: 7' / 'currently 16 colors detected' are meta-observations that don't help Claude build UIs.
Consider splitting detailed reference tables (full typography styles, spacing scales, border radius scales) into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the most critical tokens and rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints. However, there's some redundancy (e.g., border-radius scale listed twice, multiple near-identical text-16px entries, 'Detected Layout Patterns' with duplicative entries) and some tokens that don't add value (like 'Count' column showing all 1s, 'detected lightness: 7'). | 2 / 3 |
Actionability | The skill provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER), which is actionable for a design system skill. However, it lacks executable code examples showing how to apply these tokens in practice (e.g., a Tailwind config snippet, CSS custom properties setup, or a component example), which would make it more immediately usable. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the single-task clarity standard applies. The content is well-organized with clear sections, unambiguous rules using MUST/SHOULD/NEVER language, and specific values for each design decision. No destructive or batch operations are involved. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a fairly long monolithic document (~150 lines of design tokens and rules). Some sections like the full typography reference table and detailed spacing/border scales could be split into separate reference files, with the SKILL.md providing a concise overview and linking out. | 2 / 3 |
Total | 9 / 12 Passed |