CtrlK
BlogDocsLog inGet started
Tessl Logo

add-translation-strings

**EXECUTION (runbook) SKILL** — Add or change a user-facing UI string in Git Extensions and regenerate the translation catalog. USE FOR: adding a TranslationString, changing a control/menu/toolbar caption, any UI text change that must update English.xlf. DO NOT USE FOR: non-UI/log/exception-internal strings, or general feature work. Triggers: "add a UI string", "change this label", "regenerate English.xlf", "update-loc".

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

An exemplary runbook body: concise, fully executable, correctly sequenced with explicit verification and hard rules, and appropriately structured as a single file with one clearly signaled background reference. No material improvements identified.

DimensionReasoningScore

Conciseness

The body is 33 lean lines with zero concept explanations: every sentence is an operational instruction, file path, or hard rule. Nothing pads or restates what Claude already knows, matching the "every token earns its place" anchor.

5 / 5

Actionability

Guidance is fully executable: the exact declaration pattern `private readonly TranslationString _x = new("...")`, copy-paste commands (`dotnet build /v:q`, `.\update-loc.cmd` from the repo root), concrete destination files (TranslatedStrings.cs, English.xlf), and SmartFormat placeholder syntax ("{0:item|items}").

5 / 5

Workflow Clarity

A numbered 4-step sequence with an explained ordering constraint (build before regenerating, because "the generator reflects over the built assemblies"), an explicit Verify section with two checkable outcomes (git status shows English.xlf staged; the string appears in the file), and STOP conditions that state the failure consequence ("CI will fail on a stale English.xlf"). Validation is present, so the missing-validation cap does not apply.

5 / 5

Progressive Disclosure

This is a single-file skill with no bundle directories (references/, scripts/, assets/ do not exist) and no content that warrants splitting. Under 50 lines, it is well-organized into Steps / Verify / STOP sections with one clearly-signaled one-level-deep background link (translation-system.md), which per the simple-skills scoring note merits full marks.

5 / 5

Total

20

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 description that states concrete capabilities, explicit use and do-not-use boundaries, and natural trigger phrases in third person. Its only weakness is modest synonym coverage in the trigger list. Adding localization-related terms would close that gap.

Suggestions

Add common natural synonyms to the Triggers list, e.g. "localize", "add a localized string", "update translations", so users who phrase the request in localization terms still match.

Consider adding the plural/variant file mention ".xlf" alongside "English.xlf" to broaden file-extension trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Add or change a user-facing UI string", "regenerate the translation catalog", "adding a TranslationString", "changing a control/menu/toolbar caption" — comprehensively covering the skill's scope with no vague filler. It exceeds the level-4 anchor ("minor gaps in coverage") since every capability of the runbook is named.

5 / 5

Completeness

It explicitly answers both what ("Add or change a user-facing UI string in Git Extensions and regenerate the translation catalog") and when ("USE FOR: adding a TranslationString, changing a control/menu/toolbar caption, any UI text change that must update English.xlf") with concrete trigger phrases, plus a DO NOT USE FOR exclusion clause.

5 / 5

Trigger Term Quality

Triggers "add a UI string", "change this label", "regenerate English.xlf", and "update-loc" are natural phrases a user would say and include the concrete file name. However common synonyms such as "localize", "translation", or "localization" are absent, so coverage is good but a few natural terms are missing — matching the level-4 anchor rather than the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — the Git Extensions UI-string-to-English.xlf pipeline — with distinct triggers and an explicit exclusion for "non-UI/log/exception-internal strings, or general feature work", minimizing risk of triggering for the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
gitextensions/gitextensions
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.