CtrlK
BlogDocsLog inGet started
Tessl Logo

translate-docs

Translate and sync bilingual user documentation between docs/zh/ and docs/en/ following the source-of-truth rules in docs/AGENTS.md.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/translate-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is well-structured, actionable, and concise, with a clear workflow and appropriate externalization of terminology detail. Minor redundancy between the rules and mistakes sections and the absence of an explicit retry loop keep it just below top marks.

Suggestions

Fold the 'Common mistakes' items that merely restate 'Rules and conventions' into the rules, or keep only the forward-looking guidance to remove redundancy.

Add an explicit feedback loop in the Verify step, e.g. 'If the build fails, fix the reported links/errors and re-run the build before proceeding.'

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept-explanation padding, though the 'Common mistakes' section partially restates the 'Rules and conventions' section.

4 / 5

Actionability

Provides concrete commands (git diff, pnpm build) and specific typography/terminology rules, with minor gaps where guidance defers to the external docs/AGENTS.md.

4 / 5

Workflow Clarity

A clear four-step sequence includes an explicit Verify checkpoint, satisfying validation for this batch operation; it lacks a full validate-fix-retry feedback loop that would reach a 5.

4 / 5

Progressive Disclosure

Well-organized sections with a single clearly signaled one-level reference (docs/AGENTS.md) for terminology and style detail; no bundle files exist that require splitting.

4 / 5

Total

16

/

20

Passed

Description

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

The description is specific and distinctive, clearly conveying a bilingual documentation translation/sync niche. Its main weakness is the missing explicit 'when to use' trigger guidance, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when translating or syncing changes between docs/zh/ and docs/en/, or when either locale has been updated.'

Add a natural synonym or two ('localization', 'i18n') to broaden trigger-term coverage without sacrificing specificity.

DimensionReasoningScore

Specificity

Names the domain (bilingual documentation) and two concrete actions ('Translate and sync') with specific directory paths, but coverage is not comprehensive beyond those two verbs.

3 / 5

Completeness

Clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('translate', 'sync', 'bilingual', 'documentation') plus concrete path triggers, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (zh/en bilingual doc sync under specific paths) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

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
MoonshotAI/kimi-code
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.