CC i18n-sync
Translate and synchronize application JSON locale files using source-key usage, project terminology, and focused validation. Use when adding keys or languages, updating source copy, or reviewing missing and stale translations.
The skill promises to sync JSON locale files: find unused keys, pull translations by project terminology, validate gaps. Quality scores at 72% suggest working parts, but process score at 50% hints the logic is half-baked. Single file, no scripts, no model runs. Broken references means the folder links to missing resources—you'll debug paths yourself. No critical issues found, but that's not a clean bill.
Install if you already have translation infrastructure and need help with routine work. If you're building localization from scratch, test whether the skill adapts to your project structure first.
Translate and synchronize application JSON locale files using source-key usage, project terminology, and focused validation.
As a process C 50/100 · Has gaps — References files that are not bundled: ../../hooks/README.md, ../frontend-patterns/SKILL.md, ../seo/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../hooks/README.md - warning
missing-refreference to a missing file: ../frontend-patterns/SKILL.md - warning
missing-refreference to a missing file: ../seo/SKILL.md
Process rating: all ten parameters 50/100
- 0Tools and files. 3 referenced file(s) missing: ../../hooks/README.md, ../frontend-patterns/SKILL.md, ../seo/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 10 steps, 1 vague phrases
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1689 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 226: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.