Test XR session lifecycle and mode transitions. Use when verifying XR enter/exit behavior, testing mode-dependent features, or debugging session state issues.
71
87%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
75%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 a solid description with clear 'what' and 'when' clauses and a distinct niche. Its main weakness is that the specificity of actions could be more concrete (e.g., listing specific test scenarios or tools), and the trigger terms could include more natural variations like 'WebXR', 'VR', 'AR' that users might actually say.
Suggestions
Add more concrete actions such as 'simulate session start/end events, validate mode switching between inline and immersive, check session state persistence'.
Include common user-facing trigger term variations like 'WebXR', 'VR session', 'AR session', 'immersive mode' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (XR session lifecycle) and some actions (test mode transitions, verify enter/exit behavior, debug session state), but doesn't list multiple concrete specific actions like specific test operations or tools used. | 2 / 3 |
Completeness | Clearly answers both what ('Test XR session lifecycle and mode transitions') and when ('Use when verifying XR enter/exit behavior, testing mode-dependent features, or debugging session state issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'XR session', 'mode transitions', 'enter/exit behavior', and 'session state', but misses common variations users might say such as 'WebXR', 'VR', 'AR', 'immersive mode', or 'headset session'. | 2 / 3 |
Distinctiveness Conflict Risk | XR session lifecycle testing is a very specific niche that is unlikely to conflict with other skills. The triggers around XR enter/exit, mode transitions, and session state are distinct and narrowly scoped. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that clearly defines an XR session lifecycle test with concrete tool calls, explicit verification steps, and a clean sequential workflow. It's concise, actionable, and appropriately structured for its scope. The inclusion of the $ARGUMENTS filter and expected results reporting format rounds out the skill nicely.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what XR is or how sessions work. Steps are terse and assume Claude knows the domain. Token-efficient throughout. | 3 / 3 |
Actionability | Each step specifies the exact MCP tool to call and what to verify in the response. The tool names are concrete and copy-paste ready, with clear expected outputs for each step. | 3 / 3 |
Workflow Clarity | Clear 7-step sequential workflow with verification after each state transition (enter → verify active → exit → verify ended → check logs). Includes validation checkpoints at steps 3, 6, and 7, and the expected results section defines pass/fail criteria. | 3 / 3 |
Progressive Disclosure | This is a focused, single-purpose skill under 50 lines with no need for external references. The content is well-organized with clear section headers (Test Flow, Arguments, Expected Results) and the numbered steps provide natural structure. | 3 / 3 |
Total | 12 / 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 | |
e8f9df1
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.