deel-ui-skills
Deel's UI design system. Use when building interfaces inspired by Deel's aesthetic - light 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/deel/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 is well-structured with a clear 'Use when' clause and distinctive brand-specific triggers that make it easy to identify when this skill should be selected. Its main weakness is the lack of specific concrete actions - it describes the design system's characteristics but not what actions Claude can perform with it (e.g., creating components, applying styles, generating layouts).
Suggestions
Add specific concrete actions the skill enables, e.g., 'Creates UI components, applies consistent styling, and generates layouts following Deel's design system.'
Include additional trigger terms users might naturally use, such as 'theme', 'design tokens', 'component styling', or 'Deel brand'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific details (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'style buttons', or 'build layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Deel's UI design system') and when ('Use when building interfaces inspired by Deel's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and specific trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'Deel', 'UI design system', 'light mode', 'Inter font', '4px grid', and 'interfaces', but misses common variations users might say like 'design tokens', 'component library', 'styling', 'theme', or 'Deel-style'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically tied to Deel's brand aesthetic with concrete identifiers (Inter font, 4px grid, light mode). Unlikely to conflict with other design system skills unless there are multiple Deel-related 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 constraint language (MUST/SHOULD/NEVER) and useful token tables. Its main weaknesses are the lack of executable implementation examples (CSS/Tailwind/component code), inclusion of raw detection artifacts that don't add actionable value, and the monolithic structure that could benefit from splitting reference data into separate files. The skill would be significantly more actionable with concrete code snippets showing how to apply these tokens.
Suggestions
Add executable code examples (e.g., Tailwind config snippets, CSS custom properties setup, or a sample component implementation) to make the design tokens immediately usable.
Remove raw detection artifacts like 'currently 32 colors detected', 'used 75x', and 'Count' columns—these are metadata about the analysis, not actionable design guidance.
Complete the Buttons component section with all variants (primary, secondary, disabled states) or remove the incomplete table and replace with a concrete implementation example.
Split detailed reference tables (full font size list, border radius scale, text styles) into a separate REFERENCE.md file and link to it, keeping SKILL.md focused on the key constraints and most-used tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundant data (e.g., listing every detected font size, multiple near-identical layout patterns, duplicate text style names) and raw detection artifacts ('currently 32 colors detected', 'used 75x') that add noise without actionable value. | 2 / 3 |
Actionability | Provides concrete design tokens, specific values, and clear constraint rules (MUST/SHOULD/NEVER), which is good for a design system skill. However, it lacks executable code examples—no CSS/Tailwind snippets, no component implementation examples, and the button component table has only one variant with mostly empty fields, making it incomplete for actual implementation. | 2 / 3 |
Workflow Clarity | The skill is primarily a reference/constraint document rather than a multi-step workflow, so explicit sequencing is less critical. However, there's no guidance on how to apply these constraints in order (e.g., start with layout, then typography, then colors), and no validation steps to verify compliance with the design system. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections with good headers and tables, but it's a long monolithic file that could benefit from splitting detailed reference tables (all font sizes, all border radii, text styles) into separate reference files. The 'When to Apply' section is a good overview element, but there are no cross-references to deeper documentation. | 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.