warp-ui-skills

Warp's UI design system. Use when building interfaces inspired by Warp's aesthetic - light mode, Inter font, 4px grid.

Quality

68%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/warp/SKILL.md

Quality

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 benefit from additional natural trigger terms users might use.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies consistent styling, and builds layouts following Warp's design system.'

Include additional natural trigger terms users might say, such as 'Warp-style', 'design tokens', 'component styling', 'theme', or 'UI components'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific elements (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'apply styling', or 'generate layouts'.	2 / 3
Completeness	Clearly answers both what ('Warp's UI design system') and when ('Use when building interfaces inspired by Warp's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'Warp', 'UI design system', 'light mode', 'Inter font', '4px grid', but misses common user phrases like 'design tokens', 'component library', 'styling', 'theme', or 'Warp-style'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific brand name 'Warp' and concrete design specifications (Inter font, 4px grid, light mode), 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 skill with clear constraint language (MUST/SHOULD/NEVER) and specific values. Its main weaknesses are the inclusion of auto-generated artifacts that add noise ('currently 16 colors detected', 'Count: 1' columns), the lack of executable code examples showing implementation, and the monolithic structure that could benefit from splitting detailed reference tables into separate files.

Suggestions

Add executable code examples (CSS custom properties block, Tailwind config snippet, or a sample component) to make the design tokens immediately actionable rather than purely declarative.

Remove auto-generated artifacts like 'currently 16 colors detected', 'used 45x', and 'Count: 1' columns that don't add actionable value and suggest unprocessed output.

Split the detailed text styles table and font size reference into a separate TYPOGRAPHY_REFERENCE.md file, keeping only the primary styles (heading-1, body, body-secondary) inline.

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., 'Detected Layout Patterns' with raw pixel dumps, the extensive text styles table with 'Count: 1' entries, and the 'Typography Reference' section repeating font size information). The raw detection artifacts ('currently 16 colors detected', 'currently 5 detected', 'used 45x') suggest auto-generated content that wasn't fully curated.	2 / 3
Actionability	The skill provides specific values (hex codes, pixel sizes, border radii) which are concrete and actionable for implementation, but lacks executable code examples. For a design system skill, CSS/Tailwind snippets or component code would make it copy-paste ready. The MUST/SHOULD/NEVER directives are clear but remain declarative rather than demonstrating implementation.	2 / 3
Workflow Clarity	This is a reference/constraint skill rather than a multi-step workflow, so the single-task clarity standard applies. The content is well-organized into logical sections (Colors, Typography, Spacing, etc.) with clear priority signals (MUST/SHOULD/NEVER), making it unambiguous which rules to apply and when.	3 / 3
Progressive Disclosure	The content is well-sectioned with clear headings and tables, but it's a monolithic file that could benefit from splitting detailed reference tables (all text styles, full font size lists) into separate reference files. The 'When to Apply' section is good, but there are no cross-references to supplementary materials for the extensive token/style tables.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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: 8 days ago

Table of Contents

Discovery Implementation Validation

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.