CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-grab

Test grab system (distance grab, one-hand grab, two-hand grab, hand pinch grab) against the grab example using the iwsdk CLI.

Quality

82%

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

SKILL.md
Quality
Evals
Security

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 an exemplary executable test procedure: concrete commands with exact JSON payloads, per-step assertions, explicit failure and recovery paths. The only deductions are minor duplication of the trigger/squeeze guidance and a monolithic single-file layout where reference material (Component Reference, Known Issues) could be split into bundle files. Results are strong overall.

DimensionReasoningScore

Conciseness

The body is dense and imperative (command, sleep, assert) with no explanations of concepts Claude already knows; however, the trigger-vs-squeeze distinction is stated twice (Component Reference and Known Issues) and the Component Reference table partially duplicates the suites, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Every test provides copy-paste-ready 'npx @iwsdk/cli ...' commands with exact --input-json payloads, timeouts, sleeps, and explicit assertions (e.g. "Assert: `Hovered` present"), fully matching anchor 5 for executable, ready-to-run guidance.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit validation after each command, failure handling ('report FAIL for all suites and skip to Step 5'), and a Recovery section with a bounded retry loop, matching anchor 5 (explicit validation steps plus feedback loops for error recovery).

5 / 5

Progressive Disclosure

No bundle files exist and the single file is well-sectioned (Steps, Suites, Component Reference, Known Issues, Recovery) with no nested references; at ~500 lines with Component Reference and Known Issues inlined, it fits anchor 4 (good structure, minor organization gaps) rather than the well-split 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, clearly naming the grab variants, tool, and target example. Its main weakness is the absence of any 'Use when...' trigger guidance, which caps completeness and weakens discoverability. Adding an explicit use-when clause with natural trigger phrases would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to test or verify grabbing in IWSDK examples, or when grab, distance grab, pinch grab, or controller grab behavior is mentioned.'

Include common natural variations and synonyms of the trigger terms (e.g. 'grabbing', 'pick up objects', 'XR controller interaction') to improve keyword coverage.

State what the skill produces (per-suite PASS/FAIL results with assertion details) to round out the 'what' side of the description.

DimensionReasoningScore

Specificity

Names the domain, tool ('iwsdk CLI'), target ('grab example'), and four concrete grab modes (distance, one-hand, two-hand, hand pinch), but 'Test' is the only verb and no assertion/reporting actions are described, matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear (test the four grab modes against the grab example via the iwsdk CLI) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 3; this matches anchor 3 exactly.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('grab', 'distance grab', 'one-hand grab', 'two-hand grab', 'hand pinch grab') but misses common variations such as 'grabbing', 'pick up', or 'XR interaction', fitting anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (IWSDK grab-system testing) with distinct trigger terms — the four grab-mode names — giving minimal conflict risk with other skills, matching anchor 5 rather than the 'minor overlap risk' of anchor 4.

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 (501 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-grab/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.