codeium-ui-skills

Codeium's UI design system. Use when building interfaces inspired by Codeium's aesthetic - dark 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/codeium/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 branding reference to Codeium. Its main weakness is the lack of specific concrete actions—it describes the design system's attributes but not what the skill actually does (e.g., generate components, apply styles). Adding more natural trigger terms would also improve discoverability.

Suggestions

Add concrete actions the skill performs, e.g., 'Creates UI components, applies color tokens, and generates styled layouts following Codeium's design system.'

Include additional trigger terms users might naturally use, such as 'theme', 'UI components', 'design tokens', 'styling', or 'Codeium-style interface'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific elements (dark 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 ('Codeium's UI design system') and when ('Use when building interfaces inspired by Codeium's aesthetic - dark mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Codeium', 'dark mode', 'Inter font', and '4px grid' as relevant terms, but misses common variations users might say like 'UI components', 'design tokens', 'theme', 'styling', or 'Codeium-style'.	2 / 3
Distinctiveness Conflict Risk	The specific mention of 'Codeium' as a brand, combined with concrete design attributes (dark mode, Inter font, 4px grid), creates a clear niche that is 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, opinionated constraints using MUST/SHOULD/NEVER language and well-organized tables for tokens and typography. Its main weaknesses are the lack of executable code examples (CSS/Tailwind/component snippets) and the monolithic structure that could benefit from splitting detailed reference tables into separate files. Some minor redundancy exists between sections.

Suggestions

Add at least one executable code example showing how to apply the design tokens (e.g., a Tailwind config snippet, CSS custom properties block, or a sample component using the specified colors/typography)

Move the detailed Text Styles table and Semantic Tokens table into a separate REFERENCE.md file, keeping only the most essential tokens inline

Remove the redundant 'Typography Reference' subsection since font families and sizes are already captured in the Text Styles 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., the Typography Reference section repeats information already in the Text Styles table, and some detected layout patterns add marginal value). The 'Count' column in the text styles table is unnecessary.	2 / 3
Actionability	The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete and actionable for implementation, but lacks executable code examples. No CSS/Tailwind snippets or component code are provided - just specification tables. A UI design skill would benefit from at least one concrete code example showing how to apply these tokens.	2 / 3
Workflow Clarity	This is a reference/specification skill rather than a multi-step workflow, so the single-task clarity standard applies. The content is well-organized with clear sections, unambiguous constraints using MUST/SHOULD/NEVER language, and logical grouping of related concerns (colors, typography, spacing, etc.).	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and tables, but it's a fairly long monolithic document (~150 lines of specification). Some sections like the detailed text styles table or layout patterns could be split into reference files, with the main skill providing a concise overview and links to detailed specs.	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.