CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-webxr

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

Quality

85%

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.

An exemplary lean, high-signal skill body: every rule is a concrete project constraint Claude could not guess, organized into clear platform/mode patterns with real validation guidance. The only meaningful improvement would be a short executable snippet for the USDZ export path, which is currently described at a slightly higher level than the WebXR rules around it.

DimensionReasoningScore

Conciseness

The ~22-line body is lean and dense with project-specific constraints (pinned r185 bundle, xrWorldRoot parenting rules, session config details) and assumes Claude already knows WebXR; the one-line AR Quick Look explanation conveys a required platform split rather than general knowledge. Every token earns its place, and the r185 reference is a hard pin constraint, not date-drift advice.

5 / 5

Actionability

Guidance is highly concrete — "renderer.xr.enabled = true", "renderer.setAnimationLoop(animate)", "THREE.USDZExporter", "document.createElement('a').relList.supports('ar')", and specific immersive-ar features (hit-test, anchors, domOverlay) — but there are no complete copy-paste code snippets (e.g., the USDZ material-conversion and export flow is described rather than shown), so it sits just below the fully-executable anchor.

4 / 5

Workflow Clarity

Patterns are clearly organized per mode with feature gating, fallback chains, an explicit restore-on-session-end step, and a Validation section with concrete commands ("npm test", "node --check") plus an honest note on what browser smoke tests cannot cover. It misses anchor 5 only because the USDZ export flow is a pattern list without an ordered sequence or fix-and-retry loop; nothing here is destructive or batch, so no cap applies.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file under 50 lines (intro, platform split, patterns, validation) with no bundle files and no content that warrants extraction; per the rubric's simple-skill guidance, this scores 5 on organization alone.

5 / 5

Total

18

/

20

Passed

Description

78%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 tight, trigger-focused description with strong natural keywords and excellent distinctiveness from its project scoping. Its main weakness is that the 'what' is implicit in the trigger clause and under-represents the skill's capabilities — notably the Apple AR Quick Look / USDZ export path that occupies half the skill body.

Suggestions

Lead with a brief 'what' clause before the 'Use when' trigger (e.g., "Integrates WebXR AR/VR sessions and Apple AR Quick Look USDZ export in Tiny World Builder. Use when…") so both what and when are explicit.

Add the missing natural trigger terms for the Apple path: "USDZ", "AR Quick Look", and "iOS/iPadOS", plus "Quest" and "immersive" for the headset path.

Mention the two entry modes users would name — "AR (hit-test, desk/floating)" and "VR (room scale)" — to round out coverage of the capability areas the body actually handles.

DimensionReasoningScore

Specificity

"adding or modifying WebXR, AR placement, VR immersion, headset controller input, or XR rendering modes" lists several concrete capability areas, matching the several-specific-actions anchor; it is not 5 because the skill's significant Apple USDZ / AR Quick Look work is unmentioned.

4 / 5

Completeness

The "Use when…" clause explicitly answers 'when' with concrete triggers, and the "adding or modifying…" phrase gives a 'what', but the what is thin and omits the iOS AR path — not the fully explicit what+when of anchor 5, and clearly above anchor 3 since the 'when' is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

"WebXR", "AR", "VR", "headset", "controller", and "rendering modes" are terms users would naturally say; a few natural synonyms are missing ("Quick Look", "USDZ", "Quest", "immersive"), so it falls just below comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to "Tiny World Builder" with XR-specific trigger phrases, giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jasonkneen/tiny-world-builder

Path

.codex/skills/tinyworld-webxr/SKILL.md

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.