Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive design system reference with well-structured sections and concrete token values, but suffers from apparent auto-generated content that hasn't been curated (duplicate body-secondary entries, suspicious 0px input height, raw layout dimensions). It would benefit from executable implementation examples and pruning of redundant or erroneous data to increase both actionability and conciseness.
Suggestions
Add executable code examples showing implementation (e.g., CSS custom properties block, Tailwind config snippet, or a sample component using these tokens)
Curate auto-extracted values: remove duplicate body-secondary entries with near-identical colors, fix the '0px' input height which appears erroneous, and consolidate the font size list to recommended sizes vs. detected sizes
Add a quick-start checklist or verification section (e.g., 'Before shipping, verify: contrast ratios meet 4.5:1, all spacing aligns to 4px grid, no arbitrary border-radius values')
Split detailed reference tables (full font size list, detected layout patterns, text styles inventory) into a separate REFERENCE.md file, keeping only the primary/recommended values in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with its MUST/SHOULD/NEVER constraint format, but includes excessive detail that adds little value - like listing all 17 font sizes, multiple near-identical body-secondary entries with slightly different colors, and redundant 'Detected Layout Patterns' with specific pixel dimensions that seem auto-generated rather than curated. | 2 / 3 |
Actionability | Provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER), but lacks executable code examples showing how to implement these in practice (e.g., Tailwind config, CSS custom properties setup, or component snippets). Some values seem erroneous or auto-extracted without curation (e.g., input height of '0px', inconsistent body-secondary entries). | 2 / 3 |
Workflow Clarity | The skill is primarily a reference/constraint document rather than a multi-step workflow, so strict workflow scoring is less applicable. However, there's no guidance on the order of applying these constraints, no validation steps for checking compliance, and the 'When to Apply' section is minimal. For a design system skill, a checklist or verification approach would improve clarity. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections with good headers and tables, but it's a long monolithic document that could benefit from splitting detailed reference tables (all font sizes, layout patterns) into separate files. No external references are provided for deeper topics like accessibility testing or component implementation patterns. | 2 / 3 |
Total | 8 / 12 Passed |