CtrlK
BlogDocsLog inGet started
Tessl Logo

tinyworld-i18n

Add, translate, or audit TinyWorld UI strings across English/French/Chinese/Spanish. Use when adding user-facing gameplay text, when `npm run i18n:check` fails, when a string shows up in English in a non-English locale, or when adding a new language. No translation API — Claude does the translating directly, using the established glossary for consistency.

78

Quality

98%

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

96%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 highly actionable, well-sequenced i18n workflow with concrete paths, commands, validation checkpoints, and a feedback loop. The only minor gap is progressive disclosure: the glossary table could optionally live in a bundled reference file to keep the overview leaner.

Suggestions

Consider moving the Glossary table into a bundled references/ file (e.g. references/glossary.md) and linking to it, which would tighten the overview and exercise progressive disclosure.

If docs/i18n.md is part of the repo, note that it is an external (non-bundled) doc so it is clear it is not shipped with the skill.

DimensionReasoningScore

Conciseness

Lean and dense throughout: concrete file paths, commands, and a glossary table with no padding or explanations of concepts Claude already knows; every section earns its tokens.

5 / 5

Actionability

Fully executable guidance with exact paths (engine/i18n/{en,fr,es,zh}.js, engine/world/19-tools-toolbar.js), commands (npm run i18n:check/i18n:report/dev), attributes (data-i18n-title), and copy-paste patterns (tx('prefix.' + item.id, item.label), if (window.TWI18N)).

5 / 5

Workflow Clarity

The 6-step loop is clearly sequenced with explicit validation checkpoints (i18n:report to find gaps, i18n:check 'until it passes', real-app verification with ?lang=fr) and a feedback loop; the new-language flow repeats this pattern with a final check.

5 / 5

Progressive Disclosure

Well-organized into clear sections (workflow, scope, style, glossary, new language) with one clearly signaled optional reference (docs/i18n.md); no bundle files exist, and the inline glossary table is reasonable reference material, but the ~100-line body is slightly above the simple-skill threshold that would warrant a 5.

4 / 5

Total

19

/

20

Passed

Description

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

An exemplary description: concrete actions, four explicit 'Use when...' triggers, a clear what/when pair, and a tightly scoped niche that avoids conflict. It also surfaces a key constraint (no translation API) without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Add, translate, or audit TinyWorld UI strings') across four named locales, giving comprehensive coverage of the skill's capabilities rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both what (add/translate/audit UI strings, Claude translates directly via glossary) and when (four concrete trigger clauses starting with 'Use when...').

5 / 5

Trigger Term Quality

Four distinct natural trigger phrases ('adding user-facing gameplay text', 'npm run i18n:check fails', 'a string shows up in English in a non-English locale', 'adding a new language') map directly to what a user would say or observe.

5 / 5

Distinctiveness Conflict Risk

Scoped to a named project ('TinyWorld UI strings') with a distinct niche (i18n for gameplay text) and project-specific triggers, minimizing overlap with other skills.

5 / 5

Total

20

/

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.

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.