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:ThibautBaissac/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/skillAgent success when using this skill
Validation 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', 'locales', and 'i18n' creates a unique trigger profile 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 all major use cases from basic setup to testing. The main weaknesses are verbosity from showing parallel English/French examples repeatedly, and lack of explicit workflow guidance for implementing i18n in a new or existing project. The content would benefit from being split into a concise overview with links to detailed reference files.
Suggestions
Add a workflow section with numbered steps for adding i18n to an existing Rails app, including validation checkpoints (e.g., 'Run i18n-tasks health after adding translations')
Reduce redundancy by showing one complete locale file example and noting 'Follow same pattern for other locales' rather than showing EN and FR versions of each section
Split detailed YAML examples and testing setup into separate reference files (e.g., LOCALE_EXAMPLES.md, TESTING.md) and link from the main skill
| 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 checklist at the end provides a good summary, but the document lacks explicit sequencing for setting up i18n from scratch. No validation checkpoints are provided - for example, no guidance on verifying translations work before deploying, or how to catch missing translations during development. | 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, testing setup) into separate reference files. The structure is good but everything is inline. | 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.