CtrlK
BlogDocsLog inGet started
Tessl Logo

i18n-translate

Translate one, multiple, or all explicitly requested FastGPT i18next namespace JSON files from the completed Simplified Chinese source into every supported target locale, with product-language research and structural validation. Use only when the user explicitly invokes `$i18n-translate` and identifies namespace names, files under `packages/web/i18n/zh-CN/`, or all namespaces; never trigger implicitly for ordinary i18n, copywriting, or documentation work.

77

Quality

96%

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%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 efficient, fully actionable workflow for a batch translation task, with explicit validation feedback loops and well-structured one-level-deep references to real bundle files. No significant weaknesses across any dimension.

DimensionReasoningScore

Conciseness

A lean body that assumes Claude's competence, giving actionable rules ('Match the longest glossary term first', 'Use rg to find ...') without explaining i18n/i18next basics; every line earns its place.

5 / 5

Actionability

Provides copy-paste-ready commands (the validator invocation, 'git diff --', formatter) plus concrete preservation rules for {{vars}}, <bold> tags, and URLs, covering the common translation cases.

5 / 5

Workflow Clarity

A clearly sequenced four-step workflow with explicit validation checkpoints and a feedback loop (validate -> require zero errors/warnings -> format -> re-validate -> review git diff), satisfying the batch-operation validation requirement.

5 / 5

Progressive Disclosure

The overview body signals one-level-deep references to two real bundled files (translation-guidelines.md, fastgpt-glossary.json) and a scripts/ validator, keeping bulky detail out of SKILL.md while remaining easy to navigate.

5 / 5

Total

20

/

20

Passed

Description

92%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 precise, third-person description that explicitly covers what the skill does and when to trigger it, with a strong distinctiveness guard against implicit invocation. Only minor headroom on trigger-term breadth.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Translate ... namespace JSON files from the completed Simplified Chinese source into every supported target locale, with product-language research and structural validation'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (translate namespaces into target locales with research and validation) and when ('Use only when the user explicitly invokes $i18n-translate and identifies namespace names, files under packages/web/i18n/zh-CN/, or all namespaces'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('translate', 'Simplified Chinese source', 'namespace JSON files', '$i18n-translate', 'i18n', 'copywriting') with synonyms and paths, but a few natural variants a user might say are not exhaustively enumerated.

4 / 5

Distinctiveness Conflict Risk

A clear niche (FastGPT i18next namespace translation from zh-CN) with an explicit negative-trigger guard ('never trigger implicitly for ordinary i18n, copywriting, or documentation work'), minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
labring/FastGPT
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.