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

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/tinyworld-opacity-torch/SKILL.md

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-structured, information-dense spec that names concrete functions and files and includes an explicit validation checklist, suited to an instruction-only skill. Minor tightening and an explicit fix-retry loop around validation would push it higher.

Suggestions

Add an explicit 'if a validation check fails, fix the offending function and re-run the check' loop after the Validation section to complete the feedback loop.

Trim decorative phrasing ('breadcrumb trail behind the user', 'for a snappy snap-in') to lift conciseness toward the lean anchor.

Consider extracting the Continuous Landscape Mode section into a referenced file if it grows, to keep the main body a focused overview.

Dimension	Reasoning	Score
Conciseness	The body is dense with project-specific facts (function names, opacity math, file paths) and assumes Claude's competence without explaining basic concepts; only minor flourishes like 'breadcrumb trail' and 'snappy snap-in' could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It points to concrete, named hooks (opacityAtWorldPosition, revealOpacityFor, updateHomeBoardFade, 02-cameras-lighting.js, 30-ui-boot-wiring.js) and specifies exact behaviors to enforce, which is actionable for an instruction-only skill even without copy-paste code.	4 / 5
Workflow Clarity	A dedicated Validation section provides explicit, checkable assertions (home board never fades, pickTile returns null over Preview, outline visible at 8/12/16/20), giving clear checkpoints; it lacks an explicit validate-fix-retry loop, capping it just below 5.	4 / 5
Progressive Disclosure	The skill is self-contained with well-organized sections (Mental model, Reveal rules, Interaction rules, Validation, Landscape Mode) and no nested references; with no bundle files present, structure is good though the Landscape Mode section is a candidate for separation.	4 / 5
	Total	16 / 20 Passed

Description

73%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 strong, trigger-rich description with excellent distinctiveness, though it leans on a single generic action verb and leaves the skill's actual capability implied rather than stated. It would benefit from a brief explicit statement of what the skill does.

Suggestions

Lead with an explicit 'what' clause (e.g., 'Governs the opacity/reveal system for Tiny World boards') before the 'Use when' trigger list so the capability is stated, not implied.

Replace the single generic verb 'changing' with a few distinct concrete actions (e.g., 'adjusts reveal stickiness, configures preview pan behavior, toggles ghost visibility') to lift specificity.

Add common synonyms or the relevant source filenames to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names several concrete domain areas ('ghost boards, multiplayer preview boards, panning, ghost visibility, jigsaw reveal') but uses only the generic verb 'changing' rather than enumerating distinct concrete actions, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	It provides an explicit and specific 'Use when...' clause covering multiple triggers, but the 'what does this do' is only implied through the trigger list rather than stated outright, landing just above the midpoint between anchor 3 and 5.	4 / 5
Trigger Term Quality	It includes a good spread of natural project terms a developer would say ('ghost boards', 'panning', 'jigsaw reveal', 'Tiny World board'), though it lacks synonyms or file extensions that would push it to the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The description targets a clear, narrow niche (Tiny World board visibility behaviors) with distinct, project-specific triggers, giving it minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 6a9a551

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.