CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

react-admin-i18n

Guidelines for internationalizing a react-admin or shadcn admin kit application. Use when adding i18n support, creating translation files, translating hardcoded English strings in JSX, or reviewing i18n PRs in a react-admin project. Covers namespace conventions, interpolation, pluralization, locale-aware formatting, and the full workflow for converting an English-only app to multi-language. Trigger this skill whenever the user mentions i18n, internationalization, translation, localization, locale switching, or multi-language in a react-admin or shadcn admin kit context — even if they just say "translate this component" or "add French support".

Quality

84%

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

63%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 high-quality, deeply knowledgeable skill body with concrete, executable react-admin i18n guidance and a clear sequenced workflow. Its weaknesses are verbosity from a checklist that duplicates the rules section, two conflicting provider-setup examples, and a monolithic single-file structure with no progressive disclosure to reference files.

Suggestions

Replace the 18-item checklist that restates the 15 rules with a short pointer ('Verify each rule above, plus:') covering only the items not already encoded as rules.

Split the type-safe catalog section, the full LanguageSelector component, and the test suite into reference files (e.g. references/catalogs.md, references/testing.md) and keep SKILL.md as an overview with well-signaled one-level-deep links.

Fix the minor code gaps: define the 'placeholder' variable in rule 15's good example, align 'englishAppMessages' with 'englishCrmMessages' in the type-safety section, and reconcile the two i18nProvider examples (resolveBrowserLocale vs 'en' default) into one canonical setup.

Fold the validation steps into the workflow itself (e.g. step 9: run the i18nProvider tests and the compile-time satisfies check before the PR checklist).

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious react-admin/Polyglot domain knowledge, but the 'Checklist Before Submitting an i18n PR' section restates the 15 rules nearly verbatim, and two i18nProvider setups appear (rule 12 vs. the 'i18nProvider Setup' section) with conflicting locale-detection approaches. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' — below anchor 4 because of the wholesale duplication.

3 / 5

Actionability

Code examples are concrete and copy-paste-ready throughout (i18nProvider setup, pluralization, merge order, language switcher), with minor gaps: the good placeholder example uses 'placeholder={placeholder}' with an undefined variable, the type-safety section defines 'englishCrmMessages' but derives types from 'englishAppMessages', and rule 8 mentions useEditController while the example uses useEditContext. Fits 'mostly executable guidance with minor gaps', not fully executable.

4 / 5

Workflow Clarity

A clear 8-step high-level workflow, a systematic per-file conversion process, tests, and a pre-PR checklist provide real validation, so the batch-operation cap does not apply. Not a 5 because validation sits at the end (checklist, tests) rather than as explicit validate-then-fix-then-retry checkpoints inside the workflow steps themselves.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the ~470-line body is monolithic: well-organized sections, but content that clearly belongs in separate files — the type-safe catalog patterns, the full language-switcher component, the test suite — is inlined with no one-level-deep references. This is 'some structure but content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

96%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' and 'Trigger this skill' clauses, and comprehensive natural-language trigger terms including casual phrasings. Third-person voice is maintained and there is no padding. The only soft spot is minor overlap risk from the dual react-admin/shadcn scoping.

DimensionReasoningScore

Specificity

Lists many concrete actions ('adding i18n support, creating translation files, translating hardcoded English strings in JSX, or reviewing i18n PRs') plus coverage areas ('namespace conventions, interpolation, pluralization, locale-aware formatting'), giving comprehensive coverage that matches the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' ('Guidelines for internationalizing… Covers namespace conventions… the full workflow for converting an English-only app to multi-language') and 'when' ('Use when adding i18n support…' and 'Trigger this skill whenever the user mentions i18n…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural synonyms — 'i18n, internationalization, translation, localization, locale switching, or multi-language' — plus casual user phrasings like "translate this component" and "add French support". No common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Firmly scoped to 'a react-admin or shadcn admin kit context' with distinct triggers, but the dual react-admin/shadcn framing creates minor overlap risk with a general shadcn UI or generic i18n skill — fits 'mostly distinct; minor overlap risk' better than the clear-niche anchor.

4 / 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

marmelab/react-admin

Path

.agents/skills/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.