CtrlK
BlogDocsLog inGet started
Tessl Logo

tinyworld-settings

Use when changing Tiny World Builder Settings modal tabs, panels, controls, rendering/world/material/crowd/AI settings, or settings accessibility.

72

Quality

87%

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

85%

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

A high-quality, project-specific guidance skill with concrete actionable constraints and an explicit validation checklist; its only real weakness is moderate verbosity in rationale clauses that could be trimmed.

Suggestions

Trim explanatory rationale inside rule bullets (e.g. the 'on a phone that pushes lower controls off-screen' clause) to the minimum needed to state the constraint, since Claude can infer the 'why' for many of these.

Convert the Validation section into a short numbered sequence with an explicit 'if a check fails, fix and re-run' feedback loop so the validation steps read as a loop rather than a flat checklist.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious project facts, but several rules carry explanatory rationale clauses (e.g. "Never let the card grow unbounded again — on a phone that pushes lower controls off-screen and they become unreachable") that could be tightened without losing the constraint, matching 'mostly efficient but could be tightened'.

2 / 3

Actionability

It gives concrete, executable guidance throughout — specific control IDs, the `selectSettingsTab(name)` contract, exact CSS values (`max-height: calc(100vh - 100px)`), ARIA attributes, file paths, and concrete validation commands (`npm test`, `npm run build`).

3 / 3

Workflow Clarity

A dedicated Validation section sequences the checks (inline syntax check, `npm test`, `npm run build`) followed by an explicit browser-check and responsive-check checklist, providing clear verification checkpoints rather than implicit ones.

3 / 3

Progressive Disclosure

It is a well-organized single SKILL.md with clearly headed sections (compatibility, structure, organization, validation); the only file references point at source files being modified, not nested skill references, so no progressive-disclosure split is needed.

3 / 3

Total

11

/

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, well-triggered description with explicit 'Use when' guidance and natural feature terms; its only weakness is relying on one action verb over an enumerated target list rather than multiple distinct actions.

DimensionReasoningScore

Specificity

The description names the domain and enumerates concrete targets ("tabs, panels, controls, rendering/world/material/crowd/AI settings, settings accessibility") but relies on a single action verb ("changing") rather than listing multiple distinct actions like extract/fill/merge, so it sits at the 'names domain and some actions' anchor rather than fully comprehensive.

2 / 3

Completeness

It opens with an explicit "Use when changing..." trigger (the 'when') and states the 'what' (modifying the Settings modal's tabs, panels, controls, and category settings), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

It surfaces natural terms a user would actually say when needing this skill — "Settings", "rendering", "world", "material", "crowd", "AI settings", and "settings accessibility" — giving good coverage of the feature vocabulary.

3 / 3

Distinctiveness Conflict Risk

The trigger is scoped to the very specific "Tiny World Builder Settings modal", a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.