CtrlK
BlogDocsLog inGet started
Tessl Logo

check-translations-pr

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.

80

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, action-oriented skill body: executable commands at every step, explicit stop-and-ask validation checkpoints, and a precise output format. It respects Claude's competence with no redundant concept explanations and is well-structured for a simple linear task.

DimensionReasoningScore

Conciseness

The body is lean: a one-line purpose statement, a four-step outline, then per-step executable commands with no padding or explanation of concepts Claude already knows. Not a 2 because every line earns its place and there is no unnecessary exposition.

3 / 3

Actionability

Each step ships copy-paste-ready shell commands (gh pr diff piped through grep/sed, ls piped through grep) plus an exact output template. Not a 2 because the guidance is fully executable rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

Four clearly sequenced steps with explicit validation checkpoints: "stop immediately and ask" for a missing PR number and "report that and stop" when no string keys are found. Not a 2 because checkpoints are explicit (not implicit), and the operation is read-only analysis so the destructive-cap is not triggered.

3 / 3

Progressive Disclosure

A single well-organized SKILL.md with no bundle files and no nested references; content is appropriately inline for a simple linear workflow. Not a 2 because sections are clearly delimited and there is nothing that should be split out into separate files.

3 / 3

Total

12

/

12

Passed

Description

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.

A strong, third-person description that pairs two concrete capabilities with extensive, natural trigger phrasing covering direct asks, PR references, and ship-readiness cues. It clearly answers both what the skill does and when to invoke it with minimal risk of conflicting with other skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Check whether a translations PR provides full language coverage" and "identify which languages are still missing" — matching the anchor for listing several specific actions. It is not a 2 because both actions are concrete and verifiable rather than a single domain mention.

3 / 3

Completeness

Explicitly answers both what (check full language coverage, identify missing languages) and when ("Use this whenever the user asks about translation status…" and "Also trigger when the user pastes a PR number or URL"). Not a 2 because the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

Covers natural user phrasings such as "translation status", "whether translations are complete or ready", "which languages are missing", "verify a translations PR before merging", a pasted "PR number or URL", and "are we good to ship?". Not a 2 because it spans many common variations a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (translations PR language coverage) with distinct triggers unlikely to fire for unrelated skills. Not a 2 because the scope is narrow and the triggers are specific to translation/string-change contexts.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
duckduckgo/Android
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.