test-locomotion

Test locomotion system (slide, snap turn, teleport, jump) against the locomotion 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-locomotion/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.

The content is a highly actionable, well-sequenced test procedure with executable commands, explicit validation checkpoints, and error-recovery guidance. The main improvement space is conciseness (factoring repeated JSON/flags) and potentially splitting the input-mapping reference into a bundle file.

Suggestions

Factor the repeated '2>/dev/null' suffix and full gamepad JSON payloads (e.g. via a shared note or variables) to reduce repetition and token cost.

Consider moving the 'Input Mapping Reference' table and 'Known Issues & Workarounds' into a references/ bundle file linked from the body to improve progressive disclosure.

Tighten the convention callouts (tool-call format, IMPORTANT notes) since the repeated command examples already demonstrate the pattern.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean operational commands paired with explicit assertions, with only minor over-explanation (convention callouts, repeated full JSON blobs and '2>/dev/null' that could be factored), fitting anchor 4 rather than the fully trimmed anchor 5.	4 / 5
Actionability	Every step gives fully executable, copy-paste-ready 'npx iwsdk' commands with exact '--input-json' payloads and concrete screenshot/assertion steps covering the common cases.	5 / 5
Workflow Clarity	A clear Step 1–5 sequence with explicit validation assertions after each test, plus a Recovery section with retry feedback loops and a final summary table; the batch operation includes validation, so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-structured with clear Step/Suite headers and easy navigation, and the inline content genuinely belongs to a sequential procedure. It is longer than 50 lines with no external references, so it stops short of anchor 5.	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 specific and distinctive, naming the tool, target, and concrete locomotion subsystems, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause would raise the strongest remaining weakness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when testing or verifying the IWSDK locomotion example, or when validating slide, snap turn, teleport, or jump behavior.'

Add a few natural synonyms/variants (e.g. 'VR movement', 'thumbstick locomotion') to broaden trigger-term coverage.

Consider enumerating the distinct test actions (verify movement, verify rotation, verify teleport) rather than a single 'Test' verb to push specificity toward anchor 5.

Dimension	Reasoning	Score
Specificity	Names the domain, tool ('iwsdk CLI'), target ('locomotion example'), and enumerates four subsystems (slide, snap turn, teleport, jump); a single action verb applied to multiple targets fits anchor 4 rather than the multi-verb anchor 5.	4 / 5
Completeness	It clearly states what the skill does but lacks any 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'locomotion', 'slide', 'snap turn', 'teleport', and 'jump' are natural terms a user testing VR locomotion would say, giving good keyword coverage, but no synonyms or variants are present so it stops short of anchor 5.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (VR locomotion testing via the iwsdk CLI against a specific example) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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: 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.