i18n
Bilingual EN/FR content validation using next-intl. Use when adding translated content, testing language switching, or validating message key coverage before deployment.
97
Quality
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
89%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-structured description with explicit trigger guidance and good distinctiveness. The main weakness is the lack of specific concrete actions - 'validation' could be more detailed to explain what operations are actually performed (e.g., detecting missing keys, comparing translations, validating placeholders).
Suggestions
Expand the capabilities with specific actions like 'Detects missing translation keys, validates placeholder consistency, compares EN/FR message files' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (bilingual EN/FR content validation) and the technology (next-intl), but lacks specific concrete actions. 'Validation' is somewhat vague - doesn't specify what validation entails (e.g., checking missing keys, format validation, placeholder matching). | 2 / 3 |
Completeness | Clearly answers both what (bilingual EN/FR content validation using next-intl) and when (adding translated content, testing language switching, validating message key coverage before deployment) with explicit 'Use when' clause and multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms: 'translated content', 'language switching', 'message key coverage', 'EN/FR', 'bilingual', 'next-intl'. These are terms users working with internationalization would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology (next-intl), specific language pair (EN/FR), and specific use cases. Unlikely to conflict with generic translation or i18n skills due to the narrow scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers bilingual validation with concrete, actionable guidance. The validation checklist provides clear steps with executable commands and expected outputs. The structure balances quick reference needs with detailed examples, and appropriately references supporting files without over-explaining.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Each section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable commands (node scripts, npm commands), copy-paste ready code examples showing both bad and good patterns, and specific file paths. The validation checklist is immediately actionable. | 3 / 3 |
Workflow Clarity | Clear numbered validation checklist with explicit steps. The workflow progresses logically from key coverage to hardcoded strings to formatting to language switching. Expected output examples provide validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, quick reference table for common tasks, and appropriate references to supporting files and related skills. Content is appropriately scoped without unnecessary nesting. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.