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.

Quality

58%

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 ./agent-skills/web-design/dark-glass-clean-layout/SKILL.md

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 body is a clear, well-structured design-direction spec with good organization and an effective Avoid section, but it lacks concrete numeric values for execution and carries a hollow Workflow heading. Tightening repeated aesthetic restatements would improve token efficiency.

Suggestions

Provide concrete values for the tuning knobs, e.g. backdrop-blur radius ranges, fill opacity percentages, and a hex/zinc palette, so guidance is directly executable.

Fill or remove the empty "## Workflow" section — either add a short apply-and-review sequence (draft layout -> apply glass treatment -> check calm/spacing) or delete the heading.

Consolidate overlapping guidance between "Visual target", "Implementation guidance", and "Recommended patterns" to remove restated aesthetic points.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and mostly efficient, but Visual target, Implementation guidance, and Recommended patterns restate similar aesthetic ideas, and phrases like "give the glass layout technical credibility" add little; it could be tightened.	2 / 3
Actionability	Direction is specific (one-pixel gradient wrappers, low-opacity dark fills, strong backdrop blur) but gives no concrete values (blur radius, opacity percentages, hex palette), so guidance is incomplete for direct execution.	2 / 3
Workflow Clarity	This is a single design-direction application rather than a multi-step process, but the empty "## Workflow" heading signals a missing sequence and there is no checkpoint guidance for applying the direction iteratively.	2 / 3
Progressive Disclosure	No bundle files exist and the body is organized into clearly labeled sections (Scope, Visual target, Implementation guidance, Recommended patterns, Tuning knobs, Avoid), satisfying the simple-skill allowance for well-organized content.	3 / 3
	Total	9 / 12 Passed

Description

60%

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 about what the skill produces but omits any explicit "when to use" trigger guidance and leans on niche design jargon rather than natural user keywords. It is distinguishable as a direction but would benefit from explicit trigger phrasing.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when building a dark glassmorphism workspace, dark UI dashboard, or premium intelligence-console layout."

Replace jargon ("frosted premium shells", "restrained atmospheric depth") with terms users actually say, like "frosted glass panels" and "dark glassmorphism".

State concrete capabilities as actions ("Build", "Style", "Lay out") rather than a single "Create" verb with adjective-heavy descriptors.

Dimension	Reasoning	Score
Specificity	"Create a dark glass layout system with frosted premium shells, clean multi-column workspace structure, floating data cards, and restrained atmospheric depth" lists multiple specific concrete system elements (shells, columns, cards, depth), matching the multiple-concrete-actions anchor.	3 / 3
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Terms like "dark glass layout" are plausible but "frosted premium shells" and "restrained atmospheric depth" are niche design jargon rather than natural user phrasing, and common variations (e.g. glassmorphism, dark UI theme) are missing.	2 / 3
Distinctiveness Conflict Risk	The dark-glass aesthetic is a clear niche, but with no distinct trigger language it could still overlap with other general layout or design-system skills.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: MengTo/Skills
Path: agent-skills/web-design/dark-glass-clean-layout/SKILL.md
Commit: 46abf78

Reviewed: about 6 hours 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.