Check whether a translations PR provides full language coverage for all translatable strings it contains, and identify which languages are still missing. Use this whenever the user asks about translation status, whether translations are complete or ready, which languages are missing, or wants to verify a translations PR before merging. Also trigger when the user pastes a PR number or URL alongside any mention of translations, or asks something like "are we good to ship?" in a context that involves string changes.
100
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 strong skill description that clearly articulates both what the skill does and when it should be triggered. It provides excellent natural trigger terms covering multiple user phrasings, from formal ('translation status') to casual ('are we good to ship?'). The description occupies a clear niche with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Check whether a translations PR provides full language coverage', 'identify which languages are still missing'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Check whether a translations PR provides full language coverage...identify which languages are still missing') and when ('Use this whenever the user asks about translation status...') with explicit, detailed trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'translation status', 'translations are complete or ready', 'which languages are missing', 'translations PR before merging', 'PR number or URL', 'are we good to ship?', 'string changes'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: translation coverage checking for PRs. The combination of 'translations', 'PR', 'language coverage', and 'missing languages' creates a clear, specific domain unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 an excellent, well-crafted skill. It provides precise, executable commands for each step, includes critical stop-points to prevent wasted work, and specifies an exact output format. The content is concise, assumes Claude's intelligence, and covers edge cases without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what translations are, what PRs are, or how grep works. Every section serves a direct purpose, and the instructions assume Claude's competence with shell commands and Git workflows. | 3 / 3 |
Actionability | Every step includes exact, copy-paste-ready bash commands. The output format is fully specified with a concrete template. There's no pseudocode or vague direction — Claude knows exactly what to run and what to produce. | 3 / 3 |
Workflow Clarity | The four steps are clearly sequenced with explicit stop-and-ask checkpoints (no PR number → stop, no string keys → stop). The comparison step between covered and supported languages is a validation checkpoint. The workflow handles edge cases and has clear gating between steps. | 3 / 3 |
Progressive Disclosure | For a focused, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear section headers, horizontal rules separating steps, and logical grouping. No bundle files are needed for this scope. | 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.
adccd8d
Table of Contents
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.