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 with clear constraints using MUST/SHOULD/NEVER language and well-organized semantic token tables. Its main weaknesses are verbosity from raw audit data (detected counts, exhaustive font size lists) that could be trimmed or moved to a reference file, and the lack of executable code examples showing implementation patterns (e.g., CSS custom properties, Tailwind config, or component snippets).
Suggestions
Add executable code examples: a CSS custom properties block defining the tokens, a Tailwind config snippet, or a sample component implementing the design system constraints.
Move detailed reference data (full text styles table, font size enumeration, detected layout patterns) to a separate REFERENCE.md file and link to it, keeping SKILL.md as a concise overview.
Remove meta-observations like 'currently 30 colors detected' and 'currently 4 detected' — these read as audit notes rather than actionable design constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful design tokens and constraints, but includes excessive raw data dumps (e.g., 10 text styles with counts of 1, full font size lists, detected layout patterns with pixel dimensions) that add bulk without proportional value. The 'SHOULD reduce color palette (currently 30 colors detected)' and similar meta-observations about the design system feel like audit notes rather than actionable instructions. | 2 / 3 |
Actionability | The skill provides concrete values (hex codes, pixel sizes, specific CSS properties) and clear MUST/SHOULD/NEVER constraints, which is good. However, it lacks executable code examples showing how to implement these patterns (e.g., a Tailwind config snippet, a CSS custom properties block, or a component example). The guidance is specific but not copy-paste ready for implementation. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the single-task exemption applies. The content is well-organized with clear sections, and the MUST/SHOULD/NEVER hierarchy provides unambiguous priority ordering for design decisions. The 'When to Apply' section clearly scopes when to use these guidelines. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear section headers and tables, but it's a long monolithic file. The detailed text styles table, full font size lists, and layout pattern dimensions could be split into a reference file, keeping SKILL.md as a concise overview with links to detailed specs. | 2 / 3 |
Total | 9 / 12 Passed |