CtrlK
BlogDocsLog inGet started
Tessl Logo

add-localization

Add or update a language translation in the privacy policy generator. Trigger when user says: "add {language} translation", "add locale", "translate to {language}", "add localization for {language}", or when a user wants to contribute a new language.

72

Quality

88%

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

87%Weight 40%Scale 1-3

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

A concise, highly actionable skill body with a clear numbered workflow and well-organized sections. The one real weakness is a build-command inconsistency between the workflow step (make build) and the validation checklist (npm run build), which leaves the verification gate ambiguous.

Suggestions

Reconcile the build command: the Validation Checklist says "npm run build succeeds" but step 4 uses `make build` — pick one and use it consistently so the verification step is unambiguous.

Add a brief inline feedback note at the build/validation step (e.g., "if the build or JSON validation fails, fix the error and re-run") to turn the checklist into an explicit validate→fix→retry loop.

Consider noting which ISO 639-1 codes require region suffixes (e.g., zh vs zh-CN) since the locale switcher and meta handling may depend on the exact code format.

DimensionReasoningScore

Conciseness

The body is lean: numbered steps with direct shell commands and tight JSON examples, no explaining of concepts Claude already knows, and the Important Notes carry domain-specific gotchas (meta.* via JS, thirdpartyservices.yml) that earn their tokens.

3 / 3

Actionability

Concrete, copy-paste-ready commands (`cp src/locales/en.json src/locales/{code}.json`, `make build`) and correct/wrong JSON examples give fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

Steps are clearly numbered and a validation checklist exists, but the checklist gates on "npm run build succeeds" while step 4 instructs `make build" — an inconsistent validation checkpoint, which the rubric treats as a validation gap capping this dimension.

2 / 3

Progressive Disclosure

At ~57 lines with no external references needed (none exist in the bundle), the well-organized Quick Steps / Validation Checklist / Important Notes sections satisfy the simple-skill allowance for a top score without separate files.

3 / 3

Total

11

/

12

Passed

Description

90%Weight 40%Scale 1-3

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: it clearly states a specific domain, provides explicit natural trigger phrases, and answers both what and when. The only soft spot is specificity, since the capability is essentially a single add/update-translation operation rather than a broad set of distinct actions.

DimensionReasoningScore

Specificity

"Add or update a language translation in the privacy policy generator" names a concrete domain and two verbs, but it is essentially a single operation (translation) rather than the multiple distinct concrete actions the top anchor expects.

2 / 3

Completeness

It states what the skill does (add/update a language translation in the privacy policy generator) and gives an explicit "Trigger when user says..." clause answering when to use it, matching the top anchor.

3 / 3

Trigger Term Quality

Explicit natural phrases users would say are listed ("add {language} translation", "add locale", "translate to {language}", "add localization for {language}"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The narrow privacy-policy-generator localization domain with its distinct trigger phrases makes it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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
nisrulz/app-privacy-policy-generator
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.