convertkit-ui-skills

Convertkit's UI design system. Use when building interfaces inspired by Convertkit'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/convertkit/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 has a clear 'Use when' clause and is distinctive enough to avoid conflicts with other skills. However, it lacks specific concrete actions (what the skill actually produces or does beyond being a 'design system') and could benefit from more natural trigger terms users might use when requesting UI work.

Suggestions

Add concrete actions the skill performs, e.g., 'Creates buttons, forms, cards, and layouts following Convertkit's design system.'

Include additional natural trigger terms like 'Convertkit theme', 'Convertkit styling', 'Convertkit components', or 'Convertkit brand'.

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 buttons', 'style forms', or 'build layouts'.	2 / 3
Completeness	Clearly answers both what ('Convertkit's UI design system') and when ('Use when building interfaces inspired by Convertkit's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Convertkit', 'UI design system', 'light mode', 'Inter font', and '4px grid' which are somewhat relevant, but misses natural user terms like 'design components', 'styling', 'theme', 'brand', or 'UI kit'.	2 / 3
Distinctiveness Conflict Risk	The description is highly specific to Convertkit's design system with distinct identifiers (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 reasonably well-structured design system reference with clear constraint language (MUST/SHOULD/NEVER) and specific values. Its main weaknesses are the lack of executable code examples showing implementation patterns and some redundancy in the typography and border sections that appear to be raw design extraction artifacts rather than curated guidance. The content would benefit from concrete CSS/Tailwind snippets and trimming of redundant reference data.

Suggestions

Add executable code examples (CSS custom properties, Tailwind config, or component snippets) showing how to implement the design tokens and patterns

Remove redundant information: the border-radius scale is listed twice, and the Typography Reference section largely repeats the Text Styles table

Clean up raw extraction artifacts like 'Count: 1' columns, 'currently 18 colors detected', and arbitrary 'consistent element widths' (44px, 10px, 335px) that don't provide actionable guidance

Complete the Buttons component table with more variants (primary, secondary, disabled states) or remove the incomplete single-row table

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 section repeats information from the text styles table, and some detected values like 'Count: 1' add no value). The 'Detected Layout Patterns' and 'consistent element widths' feel like raw extraction artifacts 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 patterns in actual CSS/Tailwind/component code. The button component table only has one variant (Ghost) and is incomplete. Rules like 'lighten background by 10%' are somewhat vague without specifying the resulting color.	2 / 3
Workflow Clarity	This is a reference/constraint skill rather than a multi-step workflow skill. The single-purpose nature (design system reference) is well-served by its clear categorical organization with unambiguous MUST/SHOULD/NEVER directives. No destructive or batch operations are involved, so validation checkpoints are not needed.	3 / 3
Progressive Disclosure	The content is well-organized into logical sections with clear headers and tables, but it's a fairly long monolithic document. Some sections like the full typography reference or detailed spacing scales could be split into separate reference files. No external file references are provided for deeper dives into specific areas like component patterns or accessibility guidelines.	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.