CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-island-viewer

Use when changing the first-class Island Viewer shell, sequential generated-island viewer routing, or viewer-scoped graphics defaults.

59

Quality

74%

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-island-viewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The content is an unusually concrete, project-grounded ruleset: exact file paths, layer ordering, cell kinds, thresholds, and runnable validation commands leave little ambiguity about what to do or how to verify it. Minor improvements are possible — tightening the longest rule bullets and adding error-recovery guidance for failed validation — but the skill is close to exemplary for an instruction-only skill.

DimensionReasoningScore

Conciseness

The body is a dense rule list of project-specific constraints Claude could not derive (file paths, layer order, kind values) with no padding of known concepts, but several long bullets (quarry, manor, infill) could be tightened, matching anchor 4 rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is fully concrete and executable: exact script paths (scripts/island-viewer-sequential-generator.js), run commands (npm run stats:island-viewer -- --count 1000), precise thresholds (25% manor chance, >3 Manhattan spacing), and exact cell kinds and schema values (v:4, kind: "bridge"), matching anchor 5.

5 / 5

Workflow Clarity

The generator layer stack is explicitly sequenced ('all grass, first house, corner towers, paths, ... final weighted infill') and a Validation section lists concrete commands and observable checks, but there is no feedback loop for what to do when validation fails, which holds it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body is well structured into a file map, Rules, and Validation sections with no external references needed (and none exist in the bundle), and the inline rules are cohesive; at ~95 dense lines it exceeds the simple-skill size where organization alone earns a 5, so it fits anchor 4.

4 / 5

Total

17

/

20

Passed

Description

56%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 has a strong, distinctive 'Use when' trigger clause with clear project-specific scope, but it is missing any statement of what the skill actually does, which caps completeness at 2 and limits specificity. Adding a brief capability clause before the trigger would resolve the main weakness.

Suggestions

Add a 'what' clause stating the skill's capabilities, e.g., 'Guides changes to the Island Viewer shell, its sequential island generator layer order, and viewer graphics defaults. Use when...' so completeness answers both what and when.

Include natural trigger variations users might say, such as the file names 'island-viewer.html' or terms like 'island generator' or 'viewer defaults', to broaden trigger-term coverage.

Name one or two concrete actions the skill covers (e.g., 'enforce sequential generator layering and schema-valid v:4 output') to raise specificity beyond a bare 'when' scope.

DimensionReasoningScore

Specificity

The description names the domain ('first-class Island Viewer shell, sequential generated-island viewer routing, or viewer-scoped graphics defaults') with three concrete change surfaces, but states no capability or action the skill performs beyond 'changing', so it matches anchor 3 rather than anchor 4's several specific actions.

3 / 5

Completeness

Only a 'Use when...' trigger clause is present; the description never says what the skill does (no capabilities, actions, or outcomes), which is exactly anchor 2 ('only when is present without what') rather than anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

Terms like 'Island Viewer', 'viewer routing', and 'graphics defaults' are the natural phrases a user of this repo would say, giving good keyword coverage, though common variations (e.g., file names like island-viewer.html, or synonyms like 'island generator') are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — scoped to the Island Viewer shell, its sequential viewer routing, and viewer-scoped graphics defaults — so trigger terms are distinct and conflict risk with other skills is minimal, matching anchor 5.

5 / 5

Total

14

/

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: 9 missing

Warning

Total

15

/

16

Passed

Repository

jasonkneen/tiny-world-builder

Path

.codex/skills/tinyworld-island-viewer/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.