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 — Codex does the translating directly, using the established glossary for consistency.

74

Quality

91%

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

88%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 tightly written, highly actionable workflow skill with explicit validation feedback loops and concrete commands/paths throughout. Organization is clear and self-contained, with only minor prose trim opportunities.

Suggestions

Tighten the intro paragraph and 'Scope' section to bullet-only form to reclaim tokens while keeping the same information.

Consider moving the glossary table to a referenced file if it grows, keeping SKILL.md as a lean overview pointer.

DimensionReasoningScore

Conciseness

Assumes Claude's competence (no preamble on what i18n is) and uses terse, high-signal prose with a data-dense glossary table, though the intro and scope sections carry a little prose that could be trimmed further.

4 / 5

Actionability

Provides exact file paths, executable commands (npm run i18n:check / i18n:report / dev), concrete attribute and call patterns (data-i18n-*, window.t('key'), tx('prefix.' + item.id, item.label)), and a copy-paste-ready new-language checklist.

5 / 5

Workflow Clarity

The main loop is a numbered six-step sequence with explicit validation checkpoints (i18n:report to find gaps, i18n:check until it passes, real-app verification with ?lang=), and a feedback loop; the new-language flow repeats the same validated pattern.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a single one-level-deep reference ("Read docs/i18n.md first"), and the inline glossary is reasonably kept in-file; no bundle files exist to verify deeper referencing against.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, third-person description that conveys concrete actions, four target languages, and multiple explicit trigger conditions tied to a specific product. It is concise and avoids fluff while remaining highly distinctive.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions ("Add, translate, or audit TinyWorld UI strings") across four named languages, but coverage is bounded to a single product surface rather than a broad comprehensive action set.

4 / 5

Completeness

Explicitly answers both what (add/translate/audit UI strings across four locales) and when, with concrete trigger clauses introduced by "Use when…".

5 / 5

Trigger Term Quality

Includes several natural trigger phrases users would actually say ("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"), covering synonyms and the concrete checker command.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to TinyWorld gameplay i18n with product-specific triggers (the i18n:check command, locale-leak symptom), making conflict with other skills minimal.

5 / 5

Total

19

/

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.