CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-tinyverse-race-track

Use when changing the Tinyverse ground-surface race track, perimeter bridge loop, rally karts, or poser-surface show/hide hook.

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

93%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 lean, highly actionable ruleset that captures genuinely non-obvious project constraints (poser-surface Y scaling, material reuse, static mesh merging, the _tick loop contract) with concrete validation commands. The only gap is the absence of an error-recovery loop for failed validation checks.

DimensionReasoningScore

Conciseness

Every line carries project-specific knowledge Claude cannot infer (root.scale.y = 1/3, the M.* material families, the _tick contract, the animation-loop schema). There is no filler, no explanation of known concepts, and nothing to trim.

5 / 5

Actionability

Guidance is fully concrete and executable: exact file path ('engine/world/61-tinyverse-race-track.js'), exact constants, the full public API surface (show(), hide(), watch(), startRace(), stopRace(), rebuild(), group(), routeLength()), and copy-paste-ready validation commands (node --check, node tools/check.js).

5 / 5

Workflow Clarity

The editing constraints are unambiguous and a dedicated Validation section provides explicit checkpoints (two commands plus a visual check), but there is no error-recovery guidance — nothing says what to do when node tools/check.js fails — so it falls short of the feedback-loop anchor.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external reference files (none exist in the bundle), and is cleanly organized into a location line, Rules, and Validation sections — matching the simple-skill exception for well-organized short skills.

5 / 5

Total

19

/

20

Passed

Description

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

The description is a precise, low-conflict trigger for a niche project skill, but it is a 'when-only' description: it enumerates the objects being changed without ever stating what the skill does or guides. Adding an explicit capability statement and a few natural synonyms would round it out.

Suggestions

Add a leading 'what' clause before the 'Use when...' trigger, e.g., 'Rules for editing the Tinyverse race track module (road loop, bridge, rally karts, HUD).... Use when changing...' so both what and when are explicit.

Include natural synonyms and variations users might say, such as 'road loop', 'track', 'kart racing', or 'ground-surface show/hide', to broaden trigger-term coverage.

State the key capabilities concretely (e.g., 'wraps the poser-surface show/hide hooks, places track and kart geometry, and exposes a runtime API') so a reader can tell what the skill governs without opening the body.

DimensionReasoningScore

Specificity

The only action stated is 'changing', but the domain is named with concrete objects ('ground-surface race track, perimeter bridge loop, rally karts, poser-surface show/hide hook'), matching 'names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because no several specific actions are listed, and not a 2 because it is far more concrete than generic domain naming.

3 / 5

Completeness

An explicit and specific 'Use when...' trigger is present, but the description never states what the skill does — capabilities are only implied by the enumerated objects. It exceeds the vague when-only anchor (2) but lacks the clear 'what' required for a 4 or 5.

3 / 5

Trigger Term Quality

Good keyword coverage with naturally sayable project terms ('race track', 'rally karts', 'poser-surface', 'bridge loop'), but synonyms and common variations (e.g., 'road loop', 'track', 'karts') are missing, so it falls short of comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

'Tinyverse', 'poser-surface', and 'rally karts' are highly niche project-specific terms forming a clear, distinct trigger set with minimal conflict risk against any other skill.

5 / 5

Total

15

/

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-tinyverse-race-track/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.