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 reasonably well-structured design system reference with clear constraints using MUST/SHOULD/NEVER language and specific values. Its main weaknesses are the lack of executable code examples (CSS/Tailwind snippets, component templates) that would make it immediately actionable, and some raw data that feels auto-generated rather than curated (duplicate text style entries, verbose element width lists). The content would benefit from trimming redundant data and adding concrete implementation snippets.
Suggestions
Add executable code examples—e.g., a Tailwind config snippet for the color tokens, a CSS custom properties block, or a sample component showing the design system in use.
Consolidate the typography section: merge the Text Styles table and Typography Reference into a single concise reference, removing near-duplicate entries (e.g., multiple text-15px rows with slightly different colors).
Move detailed reference tables (full text styles, detected layout patterns) to a separate REFERENCE.md file and link to it, 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, but includes some redundancy (e.g., the typography section has both a 'Text Styles' table and a separate 'Typography Reference' section listing the same font sizes). The detected layout patterns and element widths feel like raw data dumps rather than curated guidance. Some tables have excessive rows with near-duplicate entries (multiple text-15px variants). | 2 / 3 |
Actionability | The skill provides specific values (hex codes, pixel sizes, timing constraints) which is good, but lacks executable code examples. For a UI design system skill, concrete CSS/Tailwind snippets or component code would significantly improve actionability. The guidance is specific but descriptive rather than directly implementable—e.g., 'lighten background by 10%' without showing how. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the single-purpose nature applies. The content is clearly organized by concern (colors, typography, spacing, etc.) with unambiguous rules using MUST/SHOULD/NEVER modifiers. The 'When to Apply' section clearly scopes when to use the skill. | 3 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers and tables, but it's a fairly long monolithic document. The typography section in particular could benefit from splitting detailed text style tables into a separate reference file. There are no cross-references to external files for deeper detail, and some sections (like the full font size list and text styles table) could be offloaded. | 2 / 3 |
Total | 9 / 12 Passed |