CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

doc-i18n

将 FastGPT 文档从中文翻译为面向北美用户的英文。当用户提到翻译文档、i18n、国际化、translate docs、新增/修改了中文文档需要同步英文版时,使用此 skill。也适用于用户要求检查文档翻译缺失、批量翻译、或对比中英文文档差异的场景。

Quality

88%

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

81%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 well-built instruction-only skill: the workflow is clearly sequenced with explicit validation, feedback, and escalation steps, and nearly all guidance is concrete and project-specific. The main improvements are trimming generic tone advice and the glossary-duplicating terminology list, and adding a runnable example of the check script and a sample translated file pair.

Suggestions

Add a copy-paste-ready invocation example for document/script/checkEnglishDocs.mjs (e.g., a node one-liner or import snippet) and a short before/after .mdx → .en.mdx / meta.json → meta.en.json pair so the translation and validation steps are fully executable.

Trim the generic tone guidance ('professional but friendly, not overly formal') and reduce the inline terminology example list, since the skill itself mandates the shared glossary as the single source of truth for product terms.

Consider moving the platform-localization table and translation-style examples into a reference file (or the shared guidelines file), keeping SKILL.md focused on the workflow overview.

DimensionReasoningScore

Conciseness

The body is dense with project-specific rules Claude could not infer (dual-file naming, /en/ prefix rules, meta.json sync rules, glossary precedence, longest-phrase matching), and the before/after example is compact and high-value. Minor over-explanation remains: the generic tone section ('保持专业但友好…不要过度正式,也不要过于随意') and the inline terminology list partially duplicate the shared glossary the skill itself defers to, so it fits the 4 anchor ('efficient; minor instances of over-explanation that could be trimmed') rather than the every-token-earns-its-place 5 anchor.

4 / 5

Actionability

Guidance is largely executable: exact commands ('git diff --name-only', 'git diff --cached --name-only'), concrete path examples ('/guide/build/workflow/assisted-generation' → '/en/guide/...'), a named validation script ('document/script/checkEnglishDocs.mjs 导出的 checkEnglishDocs(contentDir)'), and a concrete glossary-matching example ('知识库引用' → 'Dataset citation(s)'). Minor gaps keep it at 4 rather than 5: no invocation snippet for the check script and no example .en.mdx / meta.en.json input-output pair.

4 / 5

Workflow Clarity

The four-step workflow (determine scope → translate .mdx → sync meta.json → post-translation verification) is clearly sequenced, and this batch operation has explicit validation checkpoints with feedback loops: glossary cross-check ('发现禁用译法时必须修正'), residual-Chinese search, route validation via checkEnglishDocs, and escalation rules ('无法可靠判断位置时,先询问用户'; report and confirm before coining new terms). This matches the 5 anchor ('clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes') — the final section is effectively a checklist.

5 / 5

Progressive Disclosure

The file is well-organized with clear sections, and the two shared resources (translation-guidelines.md, fastgpt-glossary.json) are signaled up front with one-level-deep relative paths. However, no local bundle files exist to verify those references against (they point outside the skill directory), and reference-shaped material (the platform-localization table and style examples) is inlined, so it fits the 4 anchor ('good structure; most content appropriately placed; references mostly clear; minor organization gaps') rather than the fully split 5 anchor.

4 / 5

Total

17

/

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 strong description: it states the concrete capability set (translate, sync, audit missing translations, batch translate, bilingual diff) and gives an explicit, natural 'use when' clause with trigger terms in both Chinese and English. The only gap is a few missing synonyms such as 'l10n'/'localization'.

DimensionReasoningScore

Specificity

The description names the domain (FastGPT docs, Chinese → North American English) and multiple concrete actions: '将 FastGPT 文档从中文翻译为面向北美用户的英文' (translate), '新增/修改了中文文档需要同步英文版' (sync English versions), '检查文档翻译缺失' (check for missing translations), '批量翻译' (batch translate), and '对比中英文文档差异' (compare bilingual diffs). This matches the 5 anchor ('multiple specific concrete actions; comprehensive coverage') — the action space within this niche is fully enumerated, so it exceeds the 'minor gaps' qualifier of the 4 anchor.

5 / 5

Completeness

It clearly answers 'what' ('将 FastGPT 文档从中文翻译为面向北美用户的英文' — translate FastGPT docs from Chinese into English for North American users) and 'when' with an explicit usage clause ('当用户提到翻译文档、i18n、国际化、translate docs、新增/修改了中文文档需要同步英文版时,使用此 skill') plus extended scenarios. This matches the 5 anchor: both what and when are explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes natural trigger phrases users would actually say, in both Chinese and English: '翻译文档', 'i18n', '国际化', 'translate docs', '同步英文版', '批量翻译', '对比中英文文档差异'. However, common synonyms such as 'l10n' and 'localization' are absent, fitting the 4 anchor ('good keyword coverage; a few natural terms missing') rather than the comprehensive synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to FastGPT's Chinese↔English documentation pipeline, a clear niche with distinct triggers (FastGPT, 中文文档, 同步英文版). It would not fire for generic translation or unrelated doc tasks, matching the 5 anchor ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

labring/FastGPT

Path

.agents/skills/doc/i18n/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.