dribbble-ui-skills

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

Quality

62%

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/dribbble/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 effectively communicates when to use the skill with a clear 'Use when' clause and is distinctly scoped to Dribbble's design system. However, it lacks specificity about what concrete actions the skill performs (e.g., generating components, applying color palettes, creating layouts) and could include more natural trigger terms users might use.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies color palettes, and creates layouts following Dribbble's design system.'

Include additional natural trigger terms users might say, such as 'design system', 'styling', 'theme', 'components', or 'Dribbble-style'.

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 styles', or 'build layouts'.	2 / 3
Completeness	Clearly answers both what ('Dribbble's UI design system') and when ('Use when building interfaces inspired by Dribbble's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Dribbble', 'UI design system', 'light mode', 'Inter font', and '4px grid' which are somewhat relevant, but misses natural user terms like 'design', 'styling', 'components', 'theme', or 'look and feel'.	2 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Dribbble's specific design system with distinct identifiers (Dribbble, Inter font, 4px grid), making it 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 skill provides a comprehensive design token reference with clear constraint language (MUST/SHOULD/NEVER) and specific values, which is valuable. However, it reads more like raw design audit output than a curated skill — it lacks executable code examples showing implementation, contains some redundant reference data, and could benefit from splitting detailed token tables into separate files while keeping the SKILL.md as a concise overview.

Suggestions

Add executable code examples: a CSS custom properties block defining the semantic tokens, a Tailwind config snippet, or a sample React component demonstrating the design system in practice.

Split detailed reference tables (full text styles, border radius scale, typography reference) into a separate REFERENCE.md file and link to it from the main skill.

Remove raw audit artifacts like 'Count' columns, '(used 80x)' annotations, and the granular font size list (3px-42px) that appear to be unprocessed design tool output rather than actionable guidance.

Add a quick-start section showing a minimal component (e.g., a card or button) that demonstrates the key tokens working together, giving Claude a concrete implementation pattern to follow.

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., 'Typography Reference' section repeating font sizes already shown in the table, detected layout patterns adding little value, spacing scale of 1-8px listed individually). The raw audit data like 'Count' columns and '(used 80x)' feel like unprocessed design tool output rather than curated guidance.	2 / 3
Actionability	Provides specific values (hex codes, pixel sizes, font weights) which are concrete, but lacks executable code examples showing how to implement these tokens in CSS/Tailwind/React. The constraints are clear (MUST/SHOULD/NEVER) but implementation is left to inference — e.g., no CSS custom property definitions, no Tailwind config snippet, no component code examples.	2 / 3
Workflow Clarity	For a design system reference skill, there's no multi-step workflow needed per se, but the 'When to Apply' section is minimal and there's no guidance on how to compose these tokens together or prioritize conflicting constraints. The content reads as a flat reference rather than a guided process for building interfaces.	2 / 3
Progressive Disclosure	The content is well-sectioned with clear headers and tables, making it scannable. However, at ~150+ lines it's quite long for a single SKILL.md with no references to external files. The detailed token tables, text style references, and border radius scales could be split into separate reference files to keep the main skill lean.	2 / 3
	Total	8 / 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.