CtrlK
BlogDocsLog inGet started
Tessl Logo

dark-glass-clean-layout

Create a dark glass layout system with frosted premium shells, clean multi-column workspace structure, floating data cards, and restrained atmospheric depth.

57

Quality

65%

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-glass-clean-layout/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%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 well-structured and concise with strong section organization, but the empty Workflow section and purely directional (non-executable) guidance weaken workflow clarity and actionability.

Suggestions

Fill the empty '## Workflow' section with a short sequenced process, e.g. define palette -> build shell/frame -> add columns and cards -> tune atmosphere, or remove the heading if none is needed.

Add a few executable specifics such as example backdrop-filter values, opacity ranges, or a CSS snippet for the glass shell so guidance is copy-paste ready.

Include a light verification checkpoint (e.g. confirm shells still read as glass and center stage stays calm) to lift workflow clarity.

DimensionReasoningScore

Conciseness

Generally efficient list-based guidance that avoids explaining concepts Claude already knows, with only minor padded phrasing that could be trimmed.

4 / 5

Actionability

Gives concrete design direction (specific layout patterns, palette, glass treatments) but stops at descriptive guidance rather than executable specifics like actual CSS properties or numeric values.

3 / 5

Workflow Clarity

The '## Workflow' section is present but empty, so no sequenced steps or checkpoints exist; the rough process is only implied through the other sections.

2 / 5

Progressive Disclosure

A compact (~50 line), single-purpose skill with no external references and clean, well-organized section headers, which per the rubric allows a top score for progressive disclosure.

5 / 5

Total

14

/

20

Passed

Description

71%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 distinct, naming concrete visual deliverables in a tight third-person voice. Its main weakness is the absence of an explicit 'when to use' trigger clause.

Suggestions

Append a 'Use when...' clause naming concrete user triggers, e.g. 'Use when the user wants a premium dark workspace, intelligence console, or dark glassmorphism dashboard.'

Add a couple of common synonyms ('glassmorphism', 'dashboard', 'console UI') to broaden natural keyword coverage.

Clarify the distinguishing trigger so it is less likely to compete with generic glassmorphism skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete deliverables ('frosted premium shells', 'clean multi-column workspace structure', 'floating data cards', 'restrained atmospheric depth') with comprehensive coverage of the visual system.

5 / 5

Completeness

Provides a clear 'what' but lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains natural design-brief keywords like 'dark glass layout', 'frosted premium shells', 'multi-column workspace', and 'floating data cards', but misses common synonyms such as 'glassmorphism', 'dashboard', or 'UI'.

4 / 5

Distinctiveness Conflict Risk

Carves a fairly distinct niche (monochrome dark frosted console) that is mostly separable from generic glassmorphism, with only minor overlap risk against other layout/design skills.

4 / 5

Total

16

/

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.