weights-biases-ui-skills
Weights Biases's UI design system. Use when building interfaces inspired by Weights Biases's aesthetic - light mode, Inter font, 4px grid.
81
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/weights-biases/SKILL.mdQuality
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 has a clear 'Use when' clause and is distinctive due to the specific brand reference, but it lacks concrete action verbs describing what the skill actually does (e.g., generating components, applying styles). The brand name 'Weights & Biases' is misspelled (missing ampersand), and common abbreviations like 'W&B' or 'wandb' are absent, which could reduce discoverability.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Applies Weights & Biases's UI design system to build components, style layouts, and theme interfaces.'
Include common name variations as trigger terms: 'W&B', 'wandb', 'Weights & Biases' (with ampersand) to improve matching when users use abbreviations.
| 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 styling', or 'generate layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Weights Biases's UI design system') and when ('Use when building interfaces inspired by Weights Biases's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger context. | 3 / 3 |
Trigger Term Quality | Includes 'Weights Biases' (missing the ampersand in 'Weights & Biases' / 'W&B'), 'UI design system', 'light mode', 'Inter font', and '4px grid'. However, it's missing common variations like 'W&B', 'wandb', 'design tokens', or 'component library' that users might naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific brand name 'Weights Biases' and its particular design system attributes (Inter font, 4px grid, light mode). Unlikely to conflict with other design system skills unless there are multiple W&B-related skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured design system constraint file that efficiently communicates rules using MUST/SHOULD/NEVER conventions. Its main weaknesses are incomplete sections (font families list is empty, Components section is empty), lack of executable code examples showing how to implement these constraints, and missed opportunities for progressive disclosure into sub-files for a richer design system reference.
Suggestions
Complete the incomplete sections: the font families constraint is missing its value list, and the Components section is empty
Add at least one concrete code example (e.g., a Tailwind CSS button component) demonstrating how multiple constraints combine in practice
Consider splitting detailed sections (interactive states, animation rules) into referenced sub-files to keep the main SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It uses MUST/SHOULD/NEVER constraints without over-explaining concepts Claude already knows. Every line provides specific, actionable design tokens or rules. | 3 / 3 |
Actionability | The skill provides specific values (hex codes, pixel values, CSS properties) which is good, but lacks executable code examples. For a UI design system skill, concrete component code snippets (e.g., a Tailwind/CSS example of a button with correct states) would significantly improve actionability. The font families section is incomplete ('MUST limit font families to:' with nothing listed). | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the clear categorical organization (Colors, Typography, Spacing, etc.) with unambiguous rules serves as sufficient workflow guidance. The interactive states section clearly sequences focus, hover, and disabled states with specific values. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a semantic token table, but it's all inline in a single file. For a design system skill, separating component examples, color palettes, or animation guidelines into referenced files would improve navigation. The Components section is empty, suggesting incomplete content. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
Table of Contents
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.