levels

Conversion-focused design that removes friction and guides users toward action through clarity, trust, and speed.

Quality

42%

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/levels/SKILL.md

Quality

Content

85%

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

The content is a well-structured, actionable instruction set with concrete tokens, a clear authoring workflow, and testable quality gates; its only weakness is mild thematic overlap across the rules-oriented sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concepts Claude already knows, but the Rules, Quality Gates, Component Rule Expectations, and Example Constraint Language sections overlap thematically and could be consolidated.	2 / 3
Actionability	It provides concrete, specific guidance: exact token values (#27272A, spacing 4/8/12/16/24/32), a required-state list (default, hover, focus-visible...), a fixed output structure, and must/should constraint language — actionable without code.	3 / 3
Workflow Clarity	The Guideline Authoring Workflow is a clearly sequenced 6-step process ending in a QA checklist, with testable Quality Gates serving as validation checkpoints for the output.	3 / 3
Progressive Disclosure	No bundle files are needed or referenced; the single self-contained body is well-organized into clearly labeled sections with no nested references, appropriate for a skill of this scope.	3 / 3
	Total	11 / 12 Passed

Description

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 reads as a brand tagline rather than a skill description: it states no concrete capabilities, no natural trigger terms, and no explicit usage conditions, making it indistinguishable from other design-related skills.

Suggestions

Lead with what the skill does, e.g. 'Authors implementation-ready design-system guidelines (tokens, components, accessibility rules) for the levels design system.'

Add an explicit trigger clause, e.g. 'Use when creating or revising design-system guidelines, component rules, or design tokens for levels.'

Include natural user keywords such as 'design system', 'design tokens', 'component guidelines', and 'UI rules' so the skill is matched when users ask for them.

Dimension	Reasoning	Score
Specificity	The description ('removes friction', 'guides users toward action through clarity, trust, and speed') describes a design philosophy and outcomes, not concrete actions the skill performs (e.g. authoring guidelines, generating tokens).	1 / 3
Completeness	It weakly implies a domain but never states what the skill does (author design-system guidelines), and there is no 'Use when...' or equivalent trigger guidance for when to invoke it.	1 / 3
Trigger Term Quality	Phrases like 'Conversion-focused design' and 'removes friction' are marketing language a user would not naturally say when needing this skill; no natural keywords such as 'design system' or 'design guidelines' appear.	1 / 3
Distinctiveness Conflict Risk	The tagline is generic enough to apply to many UX, marketing, or conversion-optimization skills, so it would conflict with rather than distinguish from other design skills.	1 / 3
	Total	4 / 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/levels/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.