CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ios-liquid-glass

API reference: Liquid Glass (iOS 26+). Query for glass effects, navigation patterns, GlassEffect modifiers, design principles.

Quality

75%

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

Quality

Content

71%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 tight, highly actionable API reference with real, executable Swift examples and good decision guidance (variants, containers, accessibility). The notable defect is that its single progressive-disclosure pointer, reference.md, is a dead link — the file was never shipped with the bundle — and the morphing example leans on an undefined ActionButton helper.

Suggestions

Ship the missing reference.md (documentation links, WWDC session IDs, quick-reference tables) or remove the Reference section's dead link.

Define or inline the ActionButton view used in the morphing example so the centerpiece code sample is copy-paste runnable.

Trim or explicitly justify the SF Symbols Effects and Haptics sections, which fall outside the description's stated scope, or add them to the description.

DimensionReasoningScore

Conciseness

The body is almost entirely dense API tables and runnable code, with no explanations of concepts Claude already knows, matching the "efficient with minor instances that could be trimmed" anchor. Not 5: there is mild commentary padding ("Apple describes Liquid Glass with three principles (reference, not a mandate)", "One functional constraint worth knowing", "// Simple glass application") and the SF Symbols and Haptics sections sit outside the description's stated scope; not 3: none of it rises to "several unnecessary explanations" — nearly every line carries API information.

4 / 5

Actionability

Nearly all examples are complete, copy-paste Swift ("Text(\"Action\").padding().glassEffect()", "GlassEffectContainer(spacing: 30) {...}", "matchedTransitionSource(id:in:)" with ".navigationTransition(.zoom(...))") and the variant/shape tables map use cases to concrete calls. Not 5: the central morphing example depends on an undefined "ActionButton(icon:)" helper in four places, so it is not fully copy-paste ready; not 3: the code is real, executable API rather than pseudocode, with only that one gap.

4 / 5

Workflow Clarity

As a reference skill there is no risky multi-step process to sequence — the flow (When to Use → principles → core API → containers → navigation → accessibility → deeper reference) is a coherent, unambiguous lookup path, and guidance like "Glass cannot sample other glass. Use containers for multiple glass elements" gives clear decision rules. Not 5: no explicit workflow or checkpoints exist beyond section ordering, and the skill exceeds the under-50-line simple-skill exception; not 3: nothing is gap-ridden or incoherent, and there are no destructive or batch operations that would demand validation steps.

4 / 5

Progressive Disclosure

The body itself is well-sectioned, but the sole external reference — "see [reference.md](reference.md)" for "official Apple documentation links, WWDC session IDs, and API quick reference tables" — points to a file that does not exist anywhere in the bundle (no references/ directory), so the promised deeper layer is absent. Not 4: a clearly signaled but dead reference is more than a minor organization gap, since navigation to the detailed material fails entirely; not 2: the inline content is properly structured with headers and tables and references are not buried — the failure is one missing file, not an inlined 300-line wall.

3 / 5

Total

15

/

20

Passed

Description

70%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 concise, domain-specific description that clearly states what the skill covers, with strong distinctiveness and good trigger terms. Its main weakness is the missing explicit "Use when..." clause, which caps completeness, and slightly incomplete coverage of the skill's actual capabilities.

Suggestions

Add an explicit trigger clause, e.g. "Use when implementing iOS 26 glass materials, GlassEffectContainer layouts, or liquid-glass navigation surfaces in SwiftUI."

Mention capabilities the body actually covers but the description omits: containers/morphing transitions, accessibility adaptations, and Icon Composer.

Add natural synonyms users might say, such as "SwiftUI", "translucent/frosted materials", or "glass tab bar", to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Query for glass effects, navigation patterns, GlassEffect modifiers, design principles" lists several concrete capability areas within a clearly named domain ("API reference: Liquid Glass (iOS 26+)"), matching the anchor for several specific actions with minor gaps in coverage. Not 5: coverage omits capabilities the skill actually contains (containers, morphing transitions, haptics, accessibility, Icon Composer); not 3: it goes beyond 1-2 actions and the areas are concrete, not generic.

4 / 5

Completeness

The "what" is clear ("API reference: Liquid Glass (iOS 26+)" for glass effects, navigation, modifiers, principles), but there is no "Use when..." clause or equivalent explicit trigger guidance — "Query for..." only weakly implies when to invoke it, so the rubric cap of 3 applies. Not 4: an explicit or specific "when" statement is entirely absent, not merely imprecise.

3 / 5

Trigger Term Quality

Natural trigger phrases are present — "glass effects", "Liquid Glass", "iOS 26+", "GlassEffect", "navigation patterns" — matching the good-coverage-with-a-few-missing anchor. Not 5: misses synonyms and related phrasing users would plausibly say ("SwiftUI", "translucent", "frosted", "tab bar", "icon composer"); not 3: coverage is well beyond the "some relevant keywords" level since both the material name and the API symbol names appear.

4 / 5

Distinctiveness Conflict Risk

"Liquid Glass (iOS 26+)" names a narrow, well-defined niche with distinct trigger terms ("GlassEffect modifiers", "glass effects"), giving minimal overlap risk with other skills. Not 4: even closely related design/UI skills would not claim these iOS-26-specific glass API triggers; the one broad phrase ("design principles") is anchored by the domain qualifier.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

Prisma-Labs-Dev/apple-skills

Path

skills/ios-liquid-glass/SKILL.md

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.