intercom-ui-skills
Intercom's UI design system. Use when building interfaces inspired by Intercom'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/intercom/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 select from a pool of skills. Its main weakness is the lack of concrete actions—it describes what the system is but not what specific tasks it enables (e.g., building components, applying color palettes, creating layouts). Adding specific capabilities would strengthen it significantly.
Suggestions
Add concrete actions the skill performs, e.g., 'Applies Intercom-inspired styling to components, builds card layouts, styles buttons and form elements.'
Include additional natural trigger terms users might say, such as 'Intercom-style', 'Intercom theme', 'design tokens', 'component styling', or 'UI components'.
| 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 ('Intercom's UI design system') and when ('Use when building interfaces inspired by Intercom's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes 'Intercom' and 'UI design system' as relevant keywords, plus specific terms like 'Inter font' and '4px grid', but misses common user terms like 'design tokens', 'component library', 'styling', 'theme', or 'Intercom-style'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific brand reference (Intercom) and concrete design details (Inter font, 4px grid, light mode), making it very unlikely to conflict with 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 specific values in well-formatted tables. Its main weaknesses are the lack of executable code examples showing how to implement these constraints (e.g., Tailwind classes, CSS snippets, or component code), some redundancy in reference data, and the monolithic structure that could benefit from splitting detailed reference tables into separate files.
Suggestions
Add executable code examples for key patterns - e.g., a Tailwind/CSS snippet for a button component, a card layout, or a heading style that demonstrates the design tokens in practice.
Split detailed reference tables (full typography list, spacing scale, border-radius scale) into a separate REFERENCE.md file, keeping only the most essential tokens and constraints in the main SKILL.md.
Complete the Components section with more than just one Ghost button variant - the current table is too sparse to be useful for building actual interfaces.
Add a brief 'How to apply' section at the top showing the priority order of constraints and how to verify compliance with the design system.
| 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., border-radius scale listed twice, typography reference repeating font family info, detected layout patterns with minimal value). Some sections like the text styles table with 10 rows of similar entries could be tightened. | 2 / 3 |
Actionability | Provides specific values (hex codes, pixel sizes, font weights) and clear constraints (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. The guidance is concrete in values but incomplete in implementation. | 2 / 3 |
Workflow Clarity | This is primarily a reference/constraint skill 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 of priority, no validation steps for checking compliance, and no process for resolving conflicts between constraints. For a design system skill, a brief 'how to apply' workflow would improve clarity. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and tables, making it scannable. However, at ~150 lines with detailed reference tables (typography, colors, spacing), some of this reference material could be split into separate files. The skill tries to be both a quick reference and a comprehensive specification in one file, which makes it longer than ideal for a SKILL.md overview. | 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.