loom-ui-skills

Loom's UI design system. Use when building interfaces inspired by Loom'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/loom/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 Loom's design system with an explicit 'Use when' clause, making it easy for Claude to know when to select it. However, it lacks concrete action verbs describing what the skill actually does (e.g., generate components, apply tokens, build layouts) and could include more natural trigger terms users might say.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies spacing and color tokens, builds responsive layouts following Loom's design system.'

Expand trigger terms to include variations users might say, such as 'design system', 'UI components', 'Loom-style', 'styling', or 'theme'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific elements (light mode, Inter font, 4px grid), but doesn't list concrete actions like 'create components', 'apply spacing tokens', or 'generate layouts'.	2 / 3
Completeness	Answers both 'what' (Loom's UI design system) and 'when' (Use when building interfaces inspired by Loom's aesthetic) with an explicit 'Use when...' clause and specific trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Loom' and some design-specific terms like 'Inter font', '4px grid', 'light mode', but misses common user terms like 'design system', 'UI components', 'styling', 'theme', or 'Loom-style'.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche — specifically Loom's design aesthetic with named attributes (Inter font, 4px grid, light mode). Unlikely to conflict with other design system skills unless another Loom-specific skill exists.	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 constraints using MUST/SHOULD/NEVER language and well-organized tables of design tokens. Its main weaknesses are the lack of executable code examples showing how to implement these constraints (e.g., CSS/Tailwind snippets or component examples), some auto-generated feeling content that could be curated more tightly, and the monolithic structure that could benefit from splitting detailed references into separate files.

Suggestions

Add at least 2-3 executable code examples (e.g., a Tailwind/CSS card component, a button variant, a heading) showing how to apply the design tokens in practice.

Remove auto-generated artifacts like 'currently 14 colors detected', 'used 15x', and 'Count' columns that don't add actionable value for Claude.

Consider splitting the detailed token tables (Text Styles, Semantic Tokens) into a separate TOKENS.md reference file, keeping only the most essential values inline.

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., border-radius scale listed twice, typography reference repeating info from the table) and some detected values that feel auto-generated rather than curated (e.g., 'currently 14 colors detected', 'used 15x', element widths '137px, 144px, 6px').	2 / 3
Actionability	The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete and actionable for implementation. However, it lacks 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 card layout) would make it fully actionable.	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 and rules when building UI) is unambiguous. The MUST/SHOULD/NEVER hierarchy provides clear priority ordering, and the 'When to Apply' section clearly scopes usage.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but it's quite long (~150 lines of dense reference material) and could benefit from splitting detailed token tables and typography references into separate files. There are no references to external files for deeper content, and some sections (like the full text styles table with 10 entries) could be externalized.	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.