CtrlK
BlogDocsLog inGet started
Tessl Logo

translate-docs-zh-en

Translate and synchronize rtp2httpd Chinese documentation into English. ALWAYS use this skill whenever Chinese docs under docs/ need English translations under docs/en/, when Chinese doc diffs need to be reflected in existing English files, when VitePress English sidebar entries need to mirror Chinese docs, or when translation terminology needs to stay consistent across docs.

75

Quality

93%

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

87%

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

The body is a tight, actionable translation rulebook with concrete examples and a well-structured reference file. Its main gap is workflow_clarity: the batch-translation path lacks an explicit validate→fix→retry feedback loop across files.

Suggestions

Add an explicit cross-file validation checkpoint to the Batch Translation workflow — e.g. after translating, run a verification pass (sidebar completeness, link /en/ prefixes, no stray Chinese characters) and loop back to fix any flagged files before declaring done.

Fold the per-file Quality Checklist into a 'validate' step at the end of each numbered workflow so verification is sequenced rather than presented as a separate section.

Consider moving the inline terminology/title-mapping tables into references/translation-memory.md to slim the body, since that reference already tracks stable terminology.

DimensionReasoningScore

Conciseness

Lean and rule-dense with no concept-explaining fluff; every line is a concrete directive (path transforms, do-not-translate lists, term mappings). It assumes Claude's competence; the only minor redundancy is the Quality Checklist restating earlier rules, which does not rise to padding. Not a 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Provides concrete, copy-paste-ready guidance: exact image-path transforms ('./images/foo.png' becomes '../images/foo.png'), explicit terminology mappings ('花屏' -> 'artifacts'), and sidebar config locations. As an instruction-only skill the absence of code is not penalized; the guidance is fully actionable. Not a 2 because no key detail is missing or pseudocoded.

3 / 3

Workflow Clarity

New/Update/Batch workflows are clearly sequenced and a per-file Quality Checklist exists, but batch operations over many files lack an explicit validate→fix→retry feedback loop or cross-file verification checkpoint. Per the rubric's batch-operation note this caps the score at 2; not a 1 because the sequences and checklist are present.

2 / 3

Progressive Disclosure

The body is well-organized into clear sections and references 'references/translation-memory.md' — verified as a real, one-level-deep, clearly signaled file with no nested-reference chains. Not a 2 because references are explicitly signaled and appropriately separated rather than inline or deeply nested.

3 / 3

Total

11

/

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, well-triggered, and clearly distinct: it names concrete actions and provides four explicit 'use when' scenarios tied to a single project's doc-translation workflow. It satisfies both the what and the when without verbosity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Translate and synchronize rtp2httpd Chinese documentation into English' — across four distinct scenarios (new translations, diff sync, sidebar mirroring, terminology consistency). Matches the score-3 anchor for multiple specific concrete actions; not a 2 because the action set is comprehensive rather than partial.

3 / 3

Completeness

Explicitly states what the skill does (translate and synchronize zh→en docs) and when to use it via 'ALWAYS use this skill whenever...' with four explicit triggers, matching the score-3 anchor for both what and when.

3 / 3

Trigger Term Quality

Uses natural user-facing terms a developer would actually say: 'Chinese docs', 'English translations', 'English files', 'VitePress English sidebar'. Good coverage of natural variations rather than only jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to rtp2httpd zh→en documentation with distinct triggers; unlikely to fire for unrelated translation or doc skills. Clear niche matching the score-3 anchor.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
stackia/rtp2httpd
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.