visionos-spatial-engineer
Native visionOS spatial computing, SwiftUI volumetric interfaces, and Liquid Glass design implementation
38
23%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./spatial-visionos-engineer/skills/SKILL.mdQuality
Discovery
40%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 targets a very specific and distinctive domain (visionOS spatial computing with Liquid Glass), which makes it unlikely to conflict with other skills. However, it lacks explicit trigger guidance ('Use when...') and doesn't enumerate concrete actions, making it harder for Claude to know precisely when to select it and what capabilities it offers.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Use when building visionOS apps, Apple Vision Pro experiences, volumetric windows, immersive spaces, or applying Liquid Glass effects'.
List specific concrete actions such as 'Creates volumetric views, implements Liquid Glass materials, builds immersive spaces, configures RealityKit entities, and designs spatial UI layouts'.
Include common user-facing synonyms and related terms like 'Apple Vision Pro', 'RealityKit', '3D UI', 'immersive app', and 'mixed reality' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (visionOS spatial computing) and some actions/areas (SwiftUI volumetric interfaces, Liquid Glass design implementation), but doesn't list multiple concrete actions like 'create volumetric views, apply Liquid Glass effects, build immersive spaces'. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only partially specified, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'visionOS', 'SwiftUI', 'volumetric', 'Liquid Glass', and 'spatial computing' that developers would use, but misses common variations like 'Apple Vision Pro', 'immersive spaces', 'RealityKit', '3D interfaces', or '.reality files'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of visionOS, spatial computing, volumetric interfaces, and Liquid Glass design is highly specific and occupies a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a persona description or capability listing rather than an actionable skill document. It contains no executable code, no concrete workflows, and no specific implementation guidance—just categorized bullet points of technologies and concepts. Claude gains almost nothing from this that it wouldn't already know from its training data about visionOS development.
Suggestions
Replace the capability bullet lists with concrete, executable SwiftUI/RealityKit code examples (e.g., a complete glassBackgroundEffect implementation, a WindowGroup setup for volumetric content).
Add step-by-step workflows for common tasks like 'Creating a Liquid Glass window', 'Adding spatial widgets', or 'Setting up a volumetric scene' with validation steps.
Remove the 'Core Expertise', 'Technical Capabilities', and 'Approach' sections which describe what Claude should know rather than teaching it how to do things—Claude already understands these concepts.
Add at least 2-3 complete, copy-paste ready code snippets showing visionOS 26-specific patterns that differ from standard SwiftUI (e.g., new APIs, Liquid Glass modifiers, spatial widget configuration).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely descriptive bullet points listing concepts and capabilities Claude already knows. It reads like a resume or role description rather than actionable instructions. Phrases like 'Focuses on leveraging visionOS 26's spatial computing capabilities' add no value. | 1 / 3 |
Actionability | There is zero executable code, no concrete commands, no specific examples, and no copy-paste ready snippets. The entire skill describes what the agent should know rather than instructing it on how to do anything. Not a single SwiftUI code block or RealityKit example is provided. | 1 / 3 |
Workflow Clarity | There are no workflows, no sequenced steps, no validation checkpoints, and no processes described. The content is purely declarative lists of capabilities with no guidance on how to actually implement anything. | 1 / 3 |
Progressive Disclosure | The content has some structural organization with headers and sections, and includes external documentation references. However, the references are all to Apple's external docs rather than companion skill files, and the main content is a monolithic list of bullet points that could benefit from splitting actionable guidance into separate files. | 2 / 3 |
Total | 5 / 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 | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.