test-interactions

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

Quality

72%

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

77%Weight 40%Scale 1-3

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 with executable commands and a well-sequenced, validated workflow including error recovery. Its main weaknesses are length/repetition across suites and a monolithic single-file structure that could benefit from reference files.

Suggestions

Factor the repeated look-at → sleep → query pattern into a brief shared template or helper note instead of restating it verbatim for every suite.

Move detailed per-suite definitions into a references/ file (e.g. SUITES.md) and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows and is densely actionable, but ~600 lines repeat the same look-at/sleep/query pattern across 12 suites and could be templated, fitting 'mostly efficient but could be tightened'.	2 / 3
Actionability	Every suite provides fully executable `npx iwsdk` commands with exact JSON payloads, explicit sleep durations, and concrete assertions, matching the 'fully executable ... copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear Step 1–5 sequence includes connectivity and error-log validation checkpoints plus a Recovery section with a retry-once feedback loop, matching the 'clear sequence with explicit validation steps; feedback loops' anchor.	3 / 3
Progressive Disclosure	Sections are well-organized, but all 12 suites live inline in a single ~600-line SKILL.md with no bundle files, so content that could be split into per-suite references is inline, fitting 'content that should be separate is inline'.	2 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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, clearly stating what the skill does, but it omits any explicit 'Use when...' trigger guidance, which caps completeness. Trigger terms are relevant but lean on domain jargon rather than natural user phrasing.

Suggestions

Add a 'Use when ...' clause naming natural user triggers (e.g. 'Use when testing XR input behaviors on the poke example, or when the user asks to verify ray/poke/dual-mode interactions').

Soften jargon by including layperson variants (e.g. 'XR input testing', 'controller and hand interaction tests') alongside 'iwsdk CLI' and 'dual-mode'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete interaction types ('ray, poke/touch, dual-mode, audio, UI panel') against a named example using a specific CLI, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is explicit ('Test XR interactions ... using the iwsdk CLI') but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	Terms like 'XR interactions', 'poke/touch', and 'audio' are plausible user phrasing, but coverage is jargon-heavy ('iwsdk CLI', 'dual-mode') and lacks common variations, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The narrow niche (XR interaction testing against the poke example via iwsdk CLI) is clearly distinct and unlikely to fire for unrelated skills.	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
Path: .claude/skills/test-interactions/SKILL.md
Commit: 0fb2195

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