test-interactions

Test XR interactions (ray, poke/touch, dual-mode, audio, UI panel) against the poke example using the iwsdk CLI.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The content is highly actionable and clearly sequenced with pervasive validation and a recovery loop, scoring top marks on conciseness, actionability, and workflow clarity. Its only weakness is progressive disclosure: it is a monolithic single file with no external references despite a length that could benefit from splitting.

Suggestions

Split per-suite detail (e.g., suites 3-9 interaction recipes, audio/UI suites) into reference files under references/ and keep SKILL.md as a concise overview pointing to them, improving progressive disclosure.

Consider extracting the Known Issues & Workarounds and Recovery sections into a references/troubleshooting.md referenced one level deep from the body.

Preserve the executable command + Assert pattern and the retry feedback loop when refactoring, as they are the skill's core strengths.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable commands, assertions, and operationally relevant notes (Known Issues, Recovery) without explaining concepts Claude already knows (XR/ECS), fitting the score-3 anchor for lean, competence-assuming content despite its 600-line length being the test suite itself.	3 / 3
Actionability	Every test is a fully executable `npx iwsdk ...` command with exact `--input-json` payloads, explicit sleep durations, and concrete Assert checkpoints — copy-paste ready, matching the score-3 anchor rather than the pseudocode of score 2.	3 / 3
Workflow Clarity	A clear 5-step / 12-suite sequence with explicit per-test validation checkpoints and a Recovery feedback loop (stop → restart → retry, one retry per suite), satisfying the score-3 anchor including feedback loops for batch-style operations.	3 / 3
Progressive Disclosure	No bundle files exist and all content is inline in a single 600-line monolithic file; sections are well-organized (not a score-1 wall of text) but content that could be split into reference files is inline, fitting the score-2 anchor rather than the overview-plus-one-level-references structure of score 3.	2 / 3
	Total	11 / 12 Passed

Description

67%

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 is specific and distinctive, naming concrete XR interaction modes and the tool/target, but omits an explicit "Use when..." trigger clause and leans on jargon-heavy terms, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit "Use when..." trigger clause, e.g., "Use when testing XR interaction behaviors (ray, poke/touch, dual-mode, audio, UI panel) in the poke example."

Soften jargon in trigger terms — include natural variations like "VR/AR interaction testing", "controller/hand input", or "near-touch interaction" alongside "poke" and "dual-mode".

Keep the concrete action list and tool name; they are the description's strongest features.

Dimension	Reasoning	Score
Specificity	Quotes "Test XR interactions (ray, poke/touch, dual-mode, audio, UI panel)" and "against the poke example using the iwsdk CLI" — it lists multiple concrete actions and names the tool and target, matching the score-3 anchor rather than the partial coverage of score 2.	3 / 3
Completeness	It clearly states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2; it is not a 1 because the what is specific and clear.	2 / 3
Trigger Term Quality	Terms like "XR interactions", "audio", and "UI panel" are relevant, but the phrasing is tool/jargon-centric ("poke/touch", "dual-mode", "iwsdk CLI") and missing common natural variations, fitting score 2 rather than the broad coverage of score 3.	2 / 3
Distinctiveness Conflict Risk	Testing XR interactions against a specific poke example via the iwsdk CLI is a clear, narrow niche unlikely to trigger for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (605 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: facebook/immersive-web-sdk
Commit: 42af866

Reviewed: 6 days 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.