resend-ui-skills
Resend's UI design system. Use when building interfaces inspired by Resend's aesthetic - dark mode, Inter font, 4px grid.
75
68%
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/resend/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 minimize conflict risk. However, it lacks specificity about what concrete actions the skill performs (e.g., generating components, applying styles, creating layouts) and could include more natural trigger terms users might use when requesting Resend-inspired designs.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies color tokens, and styles layouts following Resend's design system.'
Expand trigger terms to include variations like 'Resend-style', 'Resend theme', 'minimal dark UI', or 'clean email interface design'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI design system) and mentions some specific attributes (dark mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'style layouts', or 'apply color tokens'. | 2 / 3 |
Completeness | Clearly answers both what ('Resend's UI design system') and when ('Use when building interfaces inspired by Resend's aesthetic - dark mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes 'Resend' as a key trigger and some design terms like 'dark mode', 'Inter font', '4px grid', but misses common user phrases like 'Resend-style', 'Resend theme', 'design system', 'UI components', or 'styling'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific brand reference 'Resend' and the particular design attributes (dark mode, Inter font, 4px grid), making it very unlikely to conflict with other design system skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 solid design system reference with clear constraints using MUST/SHOULD/NEVER language and well-organized tables of design tokens. Its main weaknesses are the lack of executable code examples (CSS/Tailwind/React snippets) that would make it immediately actionable, and some redundancy in the typography section. The content would benefit from being split into a concise overview with references to detailed token/component files.
Suggestions
Add executable code examples showing how to apply the design tokens - e.g., a Tailwind config snippet, CSS custom properties block, or a sample React component using the specified colors/typography
Remove redundant entries in the text styles table (multiple `text-14px` with nearly identical values) and consolidate the Typography Reference section which repeats information from the table
Consider splitting detailed token tables and component specs into separate referenced files (e.g., TOKENS.md, COMPONENTS.md) and keeping SKILL.md as a concise overview with navigation links
| 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., multiple `text-14px` entries with nearly identical values, duplicate `label` entries) and the typography reference section repeats information already in the table. The 'Count' column adds little value. | 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 executable code examples - no CSS/Tailwind snippets, no component code, no copy-paste ready implementations. For a UI design system skill, concrete code showing how to apply these tokens would significantly improve actionability. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow skill. The single-purpose nature (apply these design constraints when building UI) is unambiguous. The MUST/SHOULD/NEVER hierarchy clearly communicates priority, and the content is well-sequenced from foundational (colors, typography) to behavioral (interaction, animation, performance). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a fairly long monolithic document (~150 lines of design specs). The detailed token tables, text styles, and component specs could be split into referenced files (e.g., TOKENS.md, TYPOGRAPHY.md, COMPONENTS.md) with the SKILL.md serving as a concise overview with links. | 2 / 3 |
Total | 9 / 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.