CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-asset-editing

Use when changing Tiny World Builder selection placement, freehand drawing, asset clipboard, cut/copy/paste/duplicate, saved templates, or Stamps panel navigation.

60

Quality

76%

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-asset-editing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 specific contract document that gives Claude exact APIs, keys, and files to route edits through, with a real validation section. Its weaknesses are repetition (especially the clipboard-preservation rule), no error-recovery loop around validation, and no progressive disclosure despite a length that clearly warrants splitting into reference files.

Suggestions

Consolidate the repeated 'must not overwrite the user's explicit copy/cut clipboard' rule into one stated invariant in the Clipboard section and reference it from the individual bullets.

Split the Stamps panel, Layers dialog, and Selection properties rule sets into references/ files (e.g. references/stamps-panel.md, references/layers-panel.md), keeping SKILL.md as a short overview with one-level-deep pointers.

Add a feedback loop to the Validation section: what to do when the syntax check, npm test, or browser-check fails (fix, re-run, only proceed when passing).

DimensionReasoningScore

Conciseness

The body is project-specific with no padding of concepts Claude already knows, but it can be tightened: "must not overwrite the user's explicit copy/cut clipboard" is repeated nearly verbatim across at least six bullets (lines 47-58), and bullets like the fence-leveling rule run long. This fits 'mostly efficient but could be tightened' better than the noticeably-verbose anchor at 2.

3 / 5

Actionability

Names exact executable surfaces — `setCell(x, z, opts)`, `applyToolToCell()`, `replaceWorldCoords()`, `tinyworld:asset-templates.v1`, `engine/world/33-radial-menu.js`, `window.__tinyworldSelection` — making the guidance concretely actionable for code edits. Not a 5 because no runnable snippets or command examples beyond the validation section are given, leaving minor gaps for the less-standard flows.

4 / 5

Workflow Clarity

The content is a rule catalog rather than a step sequence, but it closes with an explicit validation section ("Run the inline script syntax check, `npm test`, and `npm run build`. " plus a browser-check list covering the risky batch operations: "selected bulk placement, copy/paste/templates, duplicate"). Not a 5 because there is no failure/recovery feedback loop (what to do when a check fails), and the destructive/batch operations have validation listed only once at the end.

4 / 5

Progressive Disclosure

The body is well-sectioned ("Clipboard and templates", "Selection properties", "Stamps panel", "Layers dialog") but is a ~200-line monolith with no bundle files at all — the Stamps-panel and Layers-dialog rule sets in particular are clearly separable reference material. This matches 'some structure but content that should be separate is inline'; it is not a 2 because section headers and consistent bullet format keep it navigable.

3 / 5

Total

14

/

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 well-scoped, niche-specific description with explicit trigger guidance and concrete feature-area enumeration. Its main weakness is the thin "what" clause — it describes when to use the skill but not what the skill itself contributes.

Suggestions

Add a leading 'what' clause stating what the skill provides, e.g. 'Editing conventions and safety contracts for Tiny World Builder asset work. Use when...'

Include the natural trigger words users would say for the body's other major surfaces: brush/brush shapes, Layers panel, and selection properties.

DimensionReasoningScore

Specificity

Enumerates six concrete capability areas ("selection placement, freehand drawing, asset clipboard, cut/copy/paste/duplicate, saved templates, or Stamps panel navigation") rather than generic language. Not a 5 because the governing verb "changing" is abstract and body topics like brush shapes, Layers, and selection properties are uncovered.

4 / 5

Completeness

The "when" is explicit ("Use when changing...") and the enumerated areas imply the "what". Not a 5 because the description never states what the skill actually provides (editing conventions/contracts for the Tiny World Builder codebase); not a 3 because the trigger guidance is explicit and multi-scenario.

4 / 5

Trigger Term Quality

Natural user phrasings like "cut/copy/paste/duplicate", "freehand drawing", "saved templates", and "Stamps panel" map well to what a user would say. Not a 5 because common variations handled by the skill body ("brush", "layers", "properties", "clipboard" as a trigger word) are absent.

4 / 5

Distinctiveness Conflict Risk

"Tiny World Builder" plus the specific feature names create a clear niche with distinct triggers and minimal overlap risk with other skills. The anchor for 5 (clear niche, distinct triggers) matches exactly.

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-asset-editing/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.