test-locomotion

Test locomotion system (slide, snap turn, teleport, jump) against the locomotion example using the iwsdk CLI.

Quality

75%

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-locomotion/SKILL.md

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.

This is a highly actionable, well-sequenced test procedure with explicit validation checkpoints, error recovery, and known-issue workarounds. The primary weaknesses are slight redundancy between setup and Suite 5 assertions and the absence of progressive disclosure across a long monolithic file.

Suggestions

Deduplicate the system/priority assertions between "Verify Locomotion Setup" and Suite 5 (e.g., verify them once and have Suite 5 reference that check).

Move the Input Mapping Reference table and/or Known Issues & Workarounds into a references/ file (e.g., references/input-mapping.md) to shrink SKILL.md toward an overview.

Introduce a shorthand (e.g., LEFT_RELEASE, RIGHT_CENTER) for the repeated zeroed gamepad JSON payloads to reduce token cost without losing executability.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable commands, assertions, and timing instructions with no concept explanations, but has minor trimmable redundancy: system/priority assertions appear in both "Verify Locomotion Setup" and Suite 5, and full gamepad JSON payloads are repeated verbatim where a shorthand would suffice.	4 / 5
Actionability	Every step is a copy-paste-ready `npx @iwsdk/cli ...` command with exact `--input-json` payloads, timeouts, sleep durations, and explicit assertions, fully covering the common cases (forward/backward slide, both turn directions, teleport, jump).	5 / 5
Workflow Clarity	Five clearly sequenced steps with explicit validation checkpoints (connectivity check with retry/fail path, error-log assertion, per-suite asserts, 60s server-startup deadline), a Recovery section with a bounded one-retry-per-suite feedback loop, and a PASS/FAIL summary that requires actual-vs-expected values on failure.	5 / 5
Progressive Disclosure	The ~385-line body is a monolithic single file with no bundle files; it is well-sectioned with clear headers, but inline content like the input-mapping table and Known Issues could be split into referenced files, matching "some structure but content that should be separate is inline".	3 / 5
	Total	17 / 20 Passed

Description

66%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 and domain-specific, clearly stating what is tested and with which tool. Its main weakness is the absence of any explicit "Use when..." trigger guidance, which caps completeness and slightly limits natural triggering.

Suggestions

Append a trigger clause such as "Use when asked to test or verify locomotion, movement, teleporting, snap turning, or the iwsdk locomotion example."

Mention the full suite coverage (e.g., system registration and stability checks) so the description matches what the skill actually runs.

Add a couple of natural synonyms (e.g., "movement", "VR navigation") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Test locomotion system (slide, snap turn, teleport, jump) against the locomotion example using the iwsdk CLI" names several concrete test targets plus the tool and app under test, but omits coverage the body contains (system registration, stability), leaving minor gaps rather than comprehensive coverage.	4 / 5
Completeness	The "what" is explicit (test the locomotion system's slide/turn/teleport/jump behaviors against the example via the iwsdk CLI), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"slide", "snap turn", "teleport", "jump", and "locomotion" are natural terms a user would say, giving good keyword coverage, though common variations like "movement" or "VR navigation" are missing.	4 / 5
Distinctiveness Conflict Risk	The "locomotion" domain plus the four named behaviors plus "iwsdk CLI" carve a distinct niche with minimal conflict risk, though it could still overlap with sibling iwsdk example-test skills (e.g., grab or interaction example tests).	4 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: facebook/immersive-web-sdk
Path: .claude/skills/test-locomotion/SKILL.md
Commit: 0778f51

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