CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-tool-icons-and-modes

Use when changing Tiny World Builder's mode indicator, boot tool selection, or Esc-to-Select behaviour.

Quality

71%

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-tool-icons-and-modes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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, high-signal body of project-specific constraints with excellent identifier-level specificity and no filler, undermined by one outright internal contradiction (mode indicator kept vs. removed) and a monolithic single-file structure that has outgrown SKILL.md. Splitting into per-topic references and resolving the stale mode-indicator passage would raise most dimensions.

Suggestions

Resolve the direct contradiction: the Mode safety section says to keep `#mode-indicator` styled and pointer-events:none while the toolbar section says it has been removed from the DOM — delete or update the stale passage.

Split the ~93-line body into one-level-deep references (e.g. references/mode-safety.md, references/toolbar-palette.md, references/walk-modes.md) and keep SKILL.md as a short overview with clearly signaled links.

Add file locations for the remaining cited functions (`bootApp`, `selectTool`, `mpEditAllowed`, `setShowcaseActive`, `setCameraMode`) the way other functions are annotated, so every instruction is directly actionable.

DimensionReasoningScore

Conciseness

The body is almost entirely project-specific facts (selectors, function names, storage keys, breakpoints) with zero explanation of concepts Claude already knows — close to anchor 5. It drops to 4 because of redundant/contradictory tokens: the mode indicator is described twice with conflicting guidance ("Keep it pointer-events:none" in Mode safety vs. "has been removed from the DOM... no-ops" in the toolbar section), so one of those passages is wasted context.

4 / 5

Actionability

For an instruction-only skill the guidance is highly concrete — exact identifiers (`#toolbar-show-groups`, `tinyworld:showGroups`, `buildToolButton(t, { flyout: true })`), file locations (`engine/world/35-tool-palette.js`, `19-tools-toolbar.js`, `20-input-place-erase.js`), and a runnable command (`npm test`). It falls short of anchor 5 because several cited functions (`bootApp`, `selectTool`, `mpEditAllowed`, `setShowcaseActive`) lack file locations, and the contradictory mode-indicator guidance leaves the reader with an ambiguous instruction.

4 / 5

Workflow Clarity

This is an invariants/gotchas reference rather than a sequenced workflow, and it does include one validation checkpoint ("`npm test` ... Update those static guards when changing boot mode, launcher chrome, or mode persistence"). However, there is no ordering of concerns within each change area, and the direct contradiction on `#mode-indicator` (keep-and-style vs. removed-from-DOM) means a reader cannot determine the correct action, which is exactly the implicit-checkpoint failure anchor 3 describes.

3 / 5

Progressive Disclosure

The body has real section structure (## Mode safety, ## Gotcha, ## Bottom toolbar vs floating block palette) but no bundle files exist, and at ~93 dense lines it mixes at least three distinct concern areas (mode safety, launcher modal, toolbar/palette) that clearly belong in separate reference files per the skill's own size. This matches anchor 3 — structure present, but content that should be split is inlined — and is below anchor 4 because the split is overdue rather than a minor gap.

3 / 5

Total

14

/

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-targeted trigger clause with good natural keywords, but it is a 'when'-only description: it never states what the skill provides, and its trigger coverage is narrower than the skill's actual scope. Adding a short 'what' clause and a few more trigger surfaces would lift it substantially.

Suggestions

Add a 'what' clause before the 'Use when' clause, e.g. "Project-specific mode-safety rules and gotchas covering boot tool state, play/showcase modes, walk modes, and toolbar/palette behavior. Use when changing..."

Include trigger terms for the other surfaces the body actually covers: toolbar vs floating palette, Showcase mode, camera/walk modes (tp/fp), and the welcome/launch modal.

Mention the validation hook (npm test static guards) as a trigger cue for users asking about test failures after mode changes.

DimensionReasoningScore

Specificity

The description names a concrete domain ("Tiny World Builder's mode indicator, boot tool selection, or Esc-to-Select behaviour") but the only action stated is the generic verb "changing" — it lists change targets rather than describing what the skill actually provides (the safety rules and constraints for those changes). This matches anchor 3 (domain plus limited concrete actions, not comprehensive); it is above anchor 2 because the targets are specific, not generic, but below anchor 4 because no real capability coverage is enumerated.

3 / 5

Completeness

The "when" is explicit and well-formed ("Use when changing..."), but the "what" is entirely absent — the description never says the skill contains mode-safety constraints and gotchas. Anchor 2 (only 'when' present without 'what', e.g. "Use when working with documents") is the structural match, but the highly specific 'when' plus the 'what' implied by the skill name place it between anchors 2 and 3, so 3 is the best fit; it cannot be 4 since no 'what' statement exists.

3 / 5

Trigger Term Quality

"mode indicator", "boot tool selection", and "Esc-to-Select behaviour" are natural phrases a developer working in this codebase would actually say, giving good keyword coverage. It falls short of anchor 5 because the body covers several more trigger surfaces — toolbar/palette, Showcase mode, walk modes, welcome modal — whose natural terms are missing from the description.

4 / 5

Distinctiveness Conflict Risk

"Tiny World Builder" plus project-specific terms ("boot tool selection", "Esc-to-Select") form a clear niche with distinct triggers that virtually no other skill would match. This cleanly matches anchor 5 and is well above anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

jasonkneen/tiny-world-builder

Path

.codex/skills/tinyworld-tool-icons-and-modes/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.