CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

translator-api

Implements and debugs browser Translator API integrations in JavaScript or TypeScript web apps. Use when adding Translator support checks, language-pair availability flows, model download UX, session creation, translate() or translateStreaming() calls, input-usage measurement, or permissions-policy handling for on-device translation. Don't use for server-side translation SDKs, cloud translation services, or generic multilingual content pipelines.

75

Quality

94%

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.

A well-structured procedural skill: fully actionable steps, explicit validation and error-recovery loops, and exemplary conditional progressive disclosure into a real bundle. The only trim opportunity is redundant repetition of the worker/server exclusion and overlapping exclusion guidance in Step 4.

Suggestions

Consolidate the worker/server exclusion stop-condition (currently stated in Step 1.6, Step 2.8, and the last Error Handling bullet) into a single stated rule to save tokens.

Merge the overlapping Step 4 items 7 and 8, which both tell Claude not to route non-browser or general translation workloads through this API.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and free of basic-concept padding, but the worker/server exclusion stop-condition is repeated nearly verbatim in Step 1.6, Step 2.8, and the final Error Handling bullet, and Step 4 items 7-8 overlap — minor redundancy that could be trimmed.

4 / 5

Actionability

Executable commands ('node scripts/find-translator-targets.mjs .'), exact exception names (NotAllowedError, QuotaExceededError), concrete session-shape decision rules, and a real adaptable template asset make the guidance fully actionable for the common cases.

5 / 5

Workflow Clarity

Five clearly sequenced phases with a dedicated validation step (re-run the inventory script, test create()+translate(), streaming abort behavior, build/tests) and per-failure recovery guidance in the Error Handling section provide explicit checkpoints and feedback loops.

5 / 5

Progressive Disclosure

All six bundle files (4 references, 1 asset, 1 script) are referenced one level deep with conditional 'read X when Y' signals (Step 2 items 2-4, Step 3.1, Step 5.7), verified to exist and be substantive — clear navigation with no inlined bulk content.

5 / 5

Total

19

/

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: concrete capabilities, explicit 'Use when' triggers, and a negative boundary that resolves the main conflict risk. The only weakness is trigger-term coverage that favors API jargon over natural user phrasings.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'Translator support checks, language-pair availability flows, model download UX, session creation, translate() or translateStreaming() calls, input-usage measurement, or permissions-policy handling' — covering the full surface described in the skill body with no gaps.

5 / 5

Completeness

It explicitly answers both 'what' ('Implements and debugs browser Translator API integrations in JavaScript or TypeScript web apps') and 'when' ('Use when adding Translator support checks...') with concrete trigger phrases, plus an explicit negative boundary.

5 / 5

Trigger Term Quality

Good keyword coverage including natural feature-area terms like 'model download UX', 'session creation', 'on-device translation', and 'permissions-policy', but it leans on API method names and misses common lay phrasings such as 'translate text in the browser' or 'built-in/offline translation'.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (browser on-device Translator API) and the 'Don't use for server-side translation SDKs, cloud translation services, or generic multilingual content pipelines' clause minimizes overlap with general i18n/translation skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

webmaxru/web-ai-agent-skills

Path

skills/translator-api/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.