linear-ui-skills

Linear's UI design system. Use when building interfaces inspired by Linear'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/linear/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 niche (Linear's design system), with an explicit 'Use when' clause and distinctive trigger terms. Its main weakness is the lack of concrete actions—it describes the system's attributes but not what the skill actually does (e.g., generate components, apply styling, create layouts). Adding specific capabilities would strengthen it significantly.

Suggestions

Add concrete actions the skill performs, e.g., 'Generates UI components, applies styling, and builds layouts following Linear's design system.'

Include additional trigger terms users might naturally say, such as 'Linear-style UI', 'Linear theme', 'minimal dark interface', or 'design tokens'.

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 styles', or 'build layouts'.	2 / 3
Completeness	Clearly answers both 'what' (Linear's UI design system) and 'when' (Use when building interfaces inspired by Linear's aesthetic) with explicit trigger conditions including specific design attributes.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'Linear', 'dark mode', 'Inter font', and '4px grid' that users might mention, but misses common variations like 'Linear-style', 'Linear theme', 'design tokens', 'UI components', or 'minimal design'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive - specifically targets Linear's design system with unique identifiers (Inter font, 4px grid, Linear's aesthetic), making it very unlikely to conflict with other UI or design 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 solid design system reference with specific values and clear constraint language (MUST/SHOULD/NEVER), making it useful as a lookup resource. However, it lacks executable code examples showing implementation (CSS, Tailwind classes, or component snippets), reads more like extracted design audit data than curated guidance, and could benefit from better progressive disclosure by splitting detailed reference tables into separate files.

Suggestions

Add executable code examples for key patterns — e.g., a Tailwind config snippet for the color tokens, a CSS custom properties block, or a sample component implementing the button variant

Split detailed reference tables (text styles, semantic tokens) into separate reference files and keep SKILL.md as a concise overview with quick-start examples

Clean up the spacing scale — the listed values (5px, 11px, 13px, 14px, 19px) don't align with the stated 4px grid requirement, which creates contradictory guidance

Add a brief workflow or checklist for building a new component/page using this design system (e.g., 'Apply surface-base background → Set Inter font → Use 4px grid spacing → Check contrast ratios')

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with clear tables and MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., 'Typography Reference' section repeats information already in the Text Styles table, and the spacing scale values don't align with a strict 4px grid which is confusing rather than helpful). Some sections like the detected layout patterns feel like raw extraction data rather than curated guidance.	2 / 3
Actionability	The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete, but lacks executable code examples showing how to implement these patterns (e.g., CSS/Tailwind snippets, component templates). The tables are reference-quality but the skill reads more like a design spec than actionable implementation guidance.	2 / 3
Workflow Clarity	The 'When to Apply' section provides clear triggers, and the MUST/SHOULD/NEVER hierarchy creates implicit priority ordering. However, there's no workflow for actually building a component or page — no sequenced steps like 'start with layout, then apply colors, then typography.' For a design system reference this is acceptable but not exemplary.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers and tables, but it's a monolithic file with no references to external files for deeper content. The text styles table, semantic tokens, and component variants could benefit from being split into separate reference files, with SKILL.md serving as a concise overview.	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.