Name: 1k-i18n
Rating: 59.2 (1 reviews)
Author: OneKeyHQ

1k-i18n

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-i18n/SKILL.md

Quality

Content

80%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.

The content is highly actionable with executable code and concrete commands, a clear search-first workflow, and appropriate progressive disclosure to a real reference file. The main improvement is adding an explicit validation checkpoint after i18n:pull/add to confirm keys synced correctly.

Suggestions

Add an explicit verification step to the workflow, e.g. after 'yarn i18n:pull' confirm the new ETranslations member is present and the build compiles before using the key in code.

Trim the 'Consequences of violation' bullet list or merge it into the critical-restrictions block to reduce repetition.

Move the deeper key-shape mapping detail into references/rules/i18n.md and keep only the most common shape inline in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with focused code examples and a compact key-shape mapping table, though the 'Consequences of violation' list and duplicated code snippets add mild padding that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready component and non-component usage examples, concrete yarn commands (i18n:search, i18n:pull, i18n:add), and an explicit key-naming pattern with examples covering the common cases.	5 / 5
Workflow Clarity	The Translation Workflow is a clear numbered sequence (search, update-or-add, use in code) with the search-first branching logic, but it lacks an explicit validate/sync-verification checkpoint after pulling or adding keys, which keeps it just short of the top band.	4 / 5
Progressive Disclosure	SKILL.md is a well-organized overview with a clearly signaled one-level-deep reference (references/rules/i18n.md) that exists as a real file, plus a Key Files table; minor gaps are that some detail (e.g. the full key-shape mapping) might also live in the reference rather than inline.	4 / 5
	Total	17 / 20 Passed

Description

61%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.

The description is specific and technically grounded with concrete API names and a clear restriction, but it lacks an explicit 'Use when...' trigger clause, which limits its completeness score. Adding trigger phrasing would lift it into the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or updating user-facing text, managing translation keys, or working with the Lokalise/i18n pipeline.'

Include a natural synonym like 'i18n strings' or 'localized text' to broaden trigger-term coverage.

Consider trimming the API-name list slightly so the core action (manage translations and locales) reads first.

Dimension	Reasoning	Score
Specificity	Names the i18n domain and several concrete capabilities (ETranslations, useIntl, formatMessage) plus a specific locale-management restriction, but coverage of actions is more enumerative than comprehensive.	4 / 5
Completeness	The 'what' is clear (translations and locale management tooling plus a forbidden-action guardrail), but there is no 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural domain terms like 'translations', 'locale management', and 'internationalization' alongside API names users would mention, though it omits common synonyms like 'i18n strings' or file extension cues.	4 / 5
Distinctiveness Conflict Risk	The OneKey-specific API references (ETranslations, formatMessage) and the auto-generated-file warning carve a distinct niche, with only minor overlap risk against a general coding-patterns skill.	4 / 5
	Total	15 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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
Path: .skillshare/skills/1k-i18n/SKILL.md
Commit: 3cff1b4

Reviewed: about 17 hours ago

Table of Contents

Discovery Implementation Validation

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.