monzo-ui-skills

Monzo's UI design system. Use when building interfaces inspired by Monzo'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/monzo/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 a distinct niche targeting Monzo's design aesthetic. Its main weakness is the lack of specific concrete actions (e.g., creating components, applying styles, building layouts) and limited trigger term coverage for how users might naturally request Monzo-inspired designs.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates buttons, cards, navigation, and layout components following Monzo's design system.'

Expand trigger terms to include natural variations like 'Monzo-style', 'banking app UI', 'Monzo theme', 'Monzo colors', or 'fintech design'.

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 buttons', 'style cards', 'build navigation components'.	2 / 3
Completeness	Clearly answers both what ('Monzo's UI design system') and when ('Use when building interfaces inspired by Monzo's aesthetic - light mode, Inter font, 4px grid'), with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Monzo' and 'UI design system' as natural keywords, plus specific terms like 'Inter font' and '4px grid', but misses common variations users might say like 'Monzo-style', 'banking app UI', 'Monzo colors', 'Monzo components', or 'design tokens'.	2 / 3
Distinctiveness Conflict Risk	Very distinct niche — specifically Monzo's design system with named characteristics (Inter font, 4px grid, light mode). Unlikely to conflict with other design system skills unless there are multiple Monzo-related skills.	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 well-structured design system reference with clear constraint language (MUST/SHOULD/NEVER) and specific values. Its main weaknesses are the lack of executable code examples showing implementation (e.g., CSS custom properties, Tailwind config, or component snippets) and some apparent auto-generated content that could be curated more tightly. The file would benefit from being split into an overview + detailed reference.

Suggestions

Add executable code examples showing how to implement the design tokens (e.g., CSS custom properties block, Tailwind config snippet, or a sample component using the system)

Move detailed reference tables (text styles, layout patterns) to a separate REFERENCE.md and link from the main skill file to improve progressive disclosure

Remove auto-generated artifacts like 'Count' columns with all 1s and 'currently N detected' notes, replacing them with curated recommendations

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., the 'Count' column with all 1s adds no value, the 'Detected Layout Patterns' section lists specific pixel values that seem auto-generated rather than curated, and some information like 'currently 15 colors detected' / 'currently 5 detected' feels like raw audit output rather than actionable guidance).	2 / 3
Actionability	The skill provides specific values (hex codes, pixel sizes, font weights) which are concrete and directly usable, but lacks any executable code examples showing how to implement these design tokens in CSS/Tailwind/React. For a UI design system skill, concrete code snippets showing CSS custom properties or component markup would significantly improve actionability.	2 / 3
Workflow Clarity	This is a reference/constraint skill rather than a multi-step workflow, and for that purpose the clear categorization with MUST/SHOULD/NEVER priority levels and well-organized sections makes the guidance unambiguous. The 'When to Apply' section clearly scopes when to use these guidelines.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but it's quite long as a single monolithic file. The detailed text styles table (10 rows), spacing scales, and border radius references could be split into a separate reference file, keeping SKILL.md as a concise overview with links to detailed specs.	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.