CtrlK
BlogDocsLog inGet started
Tessl Logo

mesh-gradient-dark-blue-clean

Create a futuristic, premium, clean dark-blue mesh-gradient design system across background rendering, hero shell, navigation, floating nodes, framed sections, CTAs, and motion. Use when the interface needs a near-black navy foundation, procedural blue mesh atmosphere, disciplined minimal structure, and infrastructural or planetary depth.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/mesh-gradient-dark-blue-clean/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable with complete, runnable code across every component and a clear build sequence. It is efficient and well-organized, with only minor conciseness trimming and inline-checkpoint gaps keeping it from top marks.

DimensionReasoningScore

Conciseness

Code blocks are dense and earn their place and prose sections are terse with no over-explanation of concepts Claude already knows, but a few adjectival restatements ('futuristic, premium, clean') in 'Use When' and 'Direction' could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready CSS tokens, hero-shell, navigation, node, and CTA rules, plus a complete runnable canvas mesh function with reduced-motion handling covering the common cases.

5 / 5

Workflow Clarity

The 'System Recipe' gives a clear 9-step build sequence and 'Quick Checks' acts as an end checklist, but validation checkpoints are not inline within the sequence and there are no error-recovery feedback loops.

4 / 5

Progressive Disclosure

The skill is self-contained in SKILL.md with well-labeled sections and no nested references; it is appropriately single-file for a design system, though the substantial token/CSS/JS bulk is inlined rather than split into bundle files.

4 / 5

Total

17

/

20

Passed

Description

67%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 is specific and explicitly covers both what and when, with a clear distinct niche. Its main weakness is trigger-term quality: the 'Use when' clause leans on evocative adjectives rather than concrete phrases users would naturally say.

Suggestions

Rewrite the 'Use when' clause with concrete user-language triggers (e.g., 'Use when the user asks for a dark-blue mesh-gradient hero, a near-black navy dashboard, or a premium infrastructural landing page').

Add common synonyms and concrete nouns users say ('dashboard', 'landing page', 'hero section', 'mesh gradient') alongside the adjectival phrasing.

Frame the listed surfaces as distinct actions ('Render a mesh-gradient background, build a hero shell, style navigation and CTAs') to lift specificity toward 5.

DimensionReasoningScore

Specificity

Lists several concrete design surfaces ('background rendering, hero shell, navigation, floating nodes, framed sections, CTAs, and motion') with a concrete action verb ('Create'), but enumerates surfaces rather than distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

Clearly states what the skill does ('Create a ... design system across ...') and when to use it ('Use when the interface needs ...'), but the 'when' trigger language is abstract rather than concrete user-uttered phrases.

4 / 5

Trigger Term Quality

Some relevant keywords appear ('mesh-gradient', 'hero shell', 'navigation', 'CTAs') but the 'Use when' phrasing leans on evocative adjectives ('infrastructural or planetary depth') rather than natural user phrases, and common synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (dark-blue mesh-gradient design system) with distinctive visual language and low overlap risk, though the abstract trigger phrasing could brush against other design-system skills.

4 / 5

Total

15

/

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.