brex-ui-skills

Brex's UI design system. Use when building interfaces inspired by Brex'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/brex/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 well-structured with a clear 'Use when' clause and strong distinctiveness due to the Brex brand specificity. However, it lacks concrete action verbs describing what the skill actually does (e.g., generating components, applying styles) and could benefit from additional trigger terms users might naturally use when requesting UI design help.

Suggestions

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

Include additional natural trigger terms users might say, such as 'design tokens', 'component library', 'theme', 'styling', or 'Brex-style interface'.

Dimension	Reasoning	Score
Specificity	Names the domain (UI design system) and mentions some specific details (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 ('Brex's UI design system') and when ('Use when building interfaces inspired by Brex's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'Brex', 'UI design system', 'light mode', 'Inter font', '4px grid', but misses common user terms like 'design tokens', 'component library', 'styling', 'theme', or 'brand guidelines'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Brex' as a specific brand makes this highly distinctive and unlikely to conflict with other design system skills. The specific aesthetic details (Inter font, 4px grid) further narrow the niche.	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 specific, concrete values (colors, sizes, spacing) organized into clear sections with tables. However, it lacks executable code examples showing implementation, reads more like a raw design audit export than an actionable skill, and some token values seem inconsistent or suspicious (e.g., 'warning' being white, 'destructive' matching 'text-primary'). The skill would benefit significantly from implementation examples and a clearer workflow for applying these constraints.

Suggestions

Add executable code examples showing implementation - e.g., a CSS custom properties block defining the design tokens, a Tailwind config snippet, or a React component example using the design system.

Add a brief workflow section explaining the order of operations when building a Brex-style UI (e.g., set up tokens first, then layout grid, then typography, then components).

Review semantic token assignments for correctness - 'warning' mapped to #FEFEFD (white) and 'destructive' matching 'text-primary' (#D98C71) seem like errors that could mislead implementation.

Split detailed reference tables (full text styles, layout patterns) into a separate REFERENCE.md file and keep SKILL.md as a concise overview with the most essential tokens and rules.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundancy (e.g., 'Typography Reference' section repeats info already in the Text Styles table, detected layout patterns feel like raw data dumps rather than actionable guidance). Some sections like the color table have questionable semantic naming (e.g., 'warning' mapped to white, 'destructive' same as 'text-primary').	2 / 3
Actionability	Provides specific values (hex codes, pixel sizes, font weights) which are concrete, but lacks executable code examples showing how to implement these in actual CSS/Tailwind/React. The skill describes design tokens and constraints but doesn't show copy-paste ready implementation patterns like CSS custom properties definitions or Tailwind config snippets.	2 / 3
Workflow Clarity	For a design system reference skill, there's no clear workflow for how to apply these guidelines when building a UI. The 'When to Apply' section is minimal. There's no sequencing guidance (e.g., start with layout, then typography, then colors) and no validation steps to verify the implementation matches the design system.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers and tables, but it's a fairly long monolithic document. Some sections like the detailed text styles table and layout patterns could be split into reference files, with the main SKILL.md providing a concise overview and linking 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.