swiftui-liquid-glass

Implement or review SwiftUI Liquid Glass APIs with correct fallbacks and modifier order.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/swiftui-liquid-glass/SKILL.md

Quality

Content

64%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 solid skill that provides actionable SwiftUI Liquid Glass guidance with good code snippets and a useful review/implementation checklist structure. Its main weaknesses are the lack of validation/verification steps in the workflows and a missing code example for the morphing transitions pattern that is repeatedly referenced. The reference to a bundle file that doesn't exist also weakens the progressive disclosure score.

Suggestions

Add a concrete code example for morphing transitions using `glassEffectID` and `@Namespace`, since this pattern is mentioned in both checklists but never demonstrated.

Include explicit validation steps in the workflow paths, such as 'Build and run on iOS 26 simulator to verify glass rendering' and 'Test on iOS 25 to confirm fallback UI appears correctly'.

Either provide the referenced `references/liquid-glass.md` bundle file or clarify what content it contains so the progressive disclosure is functional.

Dimension	Reasoning	Score
Conciseness	Generally efficient and avoids explaining basic SwiftUI concepts. Minor verbosity in the 'When to Use' section and some of the workflow descriptions that could be tightened, but overall respects Claude's intelligence.	4 / 5
Actionability	Provides concrete, copy-paste ready Swift code snippets covering the main patterns (availability gating, GlassEffectContainer, button styles). Minor gaps: no example for morphing transitions with glassEffectID/@Namespace despite mentioning it in both checklists.	4 / 5
Workflow Clarity	The decision tree provides a reasonable structure for three paths (review, improve, implement), and the checklists are useful. However, there are no explicit validation checkpoints or feedback loops — for instance, no step to verify the glass effect renders correctly or that fallbacks work on older OS versions.	3 / 5
Progressive Disclosure	References `references/liquid-glass.md` for detailed API info, which is good progressive disclosure in principle. However, no bundle files were provided, so the reference may be broken. The skill inlines a moderate amount of content but could better signal what's in the reference file versus what's here.	3 / 5
	Total	14 / 20 Passed

Description

53%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 identifies a clear niche (SwiftUI Liquid Glass APIs) and mentions two actions (implement, review) along with key concerns (fallbacks, modifier order). However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms and synonyms that users would actually say when needing this skill.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about glass effects in SwiftUI, glassEffect modifier, Liquid Glass styling, or iOS 26 visual effects.'

Include additional natural trigger terms and synonyms such as 'glass effect', '.glassEffect', 'translucent UI', 'iOS 26', 'visionOS glass', or 'blur material' to improve discoverability.

Expand the specific capabilities listed, e.g., 'apply .glassEffect modifiers, handle availability checks for older OS versions, ensure correct modifier ordering for glass rendering.'

Dimension	Reasoning	Score
Specificity	Names the domain (SwiftUI Liquid Glass APIs) and two concrete actions (implement, review), plus mentions fallbacks and modifier order, but doesn't elaborate on what specific capabilities are covered (e.g., which modifiers, which glass effects, what kinds of fallbacks).	3 / 5
Completeness	The 'what' is reasonably clear (implement or review SwiftUI Liquid Glass APIs with correct fallbacks and modifier order), but there is no explicit 'when' clause or trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant keywords like 'SwiftUI', 'Liquid Glass', 'APIs', 'fallbacks', and 'modifier order', but misses natural user phrases like 'glass effect', 'glassEffect', 'translucent', 'blur', 'iOS 26', or 'visionOS' that users might naturally say when seeking this skill.	3 / 5
Distinctiveness Conflict Risk	'SwiftUI Liquid Glass APIs' is a fairly specific niche that wouldn't easily overlap with general SwiftUI skills or other UI framework skills. Minor overlap risk exists with a broader SwiftUI skill, but the 'Liquid Glass' qualifier provides good distinctiveness.	4 / 5
	Total	13 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/swiftui-liquid-glass/SKILL.md
Commit: fbdfd63

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.