CtrlK
BlogDocsLog inGet started
Tessl Logo

translate-docs-zh-en

Translate Chinese rtp2httpd docs into docs/en/ and synchronize English navigation, links, and terminology after source changes.

70

Quality

86%

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

93%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-structured, token-efficient instruction skill with concrete examples, a real validation/build feedback loop, and appropriate progressive disclosure through one verified reference. The only gap is that the workflow is topic-organized rather than a tightly numbered sequence with explicit per-stage checkpoints.

Suggestions

Add a short numbered sequence (e.g., 1. translate content → 2. resolve links → 3. sync navigation → 4. validate build) so the workflow reads as explicit ordered checkpoints rather than topic sections.

Make the validation feedback loop more explicit as a retry loop ('If docs:build fails, fix the translation cause and re-run until it passes') to fully reach the workflow-clarity top anchor.

Consider a compact pre-completion checklist (translation complete, links/assets valid, example behavior preserved, navigation mirrored) to reinforce the validation gate.

DimensionReasoningScore

Conciseness

The body is lean and dense with rules, assumes Claude's competence (no explaining what translation/VitePress is), and every line is actionable guidance with no padding, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete executable guidance throughout — real paths (docs/en/, docs/.vitepress/config.ts), specific link transforms (/guide/quick-start → /en/guide/quick-start, ../images/foo.png → ../../images/foo.png), markup to preserve (> [!NOTE]), display-value swaps (央视 → CCTV), and the executable `pnpm run docs:build` command cover the common cases.

5 / 5

Workflow Clarity

A clear validation gate exists ('Check the diff for complete translation, valid links/assets... Run pnpm run docs:build... Correct failures caused by the translation before finishing'), giving a real feedback loop, but the workflow is organized by concern rather than a strict numbered sequence with per-stage checkpoints, so it is not a 5.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single clearly-signaled, one-level-deep reference (references/translation-memory.md, verified to exist) used for terminology, matching 'clear overview with well-signaled one-level-deep references; easy navigation'.

5 / 5

Total

19

/

20

Passed

Description

78%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 tight, third-person description that pins a specific project niche and pairs a concrete 'what' with an explicit 'when'. It could add user-mention trigger phrasing and a few synonyms to push completeness and trigger-term quality to the top level.

Suggestions

Add an explicit 'Use when...' clause naming user-mention triggers (e.g., 'Use when the user asks to translate rtp2httpd docs or mentions Chinese/English documentation changes').

Include natural synonyms/extensions such as 'localize', 'i18n', or '.md' to broaden trigger-term coverage.

Optionally name the build/validation step (e.g., 'and rebuild the docs site') so the action list is comprehensive.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Translate Chinese rtp2httpd docs into docs/en/', 'synchronize English navigation, links, and terminology'), matching the 'several specific actions; minor gaps' anchor; not a 5 because build/validation steps present in the body are absent here.

4 / 5

Completeness

It has a clear 'what' (translate and sync docs) and an explicit 'when' ('after source changes'), but the trigger is a single scenario without 'Use when the user asks...' phrasing, fitting 'both what and when; when could be more explicit'.

4 / 5

Trigger Term Quality

Natural terms a user would say ('Translate', 'Chinese', 'English', 'docs') are present, but it lacks synonyms/extensions like 'localize', 'i18n', or file types, so it stops at 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (rtp2httpd Chinese-to-English documentation) with distinct triggers and minimal conflict risk with any other skill, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

17

/

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
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.