gradient

Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth.

Quality

67%

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/gradient/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 body is a tight, well-organized instruction-only skill that assumes Claude's competence and provides a clear authoring workflow with a QA checkpoint. Its main gap is actionability: it tells Claude how to write guidelines but never shows a concrete worked example of an authored component guideline.

Suggestions

Add one short worked example of an authored component rule (e.g., a Button rule with anatomy, states, and token usage) so the guidance is copy-paste ready.

Show a concrete 'must'/'should' rule paired with its don't-example, as the 'Example Constraint Language' section prescribes but does not demonstrate.

Include a minimal sample QA checklist with checkable items rather than only naming the checklist as a deliverable.

Dimension	Reasoning	Score
Conciseness	The body is lean and bulleted with no padding or explanation of concepts Claude already knows (e.g., what design systems or accessibility are); every section adds task-specific guidance, matching 'lean and efficient; every token earns its place'.	3 / 3
Actionability	Guidance is concrete in places ('required states: default, hover, focus-visible, active, disabled, loading, error', token list, 8pt grid) but it describes how to author guidelines rather than showing a copy-paste example of an authored guideline, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The 6-step 'Guideline Authoring Workflow' is clearly sequenced and ends with an executable QA checklist ('QA checklist that can be executed in code review'), satisfying the checklist requirement of the top anchor for this non-destructive authoring task.	3 / 3
Progressive Disclosure	No bundle files exist and the single-file body is well-organized into clearly labeled sections (Mission, Style Foundations, Accessibility, Workflow, Quality Gates), which per the simple-skills note merits a 3 without external references.	3 / 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 clearly signals the gradient/visual-depth domain but relies on descriptive qualities rather than concrete actions and omits any explicit 'Use when...' trigger guidance. It is distinct enough to avoid total genericness yet not specific enough to reach the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating gradient backgrounds, mesh gradients, or color-transition surfaces for modern UIs.'

Replace descriptive qualities with concrete actions such as 'Generate, apply, and audit smooth color transitions and gradient-rich surfaces.'

Include natural variation terms users say (gradients, background gradients, color blends, shading) to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the gradient domain via 'Smooth color transitions and gradient-rich surfaces' and 'visual depth', but these are qualities rather than concrete actions (no 'generate', 'apply', 'author' verbs), matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill covers (gradient-rich surfaces for modern interfaces) but has no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'gradient', 'color transitions', 'modern, playful interfaces' are terms a user might say, but coverage is limited with no common variations like 'gradients', 'background', 'shading', 'mesh gradient', placing it at 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The gradient niche is somewhat specific, but the phrasing is generic enough to overlap with general design/styling skills, fitting '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/gradient/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.