segment-ui-skills

Segment's UI design system. Use when building interfaces inspired by Segment'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/segment/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 references that make it easy to identify when this skill should be selected. However, it lacks specificity about what concrete actions the skill enables (e.g., creating components, applying color palettes, building layouts) and could benefit from additional natural trigger terms users might use when requesting Segment-style interfaces.

Suggestions

Add concrete actions the skill performs, e.g., 'Creates components, applies color palettes, and builds layouts following Segment's UI design system.'

Include additional natural trigger terms users might say, such as 'clean dashboard UI', 'Segment-style components', 'minimal SaaS interface', or 'Twilio Segment design'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific design attributes (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 ('Segment's UI design system') and when ('Use when building interfaces inspired by Segment's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Segment', 'UI design system', 'light mode', 'Inter font', and '4px grid' which are somewhat relevant, but misses natural user terms like 'design tokens', 'component library', 'Segment-style', 'clean UI', or 'dashboard design'.	2 / 3
Distinctiveness Conflict Risk	Very specific to Segment's design system with distinct identifiers (Segment, Inter font, 4px grid, light mode) that are unlikely to conflict with other design system skills unless there are multiple Segment-related 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 skill provides a comprehensive design token reference for Segment-style UIs with good use of constraint language (MUST/SHOULD/NEVER) and structured tables. However, it reads more like raw design audit output than curated guidance — duplicate entries, seemingly auto-detected values (multiple header heights, arbitrary widths), and lack of executable code examples reduce its effectiveness. Adding code snippets, a brief component-building workflow, and splitting reference data into separate files would significantly improve it.

Suggestions

Add executable code examples (CSS custom properties block, Tailwind config snippet, or a sample component) to make the design tokens immediately actionable rather than just reference tables.

Clean up apparent extraction artifacts: remove duplicate text-15px entries, consolidate multiple header heights into a recommended value, and curate the element widths list to meaningful layout breakpoints.

Add a brief workflow section showing how to compose these tokens when building a new component (e.g., 1. Set up tokens → 2. Apply typography scale → 3. Check contrast → 4. Verify grid alignment).

Split the detailed reference tables (full typography list, detected layout patterns) into a separate REFERENCE.md file, keeping SKILL.md focused on the essential constraints and quick-start guidance.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes excessive detail that may not earn its tokens — e.g., listing every detected font size, multiple near-identical header heights, duplicate text-15px entries, and element widths like '8px, 248px, 11px' that seem like raw extraction artifacts rather than curated guidance.	2 / 3
Actionability	Provides concrete values (hex codes, pixel sizes, font weights) and clear constraint language (MUST/SHOULD/NEVER), but lacks executable code examples. For a UI design system skill, CSS/Tailwind snippets or component code would make this significantly more actionable and copy-paste ready.	2 / 3
Workflow Clarity	The 'When to Apply' section provides context, and the content is organized by concern (colors, typography, spacing, etc.), but there's no workflow for actually building a component or page. For a design system skill, a brief workflow showing how to compose these tokens into a component would improve clarity. No validation steps for checking contrast ratios or grid alignment.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers and tables, but it's a monolithic file with no references to external files for detailed component specs, examples, or advanced patterns. The extensive typography and layout detection data could be split into reference files, keeping the main skill leaner.	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.