CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xr-mode-test

Test XR session lifecycle and mode transitions. Use when verifying XR enter/exit behavior, testing mode-dependent features, or debugging session state issues.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

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

The body is an exemplar of a compact test-procedure skill: exact tool calls, expected values per step, verification checkpoints at every state transition, and a clean arguments example. Its single gap is the absence of failure-handling branches (what to do when a step's verification fails), which keeps workflow clarity at 4.

DimensionReasoningScore

Conciseness

Each step is a bare tool invocation plus expected-value bullets ("Session is active", "`visibilityState` is `\"visible\"`") with no concept explanations or padding; every token earns its place, matching the lean-and-efficient anchor rather than the 4 anchor since nothing needs trimming.

5 / 5

Actionability

Every step names an exact executable command (e.g. `mcp__iwsdk-runtime__xr_accept_session`, `mcp__iwsdk-runtime__xr_end_session`) and the Arguments section includes a worked example (`/xr-mode-test "MODE|RESET"`), matching the fully-executable anchor; it is not the 4 anchor because there are no gaps in the common-case coverage.

5 / 5

Workflow Clarity

A clearly sequenced 7-step flow with explicit verification checkpoints after each transition (steps 1, 3, 6, and 7), matching the clear-sequence-with-most-checkpoints anchor; it falls short of 5 because no error-recovery guidance exists for failures such as a session that does not activate.

4 / 5

Progressive Disclosure

The skill is a self-contained ~64-line checklist with well-organized sections (Test Flow, Arguments, Expected Results) and no bundle files; nothing is inlined that belongs in a separate file, so per the simple-skill note well-organized sections alone warrant the top anchor.

5 / 5

Total

19

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concise, with explicit what and when clauses anchored to concrete XR terms. Its only weaknesses are moderate synonym coverage (no WebXR/VR/immersive variants) and a slightly broad trigger phrase that could overlap with related testing skills.

DimensionReasoningScore

Specificity

"Test XR session lifecycle and mode transitions" plus "verifying XR enter/exit behavior, testing mode-dependent features, debugging session state issues" lists several concrete actions, matching the several-specific-actions anchor; it falls short of 5 because finer-grained capabilities (device verification, log inspection) are not named.

4 / 5

Completeness

The what ("Test XR session lifecycle and mode transitions") and an explicit when clause with three concrete trigger conditions ("Use when verifying... testing... or debugging...") are both clearly stated, matching the both-answered-with-concrete-triggers anchor rather than the 4 anchor where the 'when' is less specific.

5 / 5

Trigger Term Quality

Phrases like "XR enter/exit behavior", "mode transitions", and "session state issues" are natural things a user would say, but common synonyms such as WebXR, VR, immersive mode, or headset are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"XR session lifecycle" and "mode transitions" carve out a clear niche with minimal conflict risk, but "testing mode-dependent features" is broad enough to overlap with adjacent testing skills, fitting the mostly-distinct anchor rather than the clear-niche one.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

facebook/immersive-web-sdk

Path

.claude/skills/xr-mode-test/SKILL.md

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.