expressive

Vibrant, personality-driven design with bold colors, playful graphics, and dynamic layouts that balance creativity with structure.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/expressive/SKILL.md

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, opinionated, actionable guideline-authoring skill with concrete tokens, explicit states, and a clear sequenced workflow plus QA checklist. Its main gap is the absence of any progressive disclosure structure — everything lives inline in one file.

Suggestions

Split detailed reference material (full token tables, component-state matrices) into a referenced file (e.g. TOKENS.md / COMPONENTS.md) and link to it from the overview to enable progressive disclosure.

Keep the inline SKILL.md to a concise overview plus well-signaled one-level-deep references rather than inlining the entire rule set.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense with no padding or explanation of concepts Claude already knows; every section (tokens, rules, workflow, output structure, QA checklist) earns its place, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	It provides concrete, specific guidance — exact typography and spacing scales, color tokens with hex values, explicit required component states, 'must/should' constraint language, and a testable QA checklist — so it is fully actionable instruction-only guidance despite containing no code.	3 / 3
Workflow Clarity	The 'Guideline Authoring Workflow' is a clear six-step numbered sequence paired with a 'Required Output Structure', and because this is authoring guidance rather than a destructive or batch operation, no validation feedback loop is required; this matches the clear-sequence anchor.	3 / 3
Progressive Disclosure	The content is well organized into labeled sections but is a single flat monolithic body with no progressive-disclosure mechanism (no bundle files, no one-level-deep references to split material out), matching the 'some structure but content that should be separate is inline' anchor rather than the well-signaled-references ceiling.	2 / 3
	Total	11 / 12 Passed

Description

50%

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 effectively conveys the design aesthetic and domain but stops short of stating concrete actions, natural trigger terms, or an explicit 'when to use' clause. It reads as a style characterization rather than a usage-focused trigger.

Suggestions

Lead with concrete verbs describing what the skill produces (e.g. 'Generate and apply expressive design-system guidelines, tokens, and component rules').

Add an explicit 'Use when...' trigger clause naming natural user phrasings (e.g. 'Use when creating vibrant, personality-driven UIs, expressive design systems, or bold branded layouts').

Include terms users actually request like 'design system', 'design tokens', or 'expressive UI' to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the design domain and its attributes ('bold colors, playful graphics, and dynamic layouts') but lists no concrete actions (e.g. create, apply, generate); it describes what the style is rather than what the skill does, fitting the 'names domain and some actions but not comprehensive' anchor rather than the vague 'helps with' floor.	2 / 3
Completeness	It answers 'what' (a vibrant, personality-driven design style) but has no 'Use when...' clause or equivalent trigger, which per the judging guidelines caps completeness at 2 even though the what-side is clearly stated.	2 / 3
Trigger Term Quality	Domain keywords like 'design', 'colors', and 'layouts' are present but the phrasing uses descriptive adjectives rather than the natural terms a user would actually say when requesting this skill (e.g. 'design system', 'expressive UI', 'brand styling'), so it matches the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The 'bold colors, playful graphics, dynamic layouts' language is a recognizable aesthetic niche but is generic enough to overlap with other brand/design-system skills, matching 'somewhat specific but could still overlap with similar skills'.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bergside/awesome-design-skills
Path: skills/expressive/SKILL.md
Commit: f631a09

Reviewed: 1 day 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.