matter-ui-skills
Matter's UI design system. Use when building interfaces inspired by Matter's aesthetic - dark mode, Inter font, 4px grid.
70
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/matter/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively identifies a clear niche (Matter's design system) and provides explicit trigger guidance with a 'Use when' clause. Its main weakness is the lack of specific concrete actions—it describes the aesthetic but not what the skill actually does (e.g., generate components, apply styles, create layouts). Adding action verbs would strengthen it significantly.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates UI components, applies styling, and creates layouts following Matter's design system.'
Include additional trigger terms users might naturally say, such as 'theme', 'components', 'design tokens', 'styling', or 'Matter theme'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('UI design system') and mentions some specific design elements (dark mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'apply styles', or 'generate layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Matter's UI design system') and when ('Use when building interfaces inspired by Matter's aesthetic - dark mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'dark mode', 'Inter font', '4px grid', and 'UI design system', but misses common user phrases like 'styling', 'theme', 'components', 'design tokens', or 'Matter-style'. The term 'Matter' is specific but niche. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly tied to a specific design system ('Matter') with distinct aesthetic markers (dark mode, Inter font, 4px grid), making it unlikely to conflict with generic UI or other design system skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%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 organized tables for tokens. However, it reads more like a raw design audit output than a curated skill — it includes noisy detected values (counts, detected lightness, multiple near-identical layout patterns) and lacks implementation examples showing how to apply these tokens in code. The content would benefit from trimming raw data, adding concrete code snippets, and splitting detailed references into separate files.
Suggestions
Add concrete code examples (CSS custom properties, Tailwind config, or React component snippets) showing how to implement the design tokens — e.g., a CSS variables block or a Tailwind theme extension.
Remove raw audit artifacts like 'detected lightness: 0', 'Count: 1', 'currently 19 colors detected', and duplicate layout patterns that add noise without actionable value.
Split detailed token tables (full typography reference, all font sizes) into a separate TOKENS.md or REFERENCE.md file, keeping only the most important tokens in the main skill.
Add a quick-start section showing a minimal component example that demonstrates the key design decisions (dark background, Inter font, 4px grid, accent color) in one cohesive snippet.
| 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., listing all 17 font sizes when only key ones matter, repeating border-radius scale in both a rule and a separate reference section, and some detected layout patterns that are noisy rather than prescriptive). | 2 / 3 |
Actionability | Provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER), which is actionable for a design system skill. However, it lacks any code examples showing how to implement these tokens in CSS/Tailwind/React, and some values feel like raw data dumps (e.g., 'detected lightness: 0', 'Count: 1') rather than actionable guidance. | 2 / 3 |
Workflow Clarity | For a design system reference skill, there's no multi-step workflow needed, but the 'When to Apply' section is vague and there's no clear process for how to use these tokens when building a component. The content reads more like a specification dump than a guided workflow for building UI. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and tables, but it's a long monolithic file (~150 lines of detailed specs) that could benefit from splitting detailed token tables and typography references into separate files, with the main SKILL.md providing a concise overview and links. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ihlamury/design-skills
- Commit
126714e
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.