CtrlK
BlogDocsLog inGet started
Tessl Logo

glassmorphism

Frosted glass effect with translucent layers, subtle blur, and luminous borders for depth and modern elegance.

47

Quality

50%

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 ./skills/glassmorphism/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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, mostly lean guideline-authoring template with clear workflow steps and quality gates. Its main gaps are the absence of a worked output example, validation checkpoints integrated into the workflow, and any progressive disclosure via reference files.

Suggestions

Add one short worked example showing a finished component guideline (anatomy, states, tokens) so the abstract structure becomes copy-paste ready.

Insert explicit validation checkpoints into the numbered workflow (e.g. 'After step 3, verify every state is covered before proceeding') to turn the QA loop into an inline feedback loop.

Move the verbose token/color/typography tables into a referenced TOKENS.md and link to it, keeping SKILL.md as a lean overview — this also improves progressive disclosure.

Tighten or remove the generic 'Brand' sentence, which adds no actionable guidance and conflicts with the mobile-first framing elsewhere.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet points that assume Claude's competence, but the 'Brand' line ('provide fast, reliable communication for individuals, teams...') is generic padding and a few rules duplicate the accessibility section, so it could be tightened.

2 / 3

Actionability

It gives specific structural directives (required states, output structure, 'must'/'should' conventions) but provides no worked example of a finished guideline, so the guidance is concrete yet incomplete and not copy-paste ready.

2 / 3

Workflow Clarity

The 'Guideline Authoring Workflow' is a clear 6-step sequence and a QA checklist exists, but validation checkpoints are not embedded between the numbered steps, leaving the feedback loop implicit rather than integrated.

2 / 3

Progressive Disclosure

The skill is well-organized into clearly labeled sections but is a monolithic single file with no external references; at over 50 lines, token tables and color specifics could be split into reference files to aid navigation.

2 / 3

Total

8

/

12

Passed

Description

50%

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 vividly characterizes the glassmorphism aesthetic but never states the skill's actual capability or when to invoke it. It reads as a style tagline rather than a functional trigger, leaving both action specificity and use-conditions implicit.

Suggestions

Lead with a concrete verb describing what the skill does, e.g. 'Applies a glassmorphism design system... generate frosted-glass UI components and tokens.'

Add an explicit 'Use when...' clause naming natural triggers: 'Use when the user wants glassmorphism, frosted-glass UI, translucent/blur panels, or liquid-glass aesthetics.'

Include common keyword variations ('glassmorphism', 'frosted glass', 'blur background') so the description matches what users actually say.

DimensionReasoningScore

Specificity

Names the domain concretely with specific visual attributes ('translucent layers, subtle blur, and luminous borders'), but states no actions/verbs — it describes an aesthetic rather than what the skill does, so it is not a comprehensive capability list.

2 / 3

Completeness

It conveys what the effect is (the 'what'), but there is no 'Use when...' clause or equivalent trigger guidance, so the 'when' is missing — capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

'Frosted glass effect' is a natural term a user might say, but common variations like 'glassmorphism', 'frosted glass UI', or 'blur background' are missing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The glassmorphism aesthetic is a somewhat specific niche, but as a generic design-system skill it could still overlap with other UI styling skills and lacks distinctive triggers that would prevent misfiring.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bergside/awesome-design-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.