tinyworld-single-file

Use when editing the Tiny World Builder repo, especially tiny-world-builder.html, to preserve the static classic-script Three.js r185 app structure and local edit/reload workflow.

Quality

81%

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

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable guardrails skill with concrete commands and clean sectioning, plus well-signaled pointers to related skills. It loses points for two verbose rationale-heavy bullets and for presenting validation as a rule list rather than an explicit sequenced validate->fix->retry workflow.

Suggestions

Tighten the random-island-preview and Cluso bullets by moving rationale (e.g. 'Owner-approved override of the prior rule') into a separate note so the core rule stays one line.

Convert the Validation section into an explicit numbered validate->fix->retry loop (run npm test -> if failures, fix -> re-run -> only then judge runtime) to lift workflow_clarity to 3.

Consider extracting the long Cluso local-dev exception into a dedicated reference file so the main rules stay lean.

Dimension	Reasoning	Score
Conciseness	Most lines are dense, specific rules that assume Claude's competence, but the random-island-preview and Cluso bullets are padded with parenthetical rationale and justification ('Owner-approved override of the prior rule...') that could be tightened, matching anchor 2 rather than the lean anchor 3.	2 / 3
Actionability	It gives concrete, executable guidance throughout: 'npm run vendor:three', 'npm run build', 'npm test', a copy-paste perl/node parser check, the exact check.js regex, and a localhost validation URL, matching the copy-paste-ready anchor 3.	3 / 3
Workflow Clarity	A Validation section and a build-before-judge sequence exist, but the body is organized as a rule list rather than a numbered workflow with explicit validate->fix->retry feedback loops; checkpoints are present but implicit, so it caps at anchor 2 per the feedback-loops scoring note.	2 / 3
Progressive Disclosure	No bundle files are needed and the body is organized into clear sections (Core rules, Validation, Inline script gotcha, Related durable systems) with well-signaled one-level-deep references to sibling skills, matching the well-organized anchor 3 for a self-contained skill.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 tightly scoped, third-person description with an explicit 'Use when...' trigger that clearly states both what to preserve and when to use the skill. The only weakness is that the stated actions are abstract ('editing', 'preserve') rather than a list of concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Tiny World Builder repo, especially tiny-world-builder.html') and actions ('editing', 'preserve the static classic-script Three.js r185 app structure and local edit/reload workflow'), but the verbs are abstract rather than a list of multiple concrete actions, so it matches anchor 2 rather than 3.	2 / 3
Completeness	It explicitly answers both 'what' ('preserve the static classic-script Three.js r185 app structure and local edit/reload workflow') and 'when' with an explicit 'Use when editing the Tiny World Builder repo...' trigger clause, matching anchor 3.	3 / 3
Trigger Term Quality	The 'Use when editing the Tiny World Builder repo, especially tiny-world-builder.html' clause covers the natural terms a user would say when needing this skill, plus 'edit/reload workflow', giving good coverage for the niche. It is not anchor 2 because the trigger phrasing is explicit and uses the repo's own natural vocabulary.	3 / 3
Distinctiveness Conflict Risk	The trigger is scoped to a single named repo and file, creating a clear niche that is unlikely to fire for unrelated skills; it is well above anchor 2 ('could still overlap with similar skills').	3 / 3
	Total	11 / 12 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-single-file/SKILL.md
Commit: f21f84b

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.