CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-i18n

OneKey i18n and Lokalise workflow for module copy, full-language translation create/update, bilingual previews, confirmed upload, pull, and verification. Never edit generated translations.

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exceptionally well-crafted instruction-only skill: lean operational prose, fully executable commands with defined placeholders, a tightly sequenced workflow gated on explicit user confirmation with verification receipts, and clean one-level-deep reference structure. All four dimensions hit the top anchor without padding or over-explanation.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific operational guidance (wrapper fallbacks, silent credential loading, bundled-vs-live locale semantics, mode table) and contains no explanations of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Every workflow step ships a copy-paste-ready command (e.g. `yarn <wrapper> yarn i18n:workflow sync --project-name "Monorepo v5" --out <dir>/sync.json`, `apply --file <dir>/plan.json --approve <confirmed-hash>`) with placeholders explicitly defined (`.tmp/i18n/<task>/` for `<dir>`, wrappers `op`/`keychain`/`oenv`), plus concrete code-usage examples like `useIntl().formatMessage({ id: ETranslations.some_key })`.

5 / 5

Workflow Clarity

The 8 numbered steps are clearly sequenced with explicit validation checkpoints ("Verify the returned project name/ID", "wait for confirmation", "Check the receipt and full generated diff", "rescan and run appropriate checks") and error-recovery loops via linked recovery guidance — critical for this batch upload/delete-capable operation.

5 / 5

Progressive Disclosure

SKILL.md stays an overview/workflow layer, with detail correctly split into one-level-deep, well-signaled references (references/rules/i18n.md sections #recovery, #fill-a-draft, #old-key-cleanup, #single-key-commands, and references/interactive-review.md), all of which exist as real files and headings.

5 / 5

Total

20

/

20

Passed

Description

75%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 highly specific, distinctive description that concretely enumerates the workflow's actions and its core safety rule. Its one real weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness and slightly limits discoverability.

Suggestions

Add an explicit trigger clause, e.g. "Use when translating OneKey module copy, syncing locale JSON with Lokalise, or preparing bilingual translation previews for upload."

Include natural synonyms such as "localization", "locale", and "translate UI copy" alongside "i18n" and "translation" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"module copy, full-language translation create/update, bilingual previews, confirmed upload, pull, and verification" enumerates six concrete actions with comprehensive coverage of the workflow's capabilities, matching the top anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

The description explicitly and clearly answers "what" (copy, translation create/update, previews, upload, pull, verification) but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "i18n", "Lokalise", "translation", "upload", and "pull" are natural phrases users would say in this domain, but common synonyms such as "localization", "locale", or "translate UI copy" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"OneKey i18n and Lokalise workflow" names a specific product and toolchain, carving a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

17

/

20

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.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

relative_links

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

Warning

referenced_paths_exist

Referenced path issues: 4 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.