CtrlK
BlogDocsLog inGet started
Tessl Logo

tinyworld-visual-qa

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

77

Quality

96%

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.

A highly actionable, token-efficient QA runbook with concrete commands, URLs, and probes plus a clear verification checklist. Its main weakness is progressive disclosure: a 40+ bullet monolithic body with no references to offload detail.

Suggestions

Move the long per-feature acceptance criteria into a references/ file (e.g. CHECKS.md) and keep SKILL.md as a concise overview with setup commands and a one-level-deep link, improving progressive_disclosure.

Add a short validation/feedback note for setup (e.g. 'confirm the app loads on :8888 before running Checks') to make the workflow sequence explicit rather than implied.

DimensionReasoningScore

Conciseness

Dense, specific acceptance criteria with no padding or explanation of concepts Claude already knows; every bullet earns its place as a concrete QA check.

3 / 3

Actionability

Provides copy-paste-ready setup commands, exact proof URLs with query params, and executable JS browser probes (pickTile, getComputedStyle) — fully actionable.

3 / 3

Workflow Clarity

Setup is sequenced (./publish.sh then netlify dev) and the Checks list functions as explicit verification checkpoints for a single-purpose QA task, which the rubric allows to score 3.

3 / 3

Progressive Disclosure

Organized into setup, checks, and probes sections, but it is a long monolithic checklist with no external references or detail pushed to separate files, so it could be better split.

2 / 3

Total

11

/

12

Passed

Description

100%

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 tight, third-person description with an explicit 'Use when' trigger and a concrete list of visual-QA targets scoped to a single named project. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names the domain (Tiny World Builder UI) and lists multiple concrete test targets — 'camera, ghost opacity, buildings, tile geometry, or frontend polish' — which is comparable to listing multiple specific actions.

3 / 3

Completeness

Explicit 'Use when' trigger answers the when, and 'visually testing Tiny World Builder UI, camera, ghost opacity...' answers the what, satisfying both halves.

3 / 3

Trigger Term Quality

Natural terms a project user would actually say ('visually testing', 'Tiny World Builder UI', 'camera', 'ghost opacity', 'frontend polish', 'browser') are well covered.

3 / 3

Distinctiveness Conflict Risk

Tied to a specific named project (Tiny World Builder) with niche triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.