CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-settings

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

Quality

82%

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

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

A lean, highly actionable constraint skill: nearly every line carries project knowledge Claude could not infer (IDs, ARIA wiring, CSS caps, file paths) and validation is explicit. The small gaps are a duplicated preserve-wiring bullet, an unnamed 'inline script syntax check' command, and no ordered change sequence.

Suggestions

Replace 'Run the inline script syntax check' with the exact command so the validation step is copy-paste executable.

Deduplicate the 'Preserve the existing data-settings-tab / data-settings-panel wiring, ARIA roles, keyboard tab navigation, and search-count chips' bullet, which repeats points already made in the compatibility list.

Consider a brief ordered checklist (change -> validate -> browser-check) at the top so the workflow sequence is explicit rather than implied by the Validation section.

DimensionReasoningScore

Conciseness

The body is dense with project-specific constraints (exact IDs, CSS values, file paths) and explains nothing Claude already knows; the only fat is the 'Preserve the existing data-settings-tab / data-settings-panel wiring, ARIA roles, keyboard tab navigation' bullet, which restates earlier bullets.

4 / 5

Actionability

Guidance is highly concrete — exact control IDs, the selectSettingsTab(name) contract, exact CSS and file paths, and copy-paste commands like 'npm test' and 'npm run build' — but 'Run the inline script syntax check' never names the actual command, leaving a minor gap.

4 / 5

Workflow Clarity

The Validation section provides explicit checkpoints (syntax check, npm test, npm run build, browser behaviors, responsive checks) and regression guardrails, but the change workflow itself is unordered and the syntax-check step is unspecified.

4 / 5

Progressive Disclosure

No bundle files exist or are needed; the single-file skill is cleanly sectioned (compatibility, Structure rules, Organization guidance, Validation) with all project-specific constraints appropriately inline and no dangling references.

5 / 5

Total

17

/

20

Passed

Description

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

A strong trigger-focused description with an explicit 'Use when' clause, concrete enumerated targets, and a distinctive product-specific scope. Its main weakness is that the 'what this skill does' half is only implicit in the trigger list, and it lacks synonym variants like 'preferences'.

Suggestions

Lead with a short third-person 'what' clause (e.g., 'Guides changes to the Tiny World Builder Settings modal...') before the 'Use when' trigger list so both halves of completeness are explicit.

Add one or two natural synonyms users might say, such as 'settings preferences' or 'options', to broaden trigger-term coverage without adding padding.

DimensionReasoningScore

Specificity

Enumerates several concrete targets ('tabs, panels, controls, rendering/world/material/crowd/AI settings, or settings accessibility'), giving clear scope, though it lists areas to change rather than actions the skill performs.

4 / 5

Completeness

The 'when' is explicit and detailed ('Use when changing...'), but the 'what' is only implied by the enumerated change targets rather than stated as a capability.

4 / 5

Trigger Term Quality

Contains natural terms users would say — 'Settings', 'tabs', 'panels', 'controls', 'rendering', 'accessibility', plus the product name 'Tiny World Builder' — but misses common synonyms such as 'preferences' or 'options'.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to the Tiny World Builder Settings modal with product-specific tab names, forming a clear niche with minimal risk of triggering for unrelated skills.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jasonkneen/tiny-world-builder

Path

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