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
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines a narrow, specific capability (grabbing objects in WebXR scenes), provides explicit trigger guidance with natural user language, and includes technical details that both aid selection accuracy and reduce conflict risk. The description is concise yet comprehensive, covering the what, when, and important implementation details.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'grab an object', 'pick up', 'move', 'test grabbing'. Also specifies technical details like OneHandGrabbable/TwoHandsGrabbable components and proximity-based grip vs trigger distinction. | 3 / 3 |
Completeness | Clearly answers both 'what' (grab an object in WebXR using emulated controllers, supports specific components with proximity-based grip) and 'when' (explicit 'Use when the user wants to pick up, move, or test grabbing an object'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'grab', 'pick up', 'move', 'WebXR', 'controllers', 'object', 'grip', 'squeeze button'. Covers both casual ('pick up') and technical ('OneHandGrabbable', 'TwoHandsGrabbable') vocabulary. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: WebXR scene interaction with emulated controllers, specific to grabbing mechanics with named components (OneHandGrabbable, TwoHandsGrabbable). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that clearly defines a multi-step XR interaction workflow with precise tool calls, explicit parameter values, and strong guardrails. The required/optional split elegantly handles varying user intents, and the Notes section addresses critical pitfalls (wrong button index, teleport vs animate) that would otherwise cause subtle failures. The content is lean, actionable, and well-structured throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section serves a clear purpose. No unnecessary explanations of what XR is or how controllers work. The skill assumes Claude understands the domain and focuses purely on the specific workflow and critical constraints (e.g., squeeze vs trigger distinction). | 3 / 3 |
Actionability | Each step provides specific tool calls with exact parameters (device names, button indices, position coordinates). The commands are copy-paste ready with concrete values and clear parameter structures. Critical distinctions like button index 1 vs 0 are explicitly called out. | 3 / 3 |
Workflow Clarity | The workflow is clearly divided into required core (steps 1-5) and optional extensions (steps 6-9) with explicit sequencing. Validation is present (step 2 has a failure path, step 9 verifies via screenshot), and the Notes section provides critical guardrails against common mistakes that would break grab state. | 3 / 3 |
Progressive Disclosure | For a skill with no bundle files, the content is well-organized with clear section hierarchy (Required Core vs Optional Extensions vs Notes). The required/optional split is an effective form of progressive disclosure, and the content length is appropriate for inline presentation without needing external files. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- facebook/immersive-web-sdk
- Commit
b3d1162
- 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.