CtrlK
BlogDocsLog inGet started
Tessl Logo

blue-cloudy-clean-modern

Create a clean modern design system with a luminous blue sky atmosphere, soft drifting cloud light, minimal white framing, and serene premium typography.

49

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/blue-cloudy-clean-modern/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

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 well-structured aesthetic direction brief, but it is guidance rather than instruction: it lacks concrete design tokens or code, leaves the Workflow section empty, and repeats the description in 'Use When'. Filling in specifics and removing redundancy would materially raise the score.

Suggestions

Provide concrete design tokens — specific blue gradient stops, font stacks, spacing/radius values, and example CSS or Tailwind classes — so the guidance is copy-paste actionable.

Either populate the '## Workflow' section with a sequenced build order (background → framing → typography → CTAs → motion) or remove the empty header.

Remove the verbatim repetition of the description in 'Use When' and replace it with distinct trigger guidance to cut redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient bullet prose, but the 'Use When' section repeats the frontmatter description verbatim and 'Visual target', 'Recommended patterns', and 'Implementation guidance' restate similar ideas, adding noticeable padding.

3 / 5

Actionability

It names techniques ('canvas, WebGL, or a smooth layered gradient', 'translucent shells', 'gradient-border pills') but gives no concrete tokens — no color values, font stacks, spacing scales, or CSS — leaving the guidance directional rather than executable.

3 / 5

Workflow Clarity

The '## Workflow' header is present but empty, so no procedural sequence is defined; the remaining sections are thematic rather than sequenced, and the empty header is a clear gap.

3 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Scope, Visual target, Implementation guidance, Recommended patterns, Tuning knobs, Avoid) with no nested references; at ~60 lines it slightly exceeds the simple-skill threshold but stays easy to navigate.

4 / 5

Total

13

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 paints a vivid, on-brand aesthetic but functions more as a mood brief than a trigger: it states what to build yet omits when Claude should reach for this skill and offers few natural user phrases. It is reasonably distinct but would benefit from explicit 'Use when' guidance.

Suggestions

Add a 'Use when ...' clause naming concrete user triggers (e.g. 'Use when the user asks for a calm, airy, sky-blue design system or a luminous premium brand aesthetic').

Replace purely descriptive adjectives with at least one more concrete action verb so the capability reads as something Claude does, not just a mood.

Include natural synonyms users might say ('cloud theme', 'airy UI', 'sky-blue brand') to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('clean modern design system') and a single concrete action ('Create'), but the remaining elements are aesthetic qualities ('luminous blue sky atmosphere, soft drifting cloud light, minimal white framing') rather than distinct executable actions.

3 / 5

Completeness

It clearly states the 'what' (create a design system with specific visual qualities) but contains no 'when' / 'Use when' trigger guidance; per the rubric, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

It contains some relevant design vocabulary ('clean modern design system', 'blue sky', 'premium typography') but lacks the natural trigger phrases a user would actually say and offers no synonyms or common variations.

3 / 5

Distinctiveness Conflict Risk

The 'luminous blue sky atmosphere, soft drifting cloud light' niche is a fairly specific aesthetic direction with only minor overlap risk against other generic design-system skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
Reviewed

Table of Contents

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.