CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

translate-docs

Translate the docs site and blog into another language (website/i18n), or update translations after the English docs or blog changed; the repo lists the work and validates it, any model can translate

Quality

85%

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

92%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 exemplary instruction-only skill: every step is executable, validation and feedback loops are explicit, and the translation rules are concrete enough to apply mechanically. The only nit is a slightly redundant clarification around `--same` and a few long compound sentences that could be split without losing content.

DimensionReasoningScore

Conciseness

The body is dense, instruction-only prose that assumes Claude's competence (no explanation of MDX, Docusaurus, or translation basics), but contains minor trimmable redundancy: "Don't clear it with `--same`, which is for text meant to match English" partially restates the `--same` rule introduced two sentences earlier.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with exact flags ("node website/translate/translate.mjs prepare --json", "--locale es", "finalize", "--same <id>", "node --test website/translate/mdx.test.mjs") and coverage of the common cases: new pages, updates with and without a diff, removed translations, and UI strings.

5 / 5

Workflow Clarity

The procedure is clearly sequenced with an explicit validation feedback loop ("Fix each `✗` problem it prints and run it again until it passes"), a recovery path for stale data ("run `prepare` again and translate what it lists"), and pre-PR verification via the test suite and `check`, so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references; sections (Procedure, Weekly run, Translation rules) are well organized and the one external pointer ("How the pieces fit: `website/translate/README.md`") is clearly signaled and one level deep, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

73%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 specific, well-scoped description that clearly conveys a niche capability with an explicit trigger for the update case. Its main gaps are the un-enumerated sub-tasks (which the body shows are substantial) and missing trigger synonyms like "localization".

Suggestions

Enumerate the concrete sub-tasks to raise specificity, e.g. "Translates doc and blog pages, UI strings, and tag/author metadata; updates stale translations when English changes; commits the validated lock file".

Add an explicit trigger clause covering both paths, e.g. "Use when the English docs or blog have changed and translations need updating, or when adding translations for a new locale".

Include natural synonyms such as "localization" or "internationalization" so the description matches how users commonly phrase the request.

DimensionReasoningScore

Specificity

Names the domain ("docs site and blog", "website/i18n") and two concrete actions ("Translate ... into another language", "update translations after the English docs or blog changed"), matching the 1-2-action anchor; it does not enumerate the several distinct sub-tasks the body actually covers (UI strings, removed pages, lock files), which keeps it below the several-actions anchor.

3 / 5

Completeness

The "what" is clear (translate the docs site and blog; update translations) and an explicit "when" exists for the update path ("after the English docs or blog changed"), so trigger guidance is present rather than merely implied; however there is no trigger for the new-locale translation path and no "Use when..." clause with concrete trigger phrases, keeping it below the top anchor.

4 / 5

Trigger Term Quality

Good natural-term coverage — "translate", "translations", "another language", "docs", "blog", "English" are phrases users would naturally say — but common synonyms like "localization" or "internationalization" are missing, and "website/i18n" is a repo path rather than a user phrase.

4 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to this repository's translation workflow ("the docs site and blog", "(website/i18n)", "the repo lists the work and validates it"), giving it a clear niche with distinct triggers and minimal conflict risk against generic translation or docs skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

reactive/data-client

Path

.agents/skills/translate-docs/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.