CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-liquid-glass

SwiftUI Liquid Glass: implement, adopt, refactor, review correctness/perf/design.

60

Quality

70%

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

Quality

Content

78%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.

A well-structured, actionable body: executable snippets, concrete checklists, and a clean three-path workflow supported by a properly signaled reference file. The main weaknesses are mild redundancy across the guideline/checklist sections and a missing code example for the morphing-transition guidance.

DimensionReasoningScore

Conciseness

The body is mostly lean — checklist bullets and copy-paste snippets with no explanation of concepts Claude already knows — but guidance like modifier order, interactive(), and GlassEffectContainer repeats across "Core Guidelines", "Review Checklist", and the workflow tree, so some tokens could be trimmed. Not 5 because of that redundancy; not 3 because there is no padded or unnecessary prose.

4 / 5

Actionability

Three complete, executable Swift snippets (availability-gated glassEffect, GlassEffectContainer, .buttonStyle(.glassProminent)) plus concrete checklists with exact API names match 'mostly executable guidance with minor gaps'. Not 5 because morphing transitions via glassEffectID/@Namespace are prescribed in checklists but never shown in code.

4 / 5

Workflow Clarity

The decision tree cleanly sequences three paths, and the Review Checklist serves as validation checkpoints for the review path — 'clear sequence with most checkpoints present'. Not 5 because the implement path ends without a verification step, and not 3 because checkpoints are explicit for two of the three paths.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview (guidelines, checklists, quick snippets) that clearly signals a single one-level-deep reference ("Reference guide: references/liquid-glass.md", verified to exist with no nested references), with detail appropriately deferred to it. Easy to navigate; matches the top anchor.

5 / 5

Total

17

/

20

Passed

Description

62%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.

A terse, distinctive description with a clear sense of what the skill does, but it omits any 'Use when...' trigger guidance and lacks natural trigger variations like "iOS 26" or "glass effect". The compressed verb list also leaves the capabilities slightly generic.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or reviewing SwiftUI views for iOS 26+ that use Liquid Glass, glass buttons, or glassEffect."

Include natural trigger synonyms such as "iOS 26", "glass effect", and ".glassEffect" so the description matches how users actually phrase requests.

Expand the action list with concrete objects, e.g. "apply .glassEffect modifiers, group elements in GlassEffectContainer, add morphing transitions" instead of bare verbs.

DimensionReasoningScore

Specificity

The description names the domain and several actions ("implement, adopt, refactor, review correctness/perf/design"), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the verbs are generic and lack concrete objects (e.g., 'add glassEffect modifiers', 'wrap elements in GlassEffectContainer').

4 / 5

Completeness

It has a clear 'what' (implement/adopt/refactor/review Liquid Glass in SwiftUI) but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete and multi-faceted, not vague.

3 / 5

Trigger Term Quality

"SwiftUI" and "Liquid Glass" are relevant keywords users would say, but common variations like "iOS 26", "glass effect", ".glassEffect", or "Apple design" are absent — matching 'some relevant keywords but missing common variations or synonyms'. Not 4 because the missing variations are among the most natural triggers.

3 / 5

Distinctiveness Conflict Risk

"SwiftUI Liquid Glass" defines a clear niche with distinct triggers and minimal overlap with other skills, matching the top anchor. Adjacent anchors (broad domain, overlap risk) fit clearly worse.

5 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.