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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is actionable with ready-to-use Swift snippets and good progressive disclosure to a real reference file, but its checklists overlap and the workflow lacks explicit validation/feedback checkpoints. Tightening the redundant checklists and adding verify-then-retry steps would raise conciseness and workflow clarity.

Suggestions

Merge or de-duplicate the Core Guidelines, Review Checklist, and Implementation Checklist to remove overlapping items and tighten token use.

Add an explicit validation checkpoint to the review/implement paths (e.g. after refactor, re-check modifier order and availability gating) with a fix-and-retry loop.

Make the reference link a clickable path (references/liquid-glass.md) and consider pulling the most common snippet into a named section so navigation is unambiguous.

DimensionReasoningScore

Conciseness

Mostly lean and assumes SwiftUI competence (no basics explained), but Core Guidelines, the Review Checklist, and the Implementation Checklist overlap enough that it could be tightened; not a 3 due to redundancy.

2 / 3

Actionability

Provides copy-paste-ready, executable Swift snippets (e.g. `.glassEffect(.regular.interactive(), in: .rect(cornerRadius: 16))`, `GlassEffectContainer`, `.buttonStyle(.glassProminent)`) with concrete details.

3 / 3

Workflow Clarity

The decision tree sequences three paths and checklists exist, but there are no explicit validation/checkpoint or fix-retry feedback loops (e.g. re-verify after a refactor), leaving checkpoints implicit.

2 / 3

Progressive Disclosure

The body is a concise overview that signals a single one-level-deep reference ("Reference guide: references/liquid-glass.md", verified to exist), with content appropriately split rather than inlined.

3 / 3

Total

10

/

12

Passed

Description

67%

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 about a clear niche, but it omits explicit "when to use" trigger guidance and only partially covers the natural terms a user would actually say. Adding a Use-when clause would lift completeness and trigger quality.

Suggestions

Append a Use-when clause naming the trigger situations, e.g. "Use when building or reviewing SwiftUI views with the iOS 26+ Liquid Glass API (glass effects, glass buttons, glass containers)."

Broaden trigger terms to natural phrasings a user might say: "glass effect", "iOS 26 glass UI", "glass material", "frosted glass SwiftUI".

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "implement, adopt, refactor, review correctness/perf/design" — matching the anchor for enumerating several specific actions.

3 / 3

Completeness

States the "what" (implement/adopt/refactor/review) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Contains the core proper noun "SwiftUI Liquid Glass" but lacks common natural variations users would say (e.g. "glass effect", "iOS 26 glass", "glass UI"), so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

"SwiftUI Liquid Glass" names a specific iOS API niche with distinct triggers, making it unlikely to fire for the wrong skill; not the level below because it is far more specific than "Works with document files".

3 / 3

Total

10

/

12

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.