CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-visual-qa

Use when visually testing Tiny World Builder UI, camera, ghost opacity, buildings, tile geometry, or frontend polish in the browser.

Quality

75%

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-visual-qa/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 exemplary project-specific QA checklist: dense, executable, and free of filler, with concrete launch commands, deterministic proof URLs, and browser probes. Its main gaps are the absence of any failure-handling loop and a handful of oversized checklist entries that would benefit from being split into their own sections.

DimensionReasoningScore

Conciseness

The body is a lean checklist with zero padding: it never explains concepts Claude already knows, and every line is a project-specific acceptance criterion ('Ghost boards do not become editable', 'Tilt-shift overlays have pointer-events: none'). It assumes competence and every token earns its place, matching anchor 5; it is not anchor 4 because there is no over-explanation to trim.

5 / 5

Actionability

Mostly executable guidance: copy-paste launch commands ('./publish.sh', the full 'npx netlify dev' invocation), deterministic proof URLs with exact query strings, and runnable browser probes ('pickTile(window.innerWidth / 2, ...)'). It falls short of anchor 5 because many checks are stated as visual acceptance criteria ('should read as separate surfaces') without a concrete way to verify them programmatically, leaving minor gaps.

4 / 5

Workflow Clarity

There is a clear launch sequence for the two routes (direct localhost route when available; build then Netlify dev on 8888 for Worlds/API QA) and the skill is itself a validation checklist, which serves as the checkpoint layer. It sits at anchor 4 rather than 5 because there is no guidance on what to do when a check fails (no fix-and-reverify loop), and the launch order is implied rather than an explicitly numbered sequence.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are referenced, so the skill is self-contained with well-organized sections (intro/routes, 'Checks:', 'Useful browser probes'). This is good structure matching anchor 4; it misses anchor 5 because a few extremely long check items (e.g. the multi-sentence planet-underlay check and the blast-shield check) read as inlined sub-guides that would be cleaner as separate short sections or reference files.

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 excellent trigger specificity for this one project and near-zero conflict risk, but it is only half a description: it says when to use the skill without saying what the skill does. Adding a leading capability statement (e.g. what the QA procedure covers and produces) would raise completeness substantially.

Suggestions

Add a 'what' clause before the 'Use when' clause, e.g. 'Runs the Tiny World Builder app and walks a visual QA checklist covering UI, camera, buildings, and rendering polish.'

Broaden trigger coverage with natural synonyms users might say, such as 'visual regression', 'screenshot check', or 'UI polish pass'.

Keep the enumerated trigger subjects (camera, ghost opacity, tile geometry) — they are the description's strongest asset for correct skill matching.

DimensionReasoningScore

Specificity

The description names a specific domain ('Tiny World Builder UI') and several concrete subjects ('camera, ghost opacity, buildings, tile geometry'), but the only action stated is the generic 'visually testing' — it reads as a domain enumeration rather than a list of capabilities. It sits above anchor 2 (which names only a domain with generic action) because the enumerated check targets are concrete, but below anchor 4 because no distinct actions or coverage of what the skill actually does are listed.

3 / 5

Completeness

The description is entirely a 'when' clause ('Use when visually testing...') with no 'what' — it never states what the skill does (e.g. run the app, walk a visual checklist, probe the browser). This matches anchor 2 ('only when is present without what', example: 'Use when working with documents'); it is not anchor 3 because there is no clear 'what' at all, even though the 'when' itself is specific.

2 / 5

Trigger Term Quality

Phrases like 'visually testing', 'camera', 'ghost opacity', 'buildings', 'tile geometry', 'frontend polish', and 'in the browser' are natural terms a user on this project would say when they need visual QA. It falls short of anchor 5 because it lacks synonyms or variations for the testing/QA activity itself (e.g. 'screenshot', 'visual regression', 'polish pass') that users might also use.

4 / 5

Distinctiveness Conflict Risk

Triggers are anchored to a unique project name ('Tiny World Builder') and niche artifacts ('ghost opacity', 'tile geometry'), giving it a clear niche with minimal conflict risk against other skills. It clearly matches anchor 5 and is not merely 'mostly distinct' as in anchor 4.

5 / 5

Total

14

/

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-visual-qa/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.