CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

64

Quality

80%

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

85%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 lean, highly actionable workflow document: every step has an exact command, validation and confirmation checkpoints are explicit, and detail is correctly pushed to real, well-anchored reference files. The only soft spots are a couple of trimmable prose passages and two under-specified commands (the confirmed-hash source and i18n:search syntax).

DimensionReasoningScore

Conciseness

The body is dense, imperative, and almost entirely project-specific knowledge (wrapper selection, mode semantics, confirmation boundaries, credential/timeout behavior) with no padding or explanation of known concepts; a few prose spots (the sandbox/wrapper paragraph, "Keep the user informed while waiting...") could still be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

Every workflow step ships a concrete, copy-paste-ready command with placeholders defined ("use `.tmp/i18n/<task>/` for `<dir>`"), and code usage gives executable examples like `useIntl().formatMessage({ id: ETranslations.some_key })`; minor gaps — the origin of `<confirmed-hash>` is never stated and `yarn i18n:search` is invoked without any syntax — keep it at anchor 4.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints ("Verify the returned project name/ID", "wait for confirmation", "Check the receipt and full generated diff", rescan after wiring) and feedback loops for error recovery (recovery guidance link for interrupted applies, explicit rule against silently switching modes to bypass a rejected overwrite), matching anchor 5.

5 / 5

Progressive Disclosure

A ~100-line overview keeps the workflow inline while splitting detail into well-signaled, verified one-level-deep references — patch format, single-key commands, old-key cleanup and recovery in `references/rules/i18n.md`, and HTML feedback in `references/interactive-review.md` — with all anchors resolving to real headings, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Description

70%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, distinctive description that names concrete workflow stages and a hard safety rule, anchored to a unique product/platform niche. Its main weakness is the complete absence of any "Use when..." trigger guidance, which caps completeness and limits discoverability.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to translate, update, preview, or verify module copy in OneKey, or mentions Lokalise, i18n keys, or locale JSON."

Include common trigger synonyms such as "localization", "locale", and "translate copy" alongside "i18n" to broaden natural keyword coverage.

Spell out what "module copy" and "pull" mean in one or two words each so the capability list reads as concrete actions rather than internal workflow jargon.

DimensionReasoningScore

Specificity

Lists several concrete workflow actions ("full-language translation create/update, bilingual previews, confirmed upload, pull, and verification") plus an explicit rule ("Never edit generated translations"), matching anchor 4; not 5 because some actions like "module copy" and "pull" are workflow jargon rather than fully self-explanatory capabilities.

4 / 5

Completeness

The "what" is clear (the create/update/preview/upload/pull/verify workflow) but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric requires to score above 3.

3 / 5

Trigger Term Quality

Contains good natural trigger terms users would say — "i18n", "translation", "Lokalise", "bilingual" — matching anchor 4; not 5 because common synonyms and variations like "localization", "locale", or "translate copy" are missing.

4 / 5

Distinctiveness Conflict Risk

"OneKey i18n and Lokalise workflow" names a specific product and platform, creating a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

16

/

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

Path

.skillshare/skills/1k-i18n/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.