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.

The content is well-structured, actionable, and efficiently disclosed, with executable snippets and a clear workflow decision tree; its main weaknesses are mild redundancy between the guidelines and checklists and a missing code example for morphing transitions.

Suggestions

Consolidate the overlapping Core Guidelines with the Review/Implementation checklists to remove redundancy and tighten conciseness.

Add a short copy-paste snippet demonstrating glassEffectID + @Namespace morphing transitions, which are currently only mentioned in prose.

Add an explicit verify/build checkpoint to the implement workflow path to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining what Liquid Glass is, but the Core Guidelines section overlaps materially with the Review and Implementation checklists, leaving minor redundancy to trim.

4 / 5

Actionability

Three copy-paste Swift snippets cover common cases (glass effect with fallback, GlassEffectContainer, glass button style), but morphing transitions via glassEffectID are mentioned only in prose without a code example.

4 / 5

Workflow Clarity

A clear decision tree sequences three paths (review/implement/improve) with a Review Checklist serving as a validation checkpoint, but the implement path lacks an explicit build-or-verify step.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview with a clearly signaled, one-level-deep reference (references/liquid-glass.md, verified present), and detailed content is appropriately split into that file.

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.

The description is specific and distinctive, naming a clear niche and several concrete actions, but it omits any explicit "Use when..." trigger guidance and lacks keyword variations, which limits trigger-term quality and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or reviewing SwiftUI features targeting the iOS 26+ Liquid Glass API."

Include natural keyword variations users might say, such as "iOS 26", "glass effect", or "GlassEffectContainer".

Expand the action list slightly to be more comprehensive (e.g. mention morphing transitions or container grouping) to push specificity toward 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ("implement, adopt, refactor, review correctness/perf/design") covering the feature lifecycle, falling short of 5 only because the coverage is terse rather than comprehensive.

4 / 5

Completeness

The "what" is clear (implement/adopt/refactor/review), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"SwiftUI Liquid Glass" are relevant natural keywords a user would say, but common variations like "iOS 26", "glass effect", or "GlassEffectContainer" are missing.

3 / 5

Distinctiveness Conflict Risk

"SwiftUI Liquid Glass" names a highly specific iOS 26 niche with distinct triggers and minimal risk of firing for unrelated skills.

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.

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