CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-opacity-torch

Use when changing ghost boards, multiplayer preview boards, panning, ghost visibility, jigsaw reveal, or any visibility behavior around the active Tiny World board.

Quality

70%

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-opacity-torch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-organized, information-dense behavior specification: it names real functions, files, and constants, and closes with a concrete validation checklist. The main gaps are minor redundancy across sections, a dangling cross-reference, and the absence of a small executable snippet for the core reveal function.

Suggestions

Fix or remove the dangling reference: the body says "see `buildHomeBorder()` in the *home board border* section", but no such section or bundle file exists.

Collapse the three-fold repetition of the home-board-never-fades rule (Mental model, Reveal rules, Validation) into one authoritative statement to tighten conciseness.

Add a short reference implementation of `revealOpacityFor(root)` to make the stickiness mechanism copy-paste concrete rather than described.

DimensionReasoningScore

Conciseness

The body is dense with project-specific facts Claude could not know (function names, constants like `dt * 20` and `0.6 + 0.4 * currentOpacity`, file paths) and does not pad with general knowledge. It stops short of anchor 5 because the 'Mental model' bullets partially repeat what the 'Reveal rules' and 'Validation' sections restate (e.g., home board never fades appears three times), which could be tightened.

4 / 5

Actionability

Concrete, executable guidance throughout: exact function names and call relationships ("`updateGhostRenderBubble`, `updateHomeBoardFade` call this instead of `opacityAtWorldPosition` directly"), precise formulas, and file-level pointers (`02-cameras-lighting.js`, `30-ui-boot-wiring.js`). Per the code_vs_instruction note, absence of code is acceptable for an instruction-only skill, but a short snippet of `revealOpacityFor(root)` would close the gap to anchor 5's copy-paste-ready level.

4 / 5

Workflow Clarity

This is a behavior-rules skill rather than a pipeline, and it supplies an explicit 'Validation' checklist with concrete checks ("`pickTile()` over a Preview board should still return `null`", grid sizes 8/12/16/20) plus ordering rules (landing priority, short-circuit paths). It is not 5 because there is no sequenced workflow with error-recovery feedback loops, and the landscape-mode rules are stated without validation steps tying them back to the checklist.

4 / 5

Progressive Disclosure

A single ~100-line file with clear sections (Mental model, Reveal rules, Interaction rules, Validation, Landscape mode) and no nested references — appropriate for a focused behavior spec. It loses a point because the body points to a "*home board border* section" via `buildHomeBorder()` that exists neither in this file nor in any bundle file, a dangling reference that hurts navigation.

4 / 5

Total

16

/

20

Passed

Description

51%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 strong, distinctive trigger clause with excellent project-specific keywords, but it is only half a description: it says when to use the skill without saying what the skill does. Adding a one-clause capability statement would move completeness and specificity up substantially.

Suggestions

Add a 'what' clause stating the skill's concrete capabilities, e.g. 'Implements sticky one-by-one Preview cell reveal with an always-full-opacity home board, replacing the old opacity torch. Use when changing ghost boards, ...'

Include a few more natural trigger synonyms users might say, such as 'opacity', 'fade', or 'preview reveal', in the 'Use when' clause.

Briefly name the key mechanisms (opacityAtWorldPosition / revealOpacityFor stickiness, unrestricted panning) so the description previews the skill's actual scope.

DimensionReasoningScore

Specificity

The description names a specific domain ("visibility behavior around the active Tiny World board") and lists concrete trigger topics ("ghost boards, multiplayer preview boards, panning, ghost visibility, jigsaw reveal") but describes zero capabilities or actions the skill performs. This matches anchor 2 ('names the domain but actions are minimal or generic'); it does not reach anchor 3, which requires 1-2 concrete actions, and is above anchor 1 because the domain language is concrete, not vague.

2 / 5

Completeness

The 'when' is explicit and rich ("Use when changing ghost boards... jigsaw reveal"), but the 'what' — what the skill actually does or contains — is entirely absent. This is precisely anchor 2 ('only when is present without what'); it cannot be 3 because a clear 'what' is missing, and it is not 1 because the 'when' is concrete rather than extremely vague.

2 / 5

Trigger Term Quality

Phrases like "ghost boards", "multiplayer preview boards", "panning", "ghost visibility", and "jigsaw reveal" are exactly what a developer on this project would say, and "any visibility behavior" acts as a catch-all. A few natural synonyms are missing (e.g., opacity, fade, reveal settings), keeping it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Highly project-specific terms ("Tiny World board", "ghost boards", "jigsaw reveal") establish a clear niche with distinct triggers and minimal risk of firing for unrelated skills. No neighboring anchor fits better — anchor 4's 'minor overlap risk' is not present since no generic vocabulary is used.

5 / 5

Total

13

/

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-opacity-torch/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.