CtrlK
BlogDocsLog inGet started
Tessl Logo

tinyworld-webxr

Use when adding or modifying WebXR, AR placement, VR immersion, headset controller input, or XR rendering modes in Tiny World Builder.

71

Quality

86%

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

86%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.

A concise, technically dense skill body that gives concrete API-level guidance and a validation section without over-explaining known concepts. It is well-structured and actionable, with only minor gaps in copy-paste code formality and explicit error-recovery loops.

Suggestions

Add a short copy-paste-ready code snippet for the most common operation (e.g. enabling XR + setAnimationLoop, or the USDZ blob/<a rel="ar"> launch) to raise actionability to fully executable.

Add an explicit validate->fix->retry feedback loop in the Validation section (e.g. 'if node --check fails, fix the syntax error and re-run until it passes') to strengthen workflow clarity.

Consider adding concrete synonyms/casual phrasing (e.g. 'AR', 'VR', 'headset') to broaden trigger-term coverage in the description.

DimensionReasoningScore

Conciseness

Lean, efficient prose that assumes Claude's competence; it skips explaining what WebXR/USDZ are and every token earns its place, with no padded conceptual exposition.

5 / 5

Actionability

Provides concrete, mostly-executable guidance (e.g. 'renderer.xr.enabled = true', 'immersive-ar with required hit-test', material conversion to Standard equivalents), but presents instructions as prose rather than copy-paste-ready code blocks, leaving minor gaps.

4 / 5

Workflow Clarity

Sequences multi-step processes (USDZ export -> Blob -> object URL -> <a rel="ar"> launch; session-end restoration) with a Validation section including 'npm test' and 'node --check', but lacks an explicit fix->revalidate feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (Platform split, Patterns, Validation) with no nested or buried references; as a compact single-file skill with no external bundles, structure is appropriate and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A well-scoped, third-person description with an explicit 'Use when' clause and concrete XR feature triggers. It clearly answers both what the skill does and when to invoke it, with low conflict risk.

DimensionReasoningScore

Specificity

Names the domain and several specific capability areas ('WebXR, AR placement, VR immersion, headset controller input, or XR rendering modes') but uses only the generic verbs 'adding or modifying', leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (adding/modifying the listed XR features in Tiny World Builder) and 'when' via a concrete 'Use when' trigger clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('WebXR', 'AR placement', 'VR immersion', 'headset controller input', 'XR rendering modes') with good coverage, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to 'Tiny World Builder' with a clear niche (WebXR/XR integration) and distinct triggers, giving minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jasonkneen/tiny-world-builder
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.