CtrlK
BlogDocsLog inGet started
Tessl Logo

tinyworld-island-viewer

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

56

Quality

64%

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

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.

The body is a strong, dense instruction skill: concrete files, commands, cell kinds, and thresholds throughout, with a clear generation sequence and an explicit validation checklist. It loses a point mostly on conciseness (a few verbose rules) and progressive disclosure (everything inline with no detail files split out).

Suggestions

Tighten the longest rules (manor, quarry, weighted infill) into terse bullet sub-clauses to recover token budget.

Consider moving the detailed layer-stack and per-layer emission rules into a referenced reference file, leaving SKILL.md as the overview + invariants + validation.

Number the Validation checklist steps and add an explicit 'do not ship if any check fails' checkpoint to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The body is dense, rule-driven, and free of concept explanations Claude already knows, with every constraint tied to a specific file, kind, or threshold; a few rules (manor, quarry, infill) could be tightened, keeping it just below the lean-and-efficient anchor.

4 / 5

Actionability

Guidance is highly concrete — exact commands ('npm run stats:island-viewer -- --count 1000', 'npm test'), named files, precise cell kinds, and numeric thresholds (25% manor, 8x8) — giving mostly executable instruction with only minor gaps from being rule-based rather than code-based.

4 / 5

Workflow Clarity

A clear ordered sequential layer stack plus an explicit Validation checklist (npm test, build, stats, page-load checks) provide sequencing and checkpoints; because validation is present, the destructive/batch cap does not apply, though the rules are a flat list rather than a strict stepwise workflow.

4 / 5

Progressive Disclosure

Well-organized into a file inventory, Rules, and Validation sections with clear headers and one-level structure; no bundle files exist so all content is inline, but the sectioning keeps navigation easy with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

53%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, explicit 'Use when' trigger and a distinct, narrow niche, but it is trigger-heavy: it names the surfaces to change without stating concretely what the skill does, and its keywords are project-internal jargon rather than natural user phrases.

Suggestions

Lead with a concrete 'what' verb phrase (e.g., 'Edit and maintain the Island Viewer shell, routing, and graphics defaults') before the 'Use when' clause so both what and when are explicit.

Add natural-language synonyms a user might actually say (e.g., 'island viewer page', 'island routing', 'viewer graphics settings') alongside the technical terms.

Name the key files users reference (e.g., 'island-viewer.html') in the description to sharpen trigger matching.

DimensionReasoningScore

Specificity

Names three concrete trigger surfaces ('Island Viewer shell, sequential generated-island viewer routing, or viewer-scoped graphics defaults') but the only action verb is 'changing', so capabilities stay generic rather than comprehensive.

3 / 5

Completeness

The explicit 'Use when...' clause answers 'when' clearly, but 'what does this do' is only weakly implied through the trigger objects rather than stated, so it does not reach the both-what-and-when anchors.

3 / 5

Trigger Term Quality

Terms like 'Island Viewer shell', 'generated-island viewer routing', and 'graphics defaults' are relevant to a developer on this project but lean technical/jargon with no common synonyms or file extensions, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Scoped tightly to the first-class Island Viewer with specific trigger surfaces, giving it a clear niche with only minor overlap risk against the broader TinyWorld builder skills.

4 / 5

Total

13

/

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.

Validation15 / 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
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.