test-interactions

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

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/test-interactions/SKILL.md

Quality

Content

88%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.

A highly actionable, well-sequenced test-runner skill with concrete commands, explicit validation, and a recovery loop; its only real weakness is that all 12 suites live in one long monolithic file rather than being split into reference materials.

Dimension	Reasoning	Score
Conciseness	The body is long but almost entirely executable commands, assertions, and justified domain specifics (e.g. SphereIntersector thresholds), with no padding of concepts Claude already knows; not a 5 because a few operational notes and repeated boilerplate could be trimmed.	4 / 5
Actionability	Every suite gives copy-paste-ready 'npx iwsdk ...' commands with exact JSON inputs, explicit sleep timing, and concrete assertions; the templated placeholders (<robot>, <robot-pos>) are clearly defined and resolved in-suite.	5 / 5
Workflow Clarity	A clear 5-step sequence (Install, Start Dev Server, Verify Connectivity, Run Test Suites, Cleanup) with explicit validation checkpoints (connectivity check, error-log assertions) and a Recovery feedback loop (stop -> restart -> re-setup -> retry) for this batch operation.	5 / 5
Progressive Disclosure	Well-organized into clearly headed steps, suites, Recovery, and Known Issues with easy header-based navigation and no external references needed; not a 5 because it is a ~600-line monolithic file with no content split into reference files.	4 / 5
	Total	18 / 20 Passed

Description

70%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.

The description is concrete, well-keyworded, and distinct, but it omits any 'Use when...' trigger guidance, which caps completeness. Adding an explicit trigger clause would lift the weakest dimension.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when verifying XR interaction behaviors (ray, poke/touch, dual-mode, audio, UI panel) in the poke example.'

Consider naming the additional suites covered in the body (stability, cross-entity isolation, input mode switching) so the description's scope matches the skill's actual coverage.

Include a couple of natural synonyms users might say (e.g. 'VR interactions', 'hand/controller input') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete interaction types ('ray, poke/touch, dual-mode, audio, UI panel') plus a named target ('poke example') and tool ('iwsdk CLI'); not a 5 because the single verb 'Test' leaves minor coverage gaps versus the body's fuller scope (e.g. stability, cross-entity isolation).	4 / 5
Completeness	Has a clear 'what' ('Test XR interactions ... against the poke example using the iwsdk CLI') but no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage with 'XR interactions', 'ray', 'poke/touch', 'audio', and 'UI panel' (poke/touch even supplies a synonym); not a 5 because variations like 'VR', 'hand tracking', or 'controller input' are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (XR interaction testing against a specific example via a specific CLI) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 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
Path: .claude/skills/test-interactions/SKILL.md
Commit: 13f42e7

Reviewed: 8 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.