i18n-patterns
Implements internationalization with Rails I18n for multi-language support. Use when adding translations, managing locales, localizing dates/currencies, pluralization, or when user mentions i18n, translations, locales, or multi-language.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill i18n-patterns84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It uses third person voice correctly, provides specific concrete actions, includes comprehensive trigger terms that users would naturally use, and clearly delineates both what the skill does and when to use it. The Rails I18n focus makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'adding translations, managing locales, localizing dates/currencies, pluralization' - these are distinct, actionable capabilities within the Rails I18n domain. | 3 / 3 |
Completeness | Clearly answers both what ('Implements internationalization with Rails I18n for multi-language support') and when ('Use when adding translations, managing locales... or when user mentions i18n, translations, locales, or multi-language'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'i18n', 'translations', 'locales', 'multi-language', plus domain-specific terms like 'dates/currencies' and 'pluralization' that users working in this space would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche - specifically targets Rails I18n, not generic translation or localization. The combination of 'Rails', 'I18n', and specific triggers like 'locales' and 'pluralization' makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable Rails I18n reference with excellent code examples covering most common use cases. The main weaknesses are verbosity from showing parallel English/French examples repeatedly, and the lack of a clear step-by-step setup workflow with validation checkpoints. The content would benefit from being split into a concise overview with references to detailed examples.
Suggestions
Add a clear numbered workflow for initial i18n setup (e.g., 1. Configure application.rb, 2. Create locale structure, 3. Run i18n-tasks health to validate, 4. Add first translations, 5. Verify with test)
Move detailed YAML examples (full locale files) to a separate EXAMPLES.md or LOCALES_REFERENCE.md file, keeping only one concise example in the main skill
Add explicit validation step: 'After adding translations, run `bundle exec i18n-tasks health` to verify no missing keys before committing'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - showing both English and French versions of similar YAML structures repeatedly, and the project structure section duplicates information that becomes clear from the examples. Could be tightened by showing one complete example and noting the pattern. | 2 / 3 |
Actionability | Excellent executable code throughout - complete YAML configurations, working Ruby code for controllers/models/components, specific bash commands for i18n-tasks, and copy-paste ready examples for all major use cases including locale switching and testing. | 3 / 3 |
Workflow Clarity | The skill covers many patterns but lacks explicit workflow sequencing for setting up i18n from scratch. The checklist at the end helps, but there's no clear 'do this, then validate, then proceed' flow. Missing validation steps for checking translations work correctly before deployment. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting detailed examples (like full locale files) into separate reference files. No external file references are provided despite the content length warranting them. | 2 / 3 |
Total | 9 / 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (597 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 11 Passed | |
- 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.