CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/i18n-string-coverage

Build-an-X workflow that scans source code for untranslated strings - finds hardcoded user-facing text not wrapped in the i18n function (`t()`, `i18n.t`, `gettext`, `__()`, etc.), maps gaps to the team's translation file, reports per-language coverage (en: 100%; fr: 87%; es: 60%), gates per-PR for new untranslated strings. Use when the product ships in multiple locales and the team needs continuous coverage tracking.

79

Quality

99%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

The body is concise, fully actionable, well-sequenced with validation checkpoints, and properly splits detail into a one-level reference. The only soft spot is the Step 2 grep being a heuristic with acknowledged gaps, but this is explicitly flagged in Limitations rather than hidden.

DimensionReasoningScore

Conciseness

Lean and efficient — assumes Claude's competence (no explanation of what i18n is), every table and code block earns its place, and concepts like RTL/bidi are referenced rather than taught.

3 / 3

Actionability

Provides executable, copy-paste-ready code: the grep scan, the Python coverage diff script, and the YAML PR gate, plus a per-stack wrap-function table and a concrete worked example.

3 / 3

Workflow Clarity

The 'How to use' section sequences six numbered steps that map to Steps 1-6, the PR gate includes an explicit fail/exit-1 checkpoint with informational-vs-blocking guidance, and the worked example shows the validate-and-re-run feedback loop.

3 / 3

Progressive Disclosure

SKILL.md is an overview that defers the fill-in template to a real, one-level-deep reference (references/coverage-report.md, which exists), with inline code kept to essentials rather than duplicated into separate files.

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.

The description is specific, trigger-rich, complete, and clearly niche-scoped. A minor wrinkle is the 'Build-an-X workflow' prefix which is boilerplate scaffolding language rather than a capability statement, but it does not undermine the clarity of the rest.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'scans source code for untranslated strings', 'maps gaps to the team's translation file', 'reports per-language coverage', 'gates per-PR' — matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what (scan/map/report/gate) and when via the explicit 'Use when the product ships in multiple locales and the team needs continuous coverage tracking' clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'untranslated strings', 'translation file', 'coverage', 'multiple locales', 'per-PR' — with good breadth rather than just technical jargon.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (translation coverage gating) with distinct triggers unlikely to conflict with general scanning or linting skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents