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.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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 highly actionable, concise, well-sequenced ruleset with concrete identifiers, runnable commands, and an explicit validation checklist. Its only notable weakness is progressive disclosure: everything is inlined in a single document with no separate reference files to split the dense ruleset.

DimensionReasoningScore

Conciseness

The body is dense, project-specific operational guidance with no concept-teaching fluff (no "what a generator is"), references concrete identifiers directly, and every rule earns its place, matching anchor 3 over the 'could be tightened' anchor 2.

3 / 3

Actionability

It provides fully concrete, executable guidance: exact file paths, function names (TinyWorldIslandGenerator.generate(...), .profile(...)), schema fields (v:4, kind:"bridge", buildingType:"manor"), persistence keys, and runnable commands (npm test, npm run build, npm run stats:island-viewer -- --count 1000), matching anchor 3.

3 / 3

Workflow Clarity

A clear ordered sequence is given ("The sequential layer stack is: all grass, first house, corner towers, paths, ... final weighted infill") plus an explicit Validation section with concrete checkpoints, satisfying anchor 3; validation is present so the batch-operation cap at 2 does not apply.

3 / 3

Progressive Disclosure

There are no bundle reference files (references/, scripts/, assets/ are empty) and all ~85 lines of dense rules live inline in one SKILL.md; sections are well-organized with a top file inventory, but content that could be split into reference files is kept inline, matching anchor 2 rather than the one-level-deep reference structure of anchor 3.

2 / 3

Total

11

/

12

Passed

Description

75%

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 tight, well-targeted trigger clause tied to a specific named surface, with strong distinctiveness and an explicit 'Use when' trigger. It is held back from a perfect score by single-verb action coverage and jargon-heavy trigger terms a user would not naturally voice.

Suggestions

Lead with a distinct action clause naming what the skill does (e.g. "Guides changes to the Island Viewer shell, routing, and graphics defaults."), then append the 'Use when' trigger so 'what' and 'when' are clearly separated.

Soften internal jargon ("first-class", "sequential generated-island", "viewer-scoped") toward terms a user would naturally say, e.g. "Island Viewer", "island routing", "viewer graphics settings".

Use more than one concrete verb (e.g. "edit, route, configure") to lift specificity from naming targets to naming distinct actions.

DimensionReasoningScore

Specificity

It names a concrete domain and three specific subsystems ("Island Viewer shell, sequential generated-island viewer routing, or viewer-scoped graphics defaults"), but a single generic verb ("changing") covers all three rather than listing multiple distinct actions, matching anchor 2 over anchor 3.

2 / 3

Completeness

An explicit "Use when changing..." clause provides clear trigger guidance, and the same clause names the concrete capabilities the skill governs, answering both what and when; the judging guideline only caps at 2 when a 'Use when' clause is missing, which is not the case here.

3 / 3

Trigger Term Quality

Relevant keywords exist ("Island Viewer", "shell", "routing", "graphics defaults") but they are wrapped in heavy internal jargon ("first-class", "sequential generated-island", "viewer-scoped") a user would not naturally say, so it sits at anchor 2 rather than 1 (natural keywords present) or 3 (clean common variations).

2 / 3

Distinctiveness Conflict Risk

It targets a named, narrowly-scoped internal product surface (the Island Viewer shell/routing/graphics defaults), giving it a clear niche that is very unlikely to conflict with other skills, matching anchor 3.

3 / 3

Total

10

/

12

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.