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.

80

Quality

100%

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

100%

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

A dense but purposeful workflow: concrete file paths, commands, and code patterns with a clearly sequenced, validation-checked loop for both editing strings and adding languages. The one external reference is one level deep and clearly signaled.

DimensionReasoningScore

Conciseness

No padding or explanation of concepts Claude already knows; every section (loop, scope, style, glossary, new-language steps) is actionable reference material that earns its tokens.

3 / 3

Actionability

Provides exact file paths, commands (`npm run i18n:check`, `i18n:report`, `dev`), attributes (`data-i18n-title`, etc.), and copy-paste code patterns (`window.t('key')`, `tx('prefix.' + item.id, item.label)`, `if (window.TWI18N)`).

3 / 3

Workflow Clarity

The six-step "loop" is explicitly sequenced with validation checkpoints — report missing keys, run `i18n:check` until it passes, then verify in the real app via `?lang=` — including a feedback loop for re-checking.

3 / 3

Progressive Disclosure

A single well-signaled one-level reference (`Read docs/i18n.md first if you need the architecture`) with no nested references, organized into clearly headed sections.

3 / 3

Total

12

/

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, third-person description that states concrete capabilities and gives multiple explicit, natural trigger conditions. It clearly distinguishes itself via project-specific tooling and is unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Add, translate, or audit TinyWorld UI strings across English/French/Chinese/Spanish" — naming three distinct operations and the four target locales.

3 / 3

Completeness

Explicitly answers both what (add/translate/audit UI strings across four locales) and when (an explicit "Use when…" clause with four concrete triggers).

3 / 3

Trigger Term Quality

Covers natural phrases a user would say: "adding user-facing gameplay text", "`npm run i18n:check` fails", "a string shows up in English in a non-English locale", and "adding a new language".

3 / 3

Distinctiveness Conflict Risk

Scoped to "TinyWorld UI strings" and names the project-specific `npm run i18n:check`, giving it a clear niche unlikely to trigger 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.