liquid-glass-ios
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
Quality
64%
Does it follow best practices?
Impact
99%
1.54xAverage score across 3 eval scenarios
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 an excellent skill description that follows best practices. It clearly identifies the specific domain (Apple's Liquid Glass design system), provides concrete capabilities with specific API names, includes an explicit 'Use when...' clause with multiple trigger scenarios, and uses third person voice throughout. The technical specificity makes it highly distinguishable from other iOS development skills.
| 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, working with glass morphing transitions, or migrating from UIKit to SwiftUI glass APIs'). Has explicit 'Use when...' clause with specific triggers. | 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 clear niche: specifically targets Apple's Liquid Glass design system for iOS 26+/iPadOS 26+. The specific API names (glassEffect, GlassEffectContainer) and version requirements make it unlikely to conflict with general iOS or SwiftUI skills. | 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 functions primarily as a pointer to external documentation rather than providing actionable guidance itself. While the progressive disclosure to the reference file is well-structured, the skill body lacks any concrete code examples, specific implementation patterns, or meaningful workflow steps. The generic troubleshooting and workflow sections add no iOS/Liquid Glass-specific value.
Suggestions
Add at least one executable SwiftUI glassEffect code example in the skill body (e.g., basic .glassEffect() modifier usage with iOS 26 availability check)
Replace the generic troubleshooting section with Liquid Glass-specific issues (e.g., glass effect not rendering, morphing animation stuttering, UIKit/SwiftUI interop failures)
Provide a concrete workflow for common tasks like 'Adding glass effect to navigation bar' with specific validation steps
Remove or condense the generic 'Skill Does Not Trigger' and 'Guidance Conflicts' troubleshooting items that apply to all skills
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes generic troubleshooting sections (skill triggering, conflicts, generic output) that apply to any skill and don't add iOS-specific value. The boilerplate workflow section is also unnecessary padding. | 2 / 3 |
Actionability | No executable code, no concrete SwiftUI/UIKit examples, no copy-paste ready snippets. The content describes what exists in a reference file but provides no actual implementation guidance in the skill body itself. | 1 / 3 |
Workflow Clarity | The 3-step workflow is extremely vague ('Apply the skill rules', 'Validate output quality') with no concrete steps for implementing Liquid Glass. No validation checkpoints for glass effect implementation or migration processes. | 1 / 3 |
Progressive Disclosure | Clear structure with a well-organized reference to liquid-glass.md that lists specific topics. The reference is one level deep and clearly signaled with descriptive categories. | 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 | |
- 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.