CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

localize

Localization pipeline — find hardcoded strings, extract string tables, cultural review, VO, RTL, enforce string freeze.

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 ./.claude/skills/localize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually rigorous process skill: every mode has concrete paths, prompts, output templates, and validation logic, and the workflow ordering, freeze enforcement, and verdict precedence are exemplary. Its weaknesses are structural — a monolithic 460-line file with zero progressive disclosure — plus scattered over-explanation and a few spots (scan patterns, string-table schema) where guidance stops short of fully executable.

Suggestions

Split the larger modes (cultural-review checklist, vo-pipeline, qa) into references/ files (e.g. references/cultural-review.md) and keep SKILL.md as a mode overview with clearly signaled one-level-deep links.

Add literal grep/regex patterns for scan mode's anti-patterns (e.g. per-language patterns for unwrapped string literals) so findings are reproducible rather than described.

Specify the string-table JSON entry schema (key, value, context, max-length fields) once up front instead of implying it through the extract and validate rules.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics (checklists, exact ask prompts, output templates) with only minor over-explanation — the motivational intro ("Poor localization breaks immersion, confuses players, and blocks platform certification") and the enumerated cultural facts (white = mourning, 4 = death in Japanese/Chinese) restate knowledge Claude already has, though the latter doubles as audit scoping. Efficient with minor trimmable instances, matching anchor 4 rather than anchor 5's every-token-earns-its-place leanness or anchor 3's more substantial padding.

4 / 5

Actionability

Highly concrete throughout: exact file paths ("assets/data/strings/strings-en.json"), key-naming examples ("ui.hud.health_label"), literal "May I write..." prompts, grep targets ("HBoxContainer", "LinearLayout"), and full output templates. Minor gaps keep it below anchor 5 — scan mode describes anti-patterns without literal search regexes, and the string-table JSON schema is implied by the validate rules rather than specified — so guidance is mostly copy-paste ready but not fully.

4 / 5

Workflow Clarity

Sequencing is explicit (a Recommended Workflow section ordering all ten modes) and validation is pervasive: a pre-freeze checklist, a dedicated validate mode, freeze-violation warnings wired into extract, a QA verdict precedence with a first-match-wins rule, and NOT ASSESSED guards against false confidence. Clear sequence, explicit validation, feedback loops, and checklists — anchor 5.

5 / 5

Progressive Disclosure

The body is well-sectioned with per-mode headers, but all ten modes (~460 lines) are inlined in a single SKILL.md with no bundle files — the cultural-review checklist, VO pipeline details, and translator-brief template are each self-contained content that clearly belongs in separate reference files. Structure is good (above anchor 2's "minimal structure"), but content that should be separate is inline, matching anchor 3.

3 / 5

Total

16

/

20

Passed

Description

70%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 terse, domain-specific description that clearly communicates a distinct game-localization niche with several concrete actions, though some actions are compressed into noun labels. Its main weakness is the absence of any "Use when..." trigger guidance, which both caps completeness and leaves the most common user phrasing ("translate") unrepresented.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions localization, translating game strings, locale coverage, RTL languages, or string freeze."

Expand the noun labels into concrete actions, e.g. "review content for cultural sensitivity, manage voice-over recording, validate RTL layout" instead of "cultural review, VO, RTL".

DimensionReasoningScore

Specificity

"find hardcoded strings", "extract string tables", and "enforce string freeze" are concrete verb phrases, but "cultural review, VO, RTL" are compressed noun labels rather than described actions. This matches anchor 4 (several specific actions with minor gaps) rather than anchor 5's fully comprehensive verb-phrase coverage, and clearly exceeds anchor 3's 1-2 concrete actions.

4 / 5

Completeness

The "what" is clearly and concretely answered by the action list, but there is no "Use when..." clause or any equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 2 because the "what" is specific and multi-part, not vague.

3 / 5

Trigger Term Quality

Terms like "Localization", "hardcoded strings", "string table", "string freeze", "RTL", and "VO" are natural phrases a game developer would use when needing this skill. Coverage is good but common variations such as "translate/translation" and "i18n/l10n" are missing, matching anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym set.

4 / 5

Distinctiveness Conflict Risk

"Localization pipeline — find hardcoded strings... enforce string freeze" carves out a clear game-localization niche with distinct trigger terms (string freeze, RTL, VO pipeline) that no generic translation or documentation skill would share. Minimal conflict risk, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 10 missing, 10 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/localize/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.