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.

69

Quality

83%

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

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 lean, high-signal reference of project-specific WebXR integration patterns with concrete APIs, clearly organized sections, and an explicit validation checkpoint — it assumes Claude's competence and avoids concept padding throughout.

DimensionReasoningScore

Conciseness

The body is dense yet every token earns its place — all of it is project-specific, non-obvious detail (vendor bundle path, USDZExporter material constraints, xrWorldRoot vs scene parenting) with no explanation of concepts Claude already knows.

3 / 3

Actionability

It names concrete APIs and exact steps (renderer.xr.enabled, THREE.USDZExporter, immersive-ar with required hit-test, xrWorldRoot.worldToLocal()); the rubric's scoring note says instruction-only skills are not penalized for lacking code when guidance is this actionable.

3 / 3

Workflow Clarity

Patterns are clearly labeled per scenario and the explicit Validation section ('npm test and the inline script node --check must pass') provides a real checkpoint; the simple-skills note permits a 3 for clear, validated guidance without a single linear sequence.

3 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections (platform split, Patterns, Validation), which the simple-skills note says merits a 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

67%

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 well-scoped and specific to a clear niche, with an explicit Use-when trigger, but it is entirely trigger-focused: it never states the skill's capability as a distinct what-statement, and it mixes natural terms with some technical jargon.

Suggestions

Lead with a one-line capability statement (e.g., 'Adds WebXR/AR/VR support to Tiny World Builder') before the 'Use when' clause so the 'what' is explicit, not implied.

Add a couple of casual user-facing trigger variations (e.g., 'AR mode', 'view in VR', 'headset support') alongside the technical terms to broaden natural keyword coverage.

Trim jargon-heavy triggers like 'XR rendering modes' or pair them with plainer phrasing so the trigger reads like something a user would actually say.

DimensionReasoningScore

Specificity

The phrase 'adding or modifying WebXR, AR placement, VR immersion, headset controller input, or XR rendering modes' lists multiple specific concrete capability areas, matching the score-3 anchor rather than the narrower score-2 'domain and some actions'.

3 / 3

Completeness

The explicit 'Use when ...' clause answers 'when' clearly, but there is no separate statement of what the skill does — the capability is only implied inside the trigger, and the rubric says to score only what is explicitly stated.

2 / 3

Trigger Term Quality

It includes natural terms (WebXR, AR, VR, headset) but also technical jargon ('XR rendering modes', 'headset controller input') and misses casual variations like 'AR mode' or 'view in VR', so it lands at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

Scoped to 'WebXR, AR placement, VR immersion ... in Tiny World Builder', it defines a clear niche with distinct triggers that are unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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.