beehiiv-ui-skills

Beehiiv's UI design system. Use when building interfaces inspired by Beehiiv'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/beehiiv/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 distinctive brand-specific niche. Its main weakness is the lack of concrete actions—it describes what the system is but not what it does (e.g., generating components, applying styles, building layouts). Adding specific capabilities would strengthen it significantly.

Suggestions

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

Include additional trigger terms users might naturally say, such as 'Beehiiv-style', 'newsletter platform UI', 'design tokens', or 'component library'.

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 styles', or 'build layouts'.	2 / 3
Completeness	Clearly answers both what ('Beehiiv's UI design system') and when ('Use when building interfaces inspired by Beehiiv's aesthetic - light mode, Inter font, 4px grid') with an explicit 'Use when' clause and trigger conditions.	3 / 3
Trigger Term Quality	Includes 'Beehiiv' as a strong trigger term and some design-related terms (light mode, Inter font, 4px grid), but misses common user phrases like 'design system', 'UI components', 'styling', 'theme', or 'Beehiiv-style'.	2 / 3
Distinctiveness Conflict Risk	The specific mention of 'Beehiiv' as a brand name creates a very distinct niche that is unlikely to conflict with other design system skills. The combination of Beehiiv + specific design tokens (Inter font, 4px grid) makes it highly distinguishable.	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 reasonably well-structured design system reference with clear constraint language (MUST/SHOULD/NEVER) and specific design token values. Its main weaknesses are the lack of executable code examples showing how to implement these constraints in practice, and some redundant reference data that could be trimmed or moved to a separate file. The content would benefit significantly from concrete implementation snippets (CSS/Tailwind/component code).

Suggestions

Add executable code examples for key patterns - e.g., a styled button component in React/Tailwind, a heading with correct Inter font styling, or a CSS custom properties block defining the semantic tokens.

Move the detailed Typography Reference (full font size list, all text style variants) to a separate REFERENCE.md file and link to it, keeping only the most common styles inline.

Remove or consolidate redundant information - the duplicate text-23px entries in the Text Styles table and the overlap between the Semantic Tokens table and the Colors section header.

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., the full font size list, duplicate text-23px entries, detected layout patterns that add little actionable value). The 'Typography Reference' section repeats information already conveyed in the Text Styles table.	2 / 3
Actionability	Provides specific values (hex codes, pixel sizes, border radii) and clear constraint language (MUST/SHOULD/NEVER), which is good. However, it lacks executable code examples - no CSS snippets, no Tailwind classes, no component code. For a UI design system skill, concrete implementation examples (e.g., a button component, a heading styled correctly) would significantly improve actionability.	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 for applying constraints.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but it's a fairly long monolithic document. Some sections like the full Typography Reference with 21 font sizes, or the detailed Text Styles table with 10 entries, could be split into a separate reference file. The 'When to Apply' section provides good scoping, but no external references are used.	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.