CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-tile-variation

Use when adding or changing Tiny World Builder tile/object repeat-click behavior, terrain stacking, floors/intensity, fences, rocks, walls, crops, or Monument Valley-like height/detail growth.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/tinyworld-tile-variation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 dense, highly actionable rules document that respects the reader's intelligence and grounds every rule in real identifiers, files, and values. Its main weaknesses are inlined reference-grade detail (terrain-variant pipeline, fence/gate authoring) that belongs in separate reference files, and a missing error-recovery loop around the validation steps.

Suggestions

Move the terrain-variants slicing pipeline (paths, crop coordinates, voxel repeat scales) and the generated-enclosure fence/gate authoring rules into references/ files (e.g. references/terrain-variants.md, references/enclosures.md) and keep one-line pointers with the core rule in SKILL.md.

Turn the Validation section into an ordered checklist with an explicit fix-and-recheck loop, e.g. 'if a check fails, fix the mesh-rebuild or data-layer issue and re-run the checks before finishing'.

Add short call-shape snippets for the pivotal functions (terrainRiseAt, terrainSheetVariantMaterial, setCell) so the guardrails are directly copy-pasteable when editing the target codebase.

DimensionReasoningScore

Conciseness

The body is almost entirely terse, project-specific imperatives ('Do not add new saved fields unless necessary; prefer `floors`') with no padding or explanation of concepts Claude already knows. A few bullets run very long — the fence/gate enclosure rules and the terrain-variants pipeline bullet could each be tightened — which keeps it below level 5 but well above the verbose anchors.

4 / 5

Actionability

Guidance is concrete and executable: exact identifiers (`terrainFloors`, `terrainRiseAt`, `terrainSheetVariantMaterial()`), file paths (`tools/slice-terrain-variants.mjs`, `textures/terrain-variants/source/tw.png`), a fence-level table, exact values ('terrainRiseForLevel(level) returns (level - 1) * 1.12'), and a migration rule ('migrate object cells to `terrainFloors: 1`'). It stops short of level 5 only in lacking call-shape snippets for the key functions, and per the rubric's notes absence of code in an instruction-only skill is not penalized when the guidance is this actionable.

4 / 5

Workflow Clarity

This is a rules/guardrails skill rather than a sequenced procedure, and it is organized as Expected behavior → Implementation guardrails → Validation, with an explicit validation checklist ('Repeated object placement should keep `terrainFloors` unchanged', 'Same-terrain repeat placement should be visible before refresh/reload'). Checkpoints are present so it clears level 3, but there is no error-recovery loop, capping it at 4.

4 / 5

Progressive Disclosure

The skill is a single ~120-line file with no bundle files at all; clearly separable material (the terrain-variant slicing pipeline, fence/gate authoring rules, LandscapeEngine mesh modes, castle auto-promotion history) is inlined in one SKILL.md. Section headers give it real structure above level 2, but the length, density, and lack of any well-signaled one-level-deep references keep it at 3 rather than 4.

3 / 5

Total

15

/

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.

A highly distinctive, well-triggered description with good natural keywords, but it is essentially one long 'Use when' clause: the what-the-skill-does side is only implicit. Stating the concrete behaviors the skill enforces before the trigger clause would lift both completeness and specificity.

Suggestions

Lead with a concrete 'what' clause before the trigger, e.g. 'Enforces Tiny World Builder's terrain/object layering, rendering, and authoring rules: keeps floors vs terrainFloors separate, keeps visual offsets render-only, and validates repeat-click growth. Use when...'.

Name one or two concrete actions users take, such as 'stacking terrain on repeat clicks' or 'authoring fence/gate enclosures on generated islands', to convert the generic 'adding or changing' verb into specific capabilities.

Add a couple of natural trigger synonyms users might say, such as 'placing tiles/objects repeatedly' or 'building height/stacking', to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Tiny World Builder tile/object') and enumerates many concrete subjects ('repeat-click behavior, terrain stacking, floors/intensity, fences, rocks, walls, crops'), but the only action offered is the generic 'adding or changing', so it does not reach level 4's several distinct specific actions. It is well above level 2 because the enumerated topics are highly specific rather than minimal or generic.

3 / 5

Completeness

The 'when' is explicit ('Use when adding or changing...'), but the 'what' is only weakly implied — the description never states what the skill actually provides (layered-data rules, rendering guardrails, validation checks). This sits between anchor 2 ('only when present') and anchor 4 (both what and when explicit), landing at 3 because the trigger clause does name the operations involved.

3 / 5

Trigger Term Quality

It contains natural terms a user would say — 'fences', 'rocks', 'walls', 'crops', 'terrain', 'height', 'tile' — anchored by the product name 'Tiny World Builder'. A few natural variations are missing (e.g. 'buildings', 'placing', 'stacking blocks'), which keeps it below level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche tied to a named project ('Tiny World Builder', 'Monument Valley-like height/detail growth') with distinct, domain-specific triggers, so it is unlikely to fire for the wrong 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-tile-variation/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.