Apple's Liquid Glass design system for iOS 26+ and iPadOS 26+. Use when building iOS 26+ UI with glassEffect, implementing GlassEffectContainer, working with glass morphing transitions, or migrating from UIKit to SwiftUI glass APIs.
76
64%
Does it follow best practices?
Impact
99%
1.54xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/design/liquid-glass-ios/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly identifies a specific design system (Liquid Glass), provides concrete implementation scenarios, includes natural technical keywords developers would use, and has a clear 'Use when...' clause with explicit triggers. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'building iOS 26+ UI with glassEffect', 'implementing GlassEffectContainer', 'working with glass morphing transitions', 'migrating from UIKit to SwiftUI glass APIs'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Apple's Liquid Glass design system') and when ('Use when building iOS 26+ UI with glassEffect, implementing GlassEffectContainer...') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural technical keywords users would actually search for: 'Liquid Glass', 'iOS 26+', 'iPadOS 26+', 'glassEffect', 'GlassEffectContainer', 'glass morphing transitions', 'UIKit', 'SwiftUI glass APIs'. Good coverage of terms developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific triggers like 'Liquid Glass', 'iOS 26+', 'GlassEffectContainer', and 'glass morphing transitions'. Unlikely to conflict with general iOS or SwiftUI skills due to the specific design system focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good progressive disclosure structure but critically lacks actionable content. It functions more as a table of contents pointing to references than a skill that teaches implementation. The troubleshooting and workflow sections are generic templates that don't provide iOS/Liquid Glass-specific guidance.
Suggestions
Add executable SwiftUI code examples showing basic glassEffect modifier usage and GlassEffectContainer patterns directly in the skill file
Replace the generic workflow with iOS-specific implementation steps: version checking, applying glass effects, testing on device, handling fallbacks
Include at least one concrete UIKit NSGlassEffectView code snippet to demonstrate the API
Remove or condense the generic troubleshooting section in favor of Liquid Glass-specific gotchas (e.g., element limits, layer placement issues)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes generic boilerplate sections (Troubleshooting, Workflow) that don't add iOS-specific value and could be trimmed. The actual glass-specific content is appropriately delegated to references. | 2 / 3 |
Actionability | No executable code examples are provided. The 'Examples' section shows trigger scenarios but lacks actual SwiftUI/UIKit code demonstrating glassEffect usage. The skill describes what to do conceptually but provides no copy-paste ready implementations. | 1 / 3 |
Workflow Clarity | The workflow section is generic meta-guidance about skill usage, not a concrete sequence for implementing Liquid Glass. No validation checkpoints, no specific steps for glass effect implementation, and no error recovery patterns for common issues. | 1 / 3 |
Progressive Disclosure | Excellent structure with clear overview pointing to a single well-organized reference file. The reference sections are clearly signaled with descriptive labels, and navigation is straightforward with one-level-deep linking. | 3 / 3 |
Total | 7 / 12 Passed |
Validation
90%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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
7b466be
Table of Contents
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.