CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tinyworld-auto-batching

Use when changing Tiny World Builder Auto palette behavior, model inference, suggestions, or provider/model/API-key logic.

61

Quality

77%

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-auto-batching/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is a lean, high-signal design brief: concrete function and constant names, an unambiguous batched-inference workflow with error handling, and an explicit validation test. The only weakness is that implementation details like the suggestion schema's shape and queue-spending logic are assumed rather than shown, which is acceptable for this codebase-internal skill but leaves minor actionability gaps.

DimensionReasoningScore

Conciseness

Every line is a directive with zero padding ('Auto should not call the model on every placement', 'Do not add a backend or new dependency'); no concept Claude already knows is explained, so every token earns its place.

5 / 5

Actionability

Concrete identifiers appear throughout (snapshotCells(), AUTO_SUGGESTIONS_SCHEMA, autoSuggestionQueue, AUTO_REFRESH_EVERY, normalizeAutoAction, adaptAutoSuggestionToCell(action, x, z)) plus a testable validation recipe ('verify two Auto suggestions only call the stub once'), but minor gaps remain such as the schema's shape and how the queue is spent.

4 / 5

Workflow Clarity

The intended model is a clear ordered sequence (capture snapshot, request batch, spend locally, refresh after N placements or on empty), with an explicit error branch ('If no API key exists, open the Generate modal with the Auto key message') and an explicit validation section with pass criteria.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references; its three well-labeled sections (intended model, guardrails, validation) satisfy the rubric's simple-skill condition for a top score.

5 / 5

Total

19

/

20

Passed

Description

51%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 a highly specific, low-conflict trigger clause, but it is entirely a 'when' statement with no 'what': a reader cannot tell what the skill actually does (e.g., 'implements batched model suggestions for Auto placements'). Domain vocabulary is strong, yet the missing capability statement and absent action verbs keep specificity and completeness low.

Suggestions

State what the skill does before the trigger clause, e.g., 'Implements batched model-suggested tile placements for Tiny World Builder Auto. Use when changing...'

Add a concrete action verb or capability list so specificity moves beyond the generic 'changing', e.g., 'implement', 'debug', or 'refactor Auto batching'.

Include natural synonym terms users might say, such as 'AI suggestions', 'batching', or 'Auto tiles', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names several concrete domains ('Auto palette behavior, model inference, suggestions, or provider/model/API-key logic') but the only action stated is the generic 'changing' — no concrete capability of the skill itself is described, matching the anchor for naming a domain with minimal or generic actions.

2 / 5

Completeness

The 'when' is explicit and specific ('Use when changing Tiny World Builder Auto palette behavior...'), but the 'what' is entirely unstated — the description never says what the skill does, exactly matching the anchor for only 'when' being present without 'what'.

2 / 5

Trigger Term Quality

Terms like 'Auto palette behavior', 'model inference', 'suggestions', and 'provider/model/API-key' are natural phrases a developer on this project would say, but common variations such as 'generate', 'batching', 'AI', or 'tiles' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Tiny World Builder Auto' is a highly specific project-scoped niche with distinct trigger domains, making conflict with other skills minimal.

5 / 5

Total

13

/

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-auto-batching/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.