CtrlK
BlogDocsLog inGet started
Tessl Logo

iwsdk-ray

Ray-based interactions in the WebXR scene — click objects, press UI buttons, or distance-grab with DistanceGrabbable. Use when the user wants to point at and interact with something at a distance, click a UI button, or test ray-based selection.

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.

A well-structured, actionable skill body that leads with concrete executable commands, sequences the workflow with explicit validation checkpoints, and stays lean without explaining concepts Claude already knows. Organization via headers provides clear navigation for a self-contained single-workflow skill.

DimensionReasoningScore

Conciseness

Lean and operational throughout — every prose line is actionable guidance (e.g. "Do NOT move the controller — only rotate it") with no padding explaining what WebXR or a controller ray is, so each token earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands with concrete signatures — xr_look_at({ device, target:{x,y,z} }), xr_set_gamepad_state({device, buttons:[{index:0,value:1}]}), xr_animate_to(...) — not pseudocode.

3 / 3

Workflow Clarity

Clear ordered sequence (Required Core steps 1-4, then a single chosen Branch, then optional verify) with explicit checkpoints: session-status gating, "If the object is not found, report... and stop", and a screenshot verification step.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the body is a single tightly-coupled workflow organized under clean headers (Required Core, Interaction Branches, Notes) that give easy navigation without nested references.

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.

A strong, third-person description that states concrete capabilities and provides an explicit Use-when trigger with natural user phrasings. It occupies a clearly distinct niche and is unlikely to conflict with sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "click objects, press UI buttons, or distance-grab with DistanceGrabbable" — matching the anchor for several specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Ray-based interactions in the WebXR scene — click objects, press UI buttons, or distance-grab") and when via an explicit "Use when..." clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Natural phrasings a user would say ("point at and interact with something at a distance", "click a UI button") appear alongside the technical term, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

A clear WebXR-ray niche with distinct triggers (distance-grab, ray-based selection) makes it unlikely to fire for unrelated 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.