CtrlK
BlogDocsLog inGet started
Tessl Logo

iwsdk-grab

Grab an object in the WebXR scene using emulated controllers. Use when the user wants to pick up, move, or test grabbing an object. Supports OneHandGrabbable and TwoHandsGrabbable components which use proximity-based grip (squeeze button), not trigger.

79

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, fully executable workflow with clear sequencing, explicit validation/verification checkpoints, and high-value cautionary notes. It is concise and actionable with no padding, and its organization suits a self-contained single-task skill.

DimensionReasoningScore

Conciseness

Lean prose plus executable code blocks per step with no explanation of concepts Claude already knows; the Notes add only genuinely non-obvious pitfalls, so every token earns its place.

3 / 3

Actionability

Every step is a concrete, parameterized tool call (xr_animate_to, xr_set_gamepad_state, scene_get_object_transform, browser_screenshot) with specific positions, making it copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

A clear numbered sequence split into required core (1-5) and optional extensions (6-9) with explicit checkpoints (session status check, not-found stop gate, Step 9 screenshot verification); not a 2 because checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

No bundle files exist to reference, but the single-task skill is well organized into Required Core, Optional Extensions, and Notes sections, satisfying the well-organized-sections bar for a self-contained skill.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, written in third person, and clearly answers both what the skill does and when to use it with natural trigger terms. It is distinctive and specific with no over-claims or padding.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("Grab an object", "pick up, move, or test grabbing") plus specific component types, matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly states what it does ("Grab an object in the WebXR scene using emulated controllers") and when to use it ("Use when the user wants to pick up, move, or test grabbing an object"), satisfying both what and when with an explicit trigger.

3 / 3

Trigger Term Quality

Uses natural user phrasings ("pick up", "move", "grab", "test grabbing an object") that a user would naturally say, giving good coverage rather than just a few relevant keywords.

3 / 3

Distinctiveness Conflict Risk

The WebXR/emulated-controller scope plus named component types and the squeeze-not-trigger detail carve a clear niche unlikely to overlap with other skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
facebook/immersive-web-sdk
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.