xr-immersive-developer
Creates browser-based AR/VR/XR experiences using the WebXR Device API, builds 3D scenes with Three.js, A-Frame, and Babylon.js, implements hand tracking, raycasting, hit testing, spatial anchors, and controller input, and applies performance optimizations like LOD, occlusion culling, and shader tuning for headsets and mobile AR. Use when the user asks about WebXR, virtual reality, augmented reality, immersive 3D web apps, VR headsets, spatial computing, or mentions frameworks like Three.js, A-Frame, Babylon.js, or file formats like .glb or .gltf.
90
88%
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 thoroughly covers specific capabilities, includes comprehensive trigger terms, explicitly states both what the skill does and when to use it, and occupies a clearly distinct niche. It uses proper third-person voice throughout and avoids vague language or buzzwords. The description is detailed yet well-organized, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating browser-based AR/VR/XR experiences, building 3D scenes with named frameworks, implementing hand tracking/raycasting/hit testing/spatial anchors/controller input, and applying specific performance optimizations like LOD, occlusion culling, and shader tuning. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates AR/VR/XR experiences, builds 3D scenes, implements tracking and input, applies performance optimizations) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios and keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: WebXR, virtual reality, augmented reality, immersive 3D web apps, VR headsets, spatial computing, Three.js, A-Frame, Babylon.js, .glb, .gltf. These are all terms a user would naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting WebXR and immersive web experiences specifically. The combination of WebXR API, specific 3D frameworks (Three.js, A-Frame, Babylon.js), XR-specific features (hand tracking, spatial anchors), and file formats (.glb, .gltf) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent executable code examples covering the full WebXR development workflow from scaffolding to debugging. The validation checkpoints are a notable strength, providing clear criteria for verifying each step works correctly. The main weakness is that the content is somewhat long for a single SKILL.md and could benefit from splitting reference material (device compatibility, performance patterns) into linked files.
Suggestions
Move the device compatibility table to a separate DEVICES.md reference file and link to it from the main skill
Consider splitting performance optimization patterns into a PERFORMANCE.md file to keep the main skill focused on core WebXR setup and interaction
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary elements like emoji headers, minor explanatory comments Claude wouldn't need (e.g., '// 500 objects — 1 draw call'), and the device compatibility table adds bulk that could be a separate reference file. However, it avoids explaining basic concepts like what WebXR or Three.js are. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste-ready code examples covering Three.js VR setup, A-Frame scenes, hand tracking, raycasting, hit testing, LOD, instanced meshes, and session feature requests. The code is complete with proper imports and realistic usage patterns. | 3 / 3 |
Workflow Clarity | The scaffolding workflow has clear numbered steps with explicit validation checkpoints after each step (e.g., 'confirm the Enter VR button appears and clicking it starts an immersive-vr session without console errors'). The debugging section provides a troubleshooting flow for common issues with specific fixes. The graceful degradation pattern includes a clear decision tree. | 3 / 3 |
Progressive Disclosure | The content is well-organized into logical sections with clear headers, but it's a fairly long monolithic file (~200 lines) with no references to external files for detailed topics like the device compatibility table, shader optimization details, or framework-specific deep dives. The device compatibility table and performance section could be split into separate reference files. | 2 / 3 |
Total | 10 / 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-agents
- Commit
010799b
- 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.