xr-immersive-developer

Expert WebXR and immersive technology developer with specialization in browser-based AR/VR/XR applications

Quality

11%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./spatial-xr-immersive/skills/SKILL.md

Quality

Discovery

22%

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 description reads as a role/persona statement rather than a functional skill description. It lacks concrete actions, has no 'Use when...' trigger clause, and uses first-person-adjacent identity framing ('Expert... developer') instead of describing what the skill does. The WebXR domain specificity is its only notable strength.

Suggestions

Replace the role/identity framing with concrete actions: e.g., 'Creates browser-based AR/VR experiences using WebXR API, builds 3D scenes with Three.js/A-Frame, implements hand tracking and spatial anchors.'

Add an explicit 'Use when...' clause: e.g., 'Use when the user asks about WebXR, virtual reality, augmented reality, 3D web apps, immersive experiences, or mentions frameworks like Three.js or A-Frame.'

Include more natural trigger terms users would say, such as 'virtual reality', 'augmented reality', '3D', 'VR headset', 'Three.js', 'A-Frame', 'spatial', and file extensions like '.glb' or '.gltf'.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'expert' and 'specialization' without listing any concrete actions. It describes an identity/role rather than specific capabilities like 'create 3D scenes', 'implement hand tracking', or 'configure WebXR sessions'.	1 / 3
Completeness	The description only vaguely addresses 'what' (immersive technology development) and completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	It includes relevant domain keywords like 'WebXR', 'AR/VR/XR', 'browser-based', and 'immersive technology' that users might mention. However, it misses common variations like 'virtual reality', 'augmented reality', 'A-Frame', 'Three.js', '3D', 'headset', or 'spatial computing'.	2 / 3
Distinctiveness Conflict Risk	The WebXR/XR domain is fairly niche, which helps with distinctiveness. However, the broad phrasing 'immersive technology developer' and 'browser-based' could overlap with general web development or 3D graphics skills.	2 / 3
	Total	6 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a persona description masquerading as a skill file. It contains no actionable technical content—no code examples, no specific API usage patterns, no workflows, and no references to detailed materials. The entire content tells Claude what kind of developer to pretend to be rather than providing the concrete knowledge needed to actually build WebXR applications.

Suggestions

Replace persona/identity sections with concrete code examples for common WebXR tasks (e.g., initializing a WebXR session, setting up hand tracking, performing hit tests) using specific frameworks like Three.js or A-Frame.

Add a workflow for scaffolding and testing a WebXR project with explicit steps and validation checkpoints (e.g., 'verify XR session starts', 'test on Quest browser', 'check fallback on non-XR browser').

Include device-specific compatibility notes as a reference table or link to a separate COMPATIBILITY.md file rather than vaguely mentioning 'Meta Quest, Vision Pro, HoloLens, mobile AR'.

Add concrete performance optimization patterns with executable code (e.g., LOD setup in Three.js, draw call reduction techniques) instead of just listing concepts like 'occlusion culling, shader tuning'.

Dimension	Reasoning	Score
Conciseness	The content is almost entirely persona/identity description that Claude doesn't need. Phrases like 'Technically fearless, performance-aware, clean coder, highly experimental' and 'You've shipped simulations, VR training apps' are padding with no actionable value. The entire file describes what the agent is rather than what to do.	1 / 3
Actionability	There are zero concrete code examples, commands, API references, or executable guidance. Everything is vague direction like 'Implement immersive interactions using raycasting, hit testing, and real-time physics' without any specifics on how. No code snippets, no library-specific patterns, no configuration examples.	1 / 3
Workflow Clarity	There are no sequenced steps, no workflows, no validation checkpoints. The bullet points are capability declarations, not process instructions. Building WebXR apps involves multi-step processes (project setup, device testing, performance profiling) but none are described.	1 / 3
Progressive Disclosure	The content is a flat list of bullet points with no references to external files, no structured navigation, and no separation of overview from detailed content. For a topic as broad as WebXR development, there should be references to framework-specific guides, API references, or example projects.	1 / 3
	Total	4 / 12 Passed

Validation

90%

Warnings & errors only

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: 1 day ago

Table of Contents

Discovery Implementation Validation

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.