launchdarkly-ui-skills

Launchdarkly's UI design system. Use when building interfaces inspired by Launchdarkly's aesthetic - dark 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/launchdarkly/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 reasonably well-structured with a clear 'Use when' clause and brand-specific triggers that make it distinctive. However, it lacks specificity about what concrete actions the skill performs (e.g., generating components, applying styles, creating layouts) and could benefit from additional natural trigger terms users might use when requesting this skill.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates UI components, applies color tokens, and styles layouts following Launchdarkly's design system.'

Include additional natural trigger terms users might say, such as 'design tokens', 'component styling', 'theme', or 'Launchdarkly-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', 'style buttons', or 'build layouts'.	2 / 3
Completeness	Clearly answers both what ('Launchdarkly's UI design system') and when ('Use when building interfaces inspired by Launchdarkly's aesthetic - dark mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger details.	3 / 3
Trigger Term Quality	Includes 'Launchdarkly', 'UI design system', 'dark mode', 'Inter font', and '4px grid' which are somewhat relevant, but misses natural user terms like 'design tokens', 'component library', 'theme', 'styling', or 'Launchdarkly-style'.	2 / 3
Distinctiveness Conflict Risk	The specific brand name 'Launchdarkly' 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

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 constraints using MUST/SHOULD/NEVER language and good use of tables for token definitions. Its main weaknesses are the lack of executable implementation examples (no CSS/Tailwind/component code), some redundant information in the typography section, and the monolithic structure that could benefit from splitting detailed references into separate files.

Suggestions

Add at least one concrete implementation example—e.g., a CSS custom properties block defining the semantic tokens, or a Tailwind config snippet, or a sample component using the design system.

Remove the redundant 'Typography Reference' section that repeats font family and size information already captured in the Text Styles table.

Split detailed token tables and text style references into a separate TOKENS.md or REFERENCE.md file, keeping SKILL.md as a concise overview with links.

Add a brief validation step or checklist (e.g., 'verify contrast ratios meet 4.5:1 using browser dev tools') to make the accessibility requirements actionable.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good use of tables and MUST/SHOULD/NEVER constraints, but includes some redundant information (e.g., listing all 17 font sizes, duplicate text style entries, detected layout patterns with pixel-level specifics that add noise). The 'Typography Reference' section repeats information already in the table above it.	2 / 3
Actionability	Provides concrete design tokens, specific values, and clear constraint rules (MUST/SHOULD/NEVER), which is good for a design system skill. However, it lacks any executable code examples—no Tailwind config snippets, no CSS variable declarations, no component code—making it harder to directly implement. For a UI design system skill, at least one concrete implementation example would significantly improve actionability.	2 / 3
Workflow Clarity	The skill is primarily a reference/constraint document rather than a multi-step workflow, so explicit sequencing is less critical. However, the 'When to Apply' section is vague, and there's no guidance on the order of implementation or how to validate that the design system is correctly applied. For a design system, a brief workflow like 'set up tokens → apply typography → verify contrast ratios' would help.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers and tables, making it scannable. However, the file is quite long (~150 lines of dense reference material) and could benefit from splitting detailed token tables and typography references into separate files, keeping SKILL.md as a concise overview with links to detailed specs.	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.