plaid-ui-skills
Plaid's UI design system. Use when building interfaces inspired by Plaid's aesthetic - dark mode, Inter font, 4px grid.
75
68%
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/plaid/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 is concise and well-structured with a clear 'Use when' clause and distinct brand-specific triggers. Its main weakness is the lack of concrete actions—it describes the design system's characteristics but not what the skill actually does (e.g., generate components, apply styles, create layouts). Adding specific capabilities would strengthen it significantly.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates UI components, applies styling, and creates layouts following Plaid's design system.'
Include additional trigger terms users might naturally say, such as 'theme', 'design tokens', 'component styling', or 'Plaid-style interface'.
| 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 styling', or 'generate layouts'. | 2 / 3 |
Completeness | Clearly answers both what ('Plaid's UI design system') and when ('Use when building interfaces inspired by Plaid's aesthetic - dark mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'Plaid', 'dark mode', 'Inter font', '4px grid', and 'UI design system', but misses common variations users might say such as 'design tokens', 'component library', 'styling', 'theme', or 'Plaid-style'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically tied to Plaid's design system with unique identifiers (Plaid brand, Inter font, 4px grid, dark mode). Unlikely to conflict with other design system skills unless there are multiple Plaid-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 solid design system reference skill with clear constraints using MUST/SHOULD/NEVER language and well-organized tables for design tokens. Its main weaknesses are the lack of executable code examples (CSS, Tailwind, or component snippets) that would make it immediately actionable, and some redundancy in the typography and color sections. The content would benefit from concrete implementation examples and better progressive disclosure for the more detailed reference tables.
Suggestions
Add concrete code examples (e.g., a Tailwind config snippet, CSS custom properties block, or a sample component) to make the design tokens immediately implementable rather than just reference values.
Move the detailed text styles table and border radius reference into a separate REFERENCE.md file, keeping only the primary styles (heading-1, body) inline with a link to the full reference.
Remove redundant information like the RGB column (HEX is sufficient for Claude), the 'Count' column in text styles, and the 'detected lightness: 11' annotation to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables and clear MUST/SHOULD/NEVER constraints, but includes some redundant information (e.g., listing both HEX and RGB for every color, the 'Count' column in text styles adding little value, and the 'detected lightness: 11' annotation). The typography section has overlapping information between the table and the reference subsection. | 2 / 3 |
Actionability | The skill provides specific values (colors, sizes, spacing) and clear constraints (MUST/SHOULD/NEVER), which is actionable for a design system. However, it lacks any concrete code examples—no CSS snippets, no Tailwind classes, no component templates—that would make it truly copy-paste ready for implementation. | 2 / 3 |
Workflow Clarity | This is a reference/constraint skill rather than a multi-step workflow, so the single-task clarity standard applies. The content is well-organized into clear sections (Colors, Typography, Spacing, etc.) with unambiguous rules. The MUST/SHOULD/NEVER hierarchy makes decision-making straightforward. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and subsections, but it's a fairly long monolithic document (~150 lines of detailed tables and rules) with no references to external files for deeper content like component examples or full API references. Some sections (like the full text styles table with 10 rows) could be split out. | 2 / 3 |
Total | 9 / 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.