tinyworld-block-button-style

Use when styling any tool/block button, palette tile, icon chip, or new clickable square in Tiny World Builder. The locked-in "block" aesthetic — a raised square with a dark category-colored outline, an inner white line, and a white-bodied glyph outlined in the same dark color. Apply this whenever a new icon button/tile is added so the UI stays consistent.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%

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

Highly actionable and token-efficient reference material with concrete code and named integration points. Its weaknesses are structural: the application guidance is a non-sequenced bullet list and the single-file layout doesn't progressively disclose its long per-component section.

Suggestions

Convert 'Applying it to a new button/tile' into an ordered, numbered workflow (assign data-pos-type → wire through posTypeForTool/buildToolButton → handle any special-case component → verify in browser), and promote the pixel-sampling check out of 'Gotchas' into an explicit validation checkpoint.

Split the long per-component application rules (~65 lines covering radial menus, appbar, token corner, world pill, dark-mode overrides) into a separate reference file such as COMPONENTS.md, and keep SKILL.md as a concise overview that links to it.

In the main workflow, state the expected verification outcome explicitly as a checkpoint (e.g. 'primary block reads dark border 30,66,138 → white line ~250 → category tint') so a new button can be confirmed correct before moving on.

Dimension	Reasoning	Score
Conciseness	The body is dense with project-tribal knowledge (exact selectors, file names, color codes, inheritance gotchas) and never explains CSS concepts Claude already knows; every line earns its place.	3 / 3
Actionability	It provides copy-paste-ready CSS with exact values (border: 1.5px solid #1e428a, full box-shadow stack), a category color table, and named functions/selectors (posTypeForTool(), buildToolButton(tool, { flyout: true }), .tool[data-pos-type]).	3 / 3
Workflow Clarity	The core recipe (assign data-pos-type → existing rules paint it) is clear and a concrete browser-pixel verification step exists, but the multi-component application guidance is a flat non-sequenced bullet list and the verification check is tucked under 'Gotchas' rather than presented as a workflow checkpoint.	2 / 3
Progressive Disclosure	Sections are well organized, but the skill is a monolithic 138-line single file with no reference files; the ~65-line 'Applying it to a new button/tile' section of per-component rules is content that could be split into a one-level-deep reference.	2 / 3
	Total	10 / 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 strong, specific description with explicit triggers, concrete capabilities, and a clear distinct niche. It cleanly answers both what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete styling targets — 'tool/block button, palette tile, icon chip, or new clickable square' — and spells out the exact visual recipe (raised square, dark category-colored outline, inner white line, white-bodied outlined glyph).	3 / 3
Completeness	It answers both what (the locked 'block' aesthetic and its three ingredients) and when, with explicit 'Use when…' and 'Apply this whenever…' trigger clauses.	3 / 3
Trigger Term Quality	Natural terms a Tiny World contributor would say are well covered: 'styling', 'button', 'palette tile', 'icon chip', 'new icon button/tile', 'clickable square'.	3 / 3
Distinctiveness Conflict Risk	The niche is tightly scoped to 'Tiny World builder' block-button styling, with domain-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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-block-button-style/SKILL.md
Commit: 039a20a

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.