Builds native visionOS and Apple Vision Pro apps using SwiftUI, RealityKit, and the Liquid Glass design system. Creates volumetric views, implements Liquid Glass materials, configures immersive spaces, manages spatial WindowGroups, designs 3D UI layouts, and wires up RealityKit entities with gestures and attachments. Use when building visionOS apps, Apple Vision Pro experiences, volumetric windows, immersive spaces, mixed reality interfaces, or applying Liquid Glass effects with SwiftUI and RealityKit on visionOS 26.
96
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 clearly defines a specific niche (visionOS/Apple Vision Pro development), lists concrete actions, includes rich natural trigger terms, and provides explicit 'Use when' guidance. It uses proper third-person voice throughout and would be easily distinguishable from other Apple development skills. The description is comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates volumetric views, implements Liquid Glass materials, configures immersive spaces, manages spatial WindowGroups, designs 3D UI layouts, and wires up RealityKit entities with gestures and attachments. | 3 / 3 |
Completeness | Clearly answers both 'what' (builds native visionOS apps, creates volumetric views, implements Liquid Glass materials, etc.) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like building visionOS apps, volumetric windows, immersive spaces, and applying Liquid Glass effects. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'visionOS', 'Apple Vision Pro', 'volumetric windows', 'immersive spaces', 'mixed reality', 'Liquid Glass', 'SwiftUI', 'RealityKit', 'visionOS 26'. These are all terms a developer would naturally use when seeking help with this platform. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting visionOS/Apple Vision Pro development specifically, with unique triggers like 'Liquid Glass', 'volumetric windows', 'immersive spaces', and 'visionOS 26' that are unlikely to conflict with general SwiftUI or iOS development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that delivers concise, actionable, and well-structured guidance for visionOS 26 development. The four workflows cover the core spatial computing patterns with executable code, clear sequencing, and validation steps. The pitfalls table is an excellent addition that addresses common failure modes. Minor improvement could come from splitting into referenced sub-files for advanced topics, but the current length is manageable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what visionOS, SwiftUI, or RealityKit are, assumes Claude's competence with Swift/Apple frameworks, and every section delivers actionable code without preamble. The summary table at the top is a nice token-efficient overview. | 3 / 3 |
Actionability | Every workflow provides fully executable, copy-paste-ready Swift code with correct imports and complete struct/class definitions. Key APIs are named explicitly, and the pitfalls table provides specific troubleshooting guidance tied to concrete API calls. | 3 / 3 |
Workflow Clarity | Each workflow is clearly sequenced with numbered steps, explicit goals stated upfront, and validation checkpoints after key steps (e.g., 'Run on visionOS 26 Simulator. The panel should appear translucent...'). The workflows cover the full lifecycle from declaration to runtime verification. | 3 / 3 |
Progressive Disclosure | The content is well-structured with a summary table and four distinct workflow sections, but all content is inline in a single file. The documentation references at the top are helpful, but for a skill of this length (~180 lines of content), some workflows or the pitfalls table could be split into referenced files. However, the organization within the single file is clear and navigable. | 2 / 3 |
Total | 11 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
010799b
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.