CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/pseudo-localization-runner

Use when preparing an app for translation, checking localization infrastructure, or when pseudo-localization comes up. Replaces strings with accented, 35%-longer variants to expose hardcoded text, truncation, encoding and bidi problems without real translators.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

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 high-quality, highly actionable skill body: executable code for every common stack, a clearly sequenced workflow with an explicit activation check and a worked error-recovery example, and a well-signaled one-level-deep reference. The only weaknesses are mild redundancy between the steps and the anti-patterns table, and a mostly monolithic inline structure despite the available references directory.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, library-specific gotchas (the '--ast' requirement, i18next-pseudo's languageToPseudo activation check, the language detector's lookup order, why Accept-Language headers fail for SPAs) rather than concepts Claude already knows. Minor trimming is possible: the anti-patterns table restates several points already made in Steps 1-3, and the Overview's examples overlap Step 2, keeping it just short of the 'every token earns its place' anchor.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready formatjs CLI commands, a complete i18next init snippet, a complete Playwright scan test with a concrete leak-detection predicate and allowlist, a CI yaml step, and a real transform script in the referenced file. Specific examples cover the common stacks (react-intl, i18next, Android, manual).

5 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced (pick library, configure, run, spot issues, automate, CI, manual alternative) with an explicit validation checkpoint ("Verify the pseudo-locale is active... If it shows plain English, the locale did not activate, and every later check is meaningless") and a demonstrated feedback loop in the worked example (scan fails with three leaks, fixes applied, re-run is clean).

5 / 5

Progressive Disclosure

The single bundle reference (references/manual-transform.md) is clearly signaled in Step 7 and the References section, is one level deep, and is a real file with self-contained content. Structure is good with clear section headers, but nearly all detail (both per-stack configuration guides, the Playwright test, CI) lives inline in the 274-line SKILL.md rather than being split out, which is 'most content appropriately placed' rather than an ideal overview-plus-references split.

4 / 5

Total

18

/

20

Passed

Description

87%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 description with an explicit 'Use when' trigger clause, a concrete third-person statement of what the skill does, and a distinctive niche. The only gaps are missing common synonyms (i18n, internationalization, l10n) and the fact that it describes one core method rather than multiple discrete actions.

DimensionReasoningScore

Specificity

The description gives one concrete action ("Replaces strings with accented, 35%-longer variants") and enumerates the specific problems it exposes ("hardcoded text, truncation, encoding and bidi problems"), matching the 'several specific actions; minor gaps' anchor. It is not a 5 because it describes a single transformation method rather than multiple distinct concrete actions.

4 / 5

Completeness

It explicitly answers both: what ("Replaces strings with accented, 35%-longer variants to expose hardcoded text, truncation, encoding and bidi problems") and when ("Use when preparing an app for translation, checking localization infrastructure, or when pseudo-localization comes up") with concrete trigger phrases. Both clauses are present and explicit, matching the top anchor rather than the 'when could be more specific' level 4.

5 / 5

Trigger Term Quality

Natural triggers include "preparing an app for translation", "checking localization infrastructure", and "pseudo-localization", which users would plausibly say. Common synonyms like "i18n", "internationalization", or "l10n" are absent, keeping it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

"pseudo-localization" names a clear niche with distinct triggers, and "without real translators" explicitly separates it from real-translation skills. Overlap risk is minimal, fitting the 'clear niche with distinct triggers' anchor.

5 / 5

Total

18

/

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.

Reviewed

On this page