ghost-ui-skills

Ghost's UI design system. Use when building interfaces inspired by Ghost's aesthetic - dark 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/ghost/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 distinctive design system references. Its main weakness is the lack of specific concrete actions—it tells you what the system is but not what it does (e.g., generate components, apply styles, create layouts). Adding more trigger terms and action verbs would strengthen it.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates UI components, applies styling tokens, and creates layouts following Ghost's design system.'

Expand trigger terms to include variations users might say, such as 'Ghost theme', 'Ghost CMS UI', 'dashboard styling', or 'dark mode 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', 'style layouts', or 'generate theme files'.	2 / 3
Completeness	Clearly answers both 'what' (Ghost's UI design system) and 'when' (Use when building interfaces inspired by Ghost's aesthetic) with explicit trigger guidance including specific design attributes.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'Ghost', 'dark mode', 'Inter font', '4px grid', and 'UI design system', but misses common variations users might say such as 'Ghost theme', 'Ghost CMS styling', 'dashboard design', or 'component library'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific reference to Ghost's aesthetic combined with concrete design tokens (dark mode, Inter font, 4px grid), making it unlikely to conflict with generic UI or other design system 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 constraint hierarchies (MUST/SHOULD/NEVER) and well-organized token tables. Its main weaknesses are the lack of executable code examples (CSS/Tailwind snippets) that would make it immediately actionable, and the monolithic structure that could benefit from splitting detailed reference tables into separate files. Some raw audit artifacts (detected counts, lightness values) add noise without adding value.

Suggestions

Add executable code examples - e.g., a CSS custom properties block defining the semantic tokens, or a Tailwind config snippet implementing the design scale, to make the skill copy-paste ready.

Move detailed reference tables (full text styles, layout patterns) into separate files and link to them from the main skill, keeping only the most essential tokens and rules inline.

Remove raw audit artifacts like 'detected lightness: 8', 'Count' columns, and '(used 42x)' annotations that read as analysis output rather than actionable design guidance.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with well-structured tables and clear rules, but includes some redundancy (e.g., listing both the spacing scale and a default gap, repeating border-radius values in both rules and a separate reference section). Some detected metrics (like 'Count' columns and 'detected lightness: 8') feel like raw audit output rather than curated guidance.	2 / 3
Actionability	Provides concrete design tokens, specific values, and clear MUST/SHOULD/NEVER rules which are actionable for UI implementation. However, there are no executable code examples (e.g., CSS snippets, Tailwind config, or component code) that would make this copy-paste ready for building actual interfaces.	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 with unambiguous rules, and the MUST/SHOULD/NEVER hierarchy makes the priority of each constraint clear.	3 / 3
Progressive Disclosure	The content is well-sectioned with clear headings and tables, but it's a fairly long monolithic document (~150 lines of dense reference material). Some sections like the full text styles table and layout patterns could be split into separate reference files, with the SKILL.md providing a concise overview and links.	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.