mailchimp-ui-skills

Mailchimp's UI design system. Use when building interfaces inspired by Mailchimp'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/mailchimp/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 concise and clearly scoped to Mailchimp's design system with a good 'Use when' clause and distinctive brand-specific triggers. 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 typography, creating layouts). Adding more natural trigger terms and specific capabilities would strengthen it.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Applies Mailchimp's UI design system to build components, style layouts, and configure typography.'

Expand trigger terms to include variations users might say, such as 'Mailchimp style', 'Mailchimp theme', 'Mailchimp branding', 'design tokens', 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 styles', or 'build layouts'.	2 / 3
Completeness	Clearly answers both what ('Mailchimp's UI design system') and when ('Use when building interfaces inspired by Mailchimp's aesthetic') with explicit trigger guidance including specific parameters.	3 / 3
Trigger Term Quality	Includes 'Mailchimp' and some design terms like 'Inter font', '4px grid', 'light mode', but misses common user terms like 'design system', 'UI components', 'Mailchimp style', 'brand', 'theme', or 'color palette'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific brand reference (Mailchimp) and concrete design parameters (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 reasonably well-structured design system reference with clear constraint language (MUST/SHOULD/NEVER) and specific token values. Its main weaknesses are the lack of concrete implementation code examples, some internal contradictions (light-mode claim vs. black background), and verbose reference sections that could be externalized. The skill would benefit from executable code snippets showing how to apply these tokens in practice.

Suggestions

Add concrete code examples (e.g., Tailwind config, CSS custom properties, or React component snippets) showing how to implement the design tokens

Resolve the contradiction between 'light-mode interfaces' / 'light backgrounds' and surface-base being #000000 — clarify the intended design intent

Move detailed reference tables (full font size list, border radius scale) to a separate REFERENCE.md file and link to it from the main skill

Specify exact hover state colors instead of relative descriptions like 'lighten background by 10%'

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., the Typography Reference section listing all font sizes adds bulk, and the full RGB values alongside HEX are arguably unnecessary for Claude). The detected layout patterns and some reference sections could be trimmed.	2 / 3
Actionability	The skill provides specific values (colors, sizes, radii) and clear constraint rules (MUST/SHOULD/NEVER), which is good for a design system skill. However, it lacks concrete code examples showing how to implement these tokens in CSS/Tailwind/React, and some guidance is vague (e.g., 'lighten background by 10%' without specifying the resulting color).	2 / 3
Workflow Clarity	For a design reference skill, there's no multi-step workflow needed, but the 'When to Apply' section is minimal and the organization of sections is clear. However, there's no guidance on how to validate that an implementation conforms to these constraints, and some contradictions exist (e.g., 'light-mode interfaces' and 'light backgrounds' but surface-base is #000000 black).	2 / 3
Progressive Disclosure	The content is well-sectioned with clear headings and tables, making it scannable. However, the detailed reference tables (all font sizes, all border radii) could be split into separate reference files to keep the main skill leaner, and there are no cross-references to external files for deeper detail.	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.