copy-ai-ui-skills

Copy Ai's UI design system. Use when building interfaces inspired by Copy Ai'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/copy-ai/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 a specific brand's design system, with an explicit 'Use when' clause that aids skill selection. Its main weakness is limited specificity about what concrete actions the skill performs beyond 'building interfaces' - it could benefit from listing specific capabilities like component creation, color palette application, or layout patterns.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Applies Copy Ai's color palette, builds components with Inter typography, implements spacing on a 4px grid system'

Include additional trigger terms users might naturally say, such as 'CopyAI theme', 'design tokens', 'UI components', or 'styling'

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific elements like 'light mode, Inter font, 4px grid', but doesn't list concrete actions beyond 'building interfaces'. It lacks detail on what specific components or patterns the skill provides.	2 / 3
Completeness	Clearly answers both 'what' (Copy Ai's UI design system) and 'when' ('Use when building interfaces inspired by Copy Ai's aesthetic - light mode, Inter font, 4px grid') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'UI design system', 'light mode', 'Inter font', '4px grid', and 'Copy Ai', but misses common variations users might say such as 'design tokens', 'component library', 'styling', 'theme', or 'CopyAI'.	2 / 3
Distinctiveness Conflict Risk	Very specific to Copy Ai's design system with distinct identifiers (Inter font, 4px grid, light mode). Unlikely to conflict with other UI/design skills unless there are multiple Copy Ai-related 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 well-structured design system reference with clear constraint language (MUST/SHOULD/NEVER) and specific token values. Its main weaknesses are the lack of executable code examples (no CSS/Tailwind/component snippets) and the monolithic structure that could benefit from splitting detailed reference tables into separate files. Some data appears auto-generated (e.g., 'Count: 1' columns, detected layout patterns) without enough curation for Claude's consumption.

Suggestions

Add at least 2-3 executable code examples (e.g., a Tailwind button component, a page layout skeleton, or CSS custom properties setup) to make the design tokens immediately actionable.

Move the detailed text styles table and font size reference into a separate REFERENCE.md file, keeping only the most important styles (heading-1, body) inline.

Remove low-value auto-generated data like the 'Count' column (always 1), and curate the 'Detected Layout Patterns' section to explain when to use each pattern rather than just listing dimensions.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints. However, there's some redundancy (e.g., 'Detected Layout Patterns' listing multiple main content sizes without context, the full text styles table with 10 rows of similar entries, and the 'Count' column always showing '1' adds no value). The repeated font size listings and spacing scales could be tighter.	2 / 3
Actionability	The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete, and the MUST/SHOULD/NEVER format is clear. However, there are no executable code examples - no CSS snippets, no Tailwind classes, no component code. For a UI design system skill, having at least one concrete implementation example (e.g., a button component or a page layout) would significantly improve actionability.	2 / 3
Workflow Clarity	This is a reference/constraint skill rather than a multi-step workflow skill. The single-purpose nature (apply these design tokens when building Copy Ai-style UIs) is unambiguous. The 'When to Apply' section clearly scopes usage, and the MUST/SHOULD/NEVER hierarchy provides clear decision-making guidance without needing sequential steps.	3 / 3
Progressive Disclosure	The content is well-organized with clear section headers and tables, but it's a fairly long monolithic document (~150 lines of detailed specifications). Some sections like the full text styles table with 10 entries, or the comprehensive font sizes list, could be split into a reference file. No external file references are provided for deeper dives.	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.