robinhood-ui-skills
Robinhood's UI design system. Use when building interfaces inspired by Robinhood'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/robinhood/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 distinct brand-specific triggers that make it easily distinguishable from other skills. However, it lacks specificity about what concrete actions the skill performs (e.g., creating components, styling elements, generating layouts) and could benefit from additional trigger terms that users might naturally use when seeking this type of design guidance.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates components, styles layouts, and applies color schemes following Robinhood's UI design system.'
Expand trigger terms to include related phrases users might say, such as 'fintech UI', 'trading app design', 'stock app interface', or 'Robinhood-style components'.
| 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 buttons', or 'build layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Robinhood's UI design system') and when ('Use when building interfaces inspired by Robinhood's aesthetic - dark mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'Robinhood', 'dark mode', 'Inter font', and 'UI design system', but misses common variations users might say such as 'stock app design', 'fintech UI', 'trading app style', or 'green accent theme'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets Robinhood's design aesthetic with unique identifiers (Inter font, 4px grid, dark mode combination). 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 solid design system reference with clear constraints using MUST/SHOULD/NEVER language and well-organized tables for tokens and typography. Its main weaknesses are the lack of executable code examples (no CSS, Tailwind, or component snippets) and some raw data that could be better curated or moved to reference files. Adding implementation examples and trimming redundant/raw-dump content would significantly improve its utility.
Suggestions
Add at least 2-3 executable code examples showing how to implement key components (e.g., a button in Tailwind/CSS, a page layout skeleton, a card component) to improve actionability.
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.
Remove redundant information like the border-radius scale being listed both inline and in a separate subsection, and deduplicate the 'body-secondary' text style entries.
Add a brief workflow section describing the recommended order for building a new Robinhood-style interface and how to validate compliance with the design system constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints. However, there's some redundancy (e.g., border-radius scale listed twice, duplicate 'body-secondary' entries, 'Font Families: Inter (used 13x)' adds little value). Some detected layout patterns feel like raw data dumps rather than actionable guidance. | 2 / 3 |
Actionability | Provides concrete design tokens, specific values, and clear constraints (MUST/SHOULD/NEVER). However, it lacks executable code examples - no CSS snippets, no Tailwind classes, no component code. For a UI design system skill, having at least one concrete implementation example (e.g., a button component or a page layout) would make it significantly more actionable. | 2 / 3 |
Workflow Clarity | The skill is primarily a reference/constraint document rather than a multi-step workflow, which is appropriate for a design system. The 'When to Apply' section provides clear triggers. However, there's no guidance on the order of operations when building a new interface (e.g., start with layout, then typography, then colors) and no validation steps for checking compliance with the design system. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and tables, making it scannable. However, at ~150+ lines, some sections (like the full text styles table with 10 rows) could be split into a reference file. There are no cross-references to external files for deeper details, and the detected layout patterns section feels like it belongs in a separate reference document. | 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.