CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-interactions

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

Quality

80%

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

Fix and improve this skill with Tessl

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

Quality

Content

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

An exceptionally actionable and well-sequenced test procedure: concrete commands, explicit assertions, recovery loops, and validation gates throughout. Its weaknesses are repetitive boilerplate across the 13 suites and a monolithic single-file structure that forgoes progressive disclosure despite being long enough to benefit from it.

Suggestions

Split the 13 suite specifications into one-level-deep reference files (e.g., references/suites/robot-poke.md) and keep SKILL.md as an overview with the shared setup, tool-call conventions, and a suite index.

State the shared conventions once (the 'ecs query then assert' pattern, placeholder arithmetic like <pos.z> + 0.3, and the 2>/dev/null suffix) instead of repeating them in every suite, shrinking boilerplate considerably.

DimensionReasoningScore

Conciseness

The body is command-driven with little conceptual padding and no explanations of things Claude already knows, but there is noticeable boilerplate repetition across the 13 suites — the identical 'ecs query ... then assert' pattern, repeated '2>/dev/null', and parenthetical placeholder explanations like '(where <z+0.3> = <robot-pos.z> + 0.3)' could be stated once. It is efficient overall with minor instances that could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

Every step is a fully executable, copy-paste-ready CLI command with exact JSON inputs, explicit timeout values, and concrete expected values (e.g., position near (0, 0.95, -1.5), 'Click - N+1', contactMs < 800). Placeholder substitution rules are explicitly defined inline, so the common cases are completely covered.

5 / 5

Workflow Clarity

The process is clearly sequenced (Steps 1-5) with explicit validation checkpoints after nearly every command ('Parse the JSON output and verify assertions before moving to the next command'), error-log gates, failure handling ('report FAIL for all suites and skip to Step 5'), a Recovery section with a bounded retry loop, and a required summary table. Although this is a batch operation, validation and feedback loops are present, so the batch cap does not apply.

5 / 5

Progressive Disclosure

Headers per Step and per Suite give the document internal structure, but roughly 670 lines of per-suite test specifications are inlined in SKILL.md with no bundle files at all — content with clear boundaries (individual suites, known-issues notes) that could live in one-level-deep reference files is kept inline. It is above 2 because the structure is good and nothing is buried, but below 4 because no content is split out despite obvious seams.

3 / 5

Total

17

/

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.

A specific, distinctive description that names concrete test areas, the target example, and the tool. Its main weakness is the absence of any 'when to use this skill' trigger clause, which both caps completeness and leaves users without explicit invocation guidance.

Suggestions

Append an explicit trigger clause, e.g.: 'Use when asked to run XR interaction tests, verify ray/poke behavior in the poke example, or regression-test input or audio changes in IWSDK.'

Add natural trigger synonyms such as 'XR', 'VR', 'immersive web', 'controller/hand interactions', or 'interaction regression test' to broaden natural-term coverage.

Consider mentioning the ECS/stability verification the skill actually performs (e.g., 'verify ECS registration and runtime stability') to close the coverage gaps.

DimensionReasoningScore

Specificity

The description lists several concrete test areas — "ray, poke/touch, dual-mode, hand poke, audio, UI panel" — plus the specific target ("the poke example") and tool ("the iwsdk CLI"), matching the 'several specific actions; minor gaps' anchor. It is not a 5 because the verb is uniformly 'test' and coverage omits areas the skill actually covers (ECS registration, entity discovery, stability).

4 / 5

Completeness

The 'what' is clear (test XR interaction behaviors against the poke example using the iwsdk CLI), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is above 2 because the 'what' is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Terms like "XR interactions", "poke/touch", "hand poke", "UI panel", "poke example", and "iwsdk CLI" are natural phrases a user needing this skill would say, giving good keyword coverage. It falls short of 5 because common variations/synonyms (e.g., VR, immersive, controller interaction, interaction regression) are missing.

4 / 5

Distinctiveness Conflict Risk

"against the poke example using the iwsdk CLI" pins a clear, project-specific niche with distinct triggers, making conflict with other skills very unlikely. It matches the 'clear niche with distinct triggers; minimal conflict risk' anchor exactly.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (676 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

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.