CtrlK
BlogDocsLog inGet started
Tessl Logo

dark-blue-contrasting-clean

Create a dark-blue clean design system with strong contrast, cobalt gradient feature blocks, crisp framed structure, and restrained premium glow.

47

Quality

48%

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/dark-blue-contrasting-clean/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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 clean, well-organized design brief with good progressive disclosure, but it is held back by an empty Workflow section, design-prose padding, and the absence of concrete tokens or executable detail. Actionability and workflow clarity are the weakest dimensions.

Suggestions

Fill the empty '## Workflow' section with an explicit apply-order (e.g., set base palette → build framing rails → add cobalt feature blocks → tune glow) or remove the header.

Provide concrete tokens or values — specific navy/cobalt hex codes, border widths, blur radii — so the guidance is directly executable.

Tighten adjective-heavy lines into terse directives to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is well-structured and avoids explaining concepts Claude already knows, but adjective-heavy design prose ('clean, architectural, and high-contrast', 'restrained premium glow') adds padding that could be tightened.

2 / 3

Actionability

Visual guidance is concrete ('border-gradient wrappers', 'border-x rails', 'small corner squares', tuning knobs) but lacks actual tokens, hex values, or CSS so it stays incomplete for direct execution.

2 / 3

Workflow Clarity

The '## Workflow' section is empty and no explicit sequence is given; the surrounding sections are well-organized but a clear step order with checkpoints is absent.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-file, and organized into clearly labeled sections with no need for external references, satisfying the simple-skill allowance for a top score.

3 / 3

Total

9

/

12

Passed

Description

40%

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 conveys the design aesthetic and scope but lacks explicit trigger guidance and is written in imperative rather than third-person voice. It is reasonably specific to its niche but weak on natural trigger terms and completeness.

Suggestions

Rewrite in third person ('Creates a dark-blue clean design system...') to avoid the voice penalty.

Add a 'Use when...' clause naming natural triggers like 'dark-blue UI', 'premium dark theme', 'high-contrast design system', or 'cobalt/blue-led visual style'.

Lead with concrete actions users would say rather than adjective-heavy attributes.

DimensionReasoningScore

Specificity

Only one concrete action ('Create') plus design attributes like 'cobalt gradient feature blocks' and 'crisp framed structure' rather than multiple discrete actions; the imperative 'Create' is second-person voice, triggering the -1 specificity penalty per the judging guidelines.

1 / 3

Completeness

It states what the skill does but provides no 'Use when...' or equivalent trigger guidance, so completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like 'dark-blue', 'clean design', 'strong contrast', and 'premium' are plausible user phrasing, but compound jargon such as 'cobalt gradient feature blocks' and 'restrained premium glow' are not natural trigger words.

2 / 3

Distinctiveness Conflict Risk

The dark-blue premium niche is fairly specific, but with no explicit triggers and overlap with other design-system skills it could still conflict.

2 / 3

Total

7

/

12

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.