ashby-ui-skills
Ashby's UI design system. Use when building interfaces inspired by Ashby'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/ashby/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 reasonably effective with a clear 'Use when' clause and distinctive branding reference to Ashby. Its main weakness is the lack of specific concrete actions—it tells Claude about the aesthetic but not what it can actually do (e.g., build components, style pages, create layouts). Adding more trigger terms and action verbs would strengthen it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates buttons, forms, cards, navigation components, and page layouts following Ashby's design system.'
Expand trigger terms to include variations users might say, such as 'UI components', 'design tokens', 'theme', 'styling', or 'Ashby-like interface'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific elements (dark mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'style forms', or 'build layouts'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Ashby's UI design system) and 'when' (Use when building interfaces inspired by Ashby's aesthetic) with explicit trigger guidance including specific design attributes. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'dark mode', 'Inter font', '4px grid', and 'Ashby', but misses common variations users might say such as 'design system', 'UI components', 'styling', 'theme', or 'Ashby-style'. | 2 / 3 |
Distinctiveness Conflict Risk | The reference to 'Ashby' as a specific product/brand combined with concrete design tokens (Inter font, 4px grid, dark mode) creates a clear niche that is 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 specific, opinionated constraints using clear MUST/SHOULD/NEVER language. Its main weaknesses are the lack of executable code examples (CSS custom properties, Tailwind config, or component snippets), some redundancy in the typography section, and questionable values (0px input height, surface-raised being white #FEFEFE in a dark theme). The content would benefit from concrete implementation examples and better progressive disclosure.
Suggestions
Add executable code examples: a CSS custom properties block defining the semantic tokens, a Tailwind config snippet, or a sample component implementation to make the design system immediately actionable.
Review and fix suspicious values: 0px input height and #FEFEFE (near-white) for 'surface-raised' in a dark theme seem incorrect and could lead to broken implementations.
Split detailed reference tables (typography styles, full color tokens) into a separate REFERENCE.md file, keeping SKILL.md as a lean overview with the most critical constraints and links to details.
Add a validation/verification section: e.g., how to check contrast ratios meet 4.5:1, how to verify 4px grid alignment, or a checklist for reviewing implementations against these constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with clear MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., 'Border Radius Reference' section repeating '10px' already stated above, duplicate 'text-19px' entries, and the typography reference section largely restating what's in the table). The detailed tables are useful but some could be trimmed. | 2 / 3 |
Actionability | The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete and actionable for design implementation. However, it lacks any executable code examples - no CSS snippets, no Tailwind config, no component code. For a UI design system skill, at least one concrete implementation example (e.g., a styled component or CSS custom properties block) would significantly improve actionability. | 2 / 3 |
Workflow Clarity | The skill is organized as a reference document rather than a workflow, which is appropriate for a design system. However, there's no guidance on the order of applying these constraints, no validation steps (e.g., how to check contrast ratios), and the 'When to Apply' section is vague. For a design system that includes destructive constraints (MUST/NEVER), some verification guidance would be valuable. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a monolithic file with no references to external files for detailed content. The typography section alone is quite long with multiple tables. Splitting detailed token references, component specs, and animation rules into separate files with links from a leaner overview would improve navigation. | 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.