CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-i18n

Internationalization — translations (ETranslations, useIntl, formatMessage) and locale management. NEVER modify auto-generated translation files.

59

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 ./.skillshare/skills/1k-i18n/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

An action-oriented, well-structured i18n skill body with executable code, exact commands, and a clean one-level reference. The main weaknesses are a missing validation checkpoint in the translation workflow and minor duplication of the critical-restrictions block.

Suggestions

Add a validation step to the Translation Workflow, e.g. 'Verify the new key appears in ETranslations after yarn i18n:pull before using it in code.'

Deduplicate the critical-restrictions/consequences content and trim the 'Topics covered' list, since both repeat material already present in the body.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable code and compact tables, but the auto-generated restriction and 'Consequences of violation' list are duplicated, and the 'Topics covered' enumeration repeats content already in the body — mild padding that could be tightened.

2 / 3

Actionability

It provides copy-paste-ready TypeScript (useIntl, formatMessage, appLocale), exact CLI commands (yarn i18n:search/pull/add), and a concrete key-shape mapping table — fully executable guidance.

3 / 3

Workflow Clarity

The Translation Workflow is a clear 4-step sequence, but it touches external/generated state (Lokalise edits and i18n:pull) with no validation checkpoint, so per the destructive/batch-operations rule workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview with one well-signaled, one-level-deep reference (references/rules/i18n.md, verified present), and content is appropriately split across clear sections.

3 / 3

Total

10

/

12

Passed

Description

67%

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-delineated i18n description that names real APIs and a strong distinguishing restriction. Its main gap is the absence of explicit 'when to use' trigger guidance, which caps completeness and weakens trigger-term naturalness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when adding, updating, or searching translations, formatting localized text, or managing locales in OneKey.'

Soften API-name jargon in the lead with natural user phrasings like 'translate UI text' or 'add a translation key' alongside ETranslations/useIntl/formatMessage.

DimensionReasoningScore

Specificity

The description enumerates concrete named primitives ('ETranslations, useIntl, formatMessage') and locale management rather than vague actions, matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

It clearly states what the skill does (translations and locale management) but has no 'Use when...' trigger clause — only a prohibition ('NEVER modify auto-generated translation files') — so the when guidance is missing, capping completeness at 2.

2 / 3

Trigger Term Quality

It includes natural domain terms like 'Internationalization', 'translations', and 'locale management', but leans on API-name jargon (ETranslations, useIntl, formatMessage) that users would rarely say verbatim, missing common variations.

2 / 3

Distinctiveness Conflict Risk

It carves out a clear i18n niche with a distinctive auto-generated-files prohibition, making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.