CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ios-localization

Implement or review Apple-platform localization with String Catalogs, generated symbols, plurals, locale-aware formatting, package resources, and right-to-left layout. Use for multi-language UI, translation keys, localized values, or localization testing.

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

78%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.

A well-structured overview skill: lean directive sections with executable Swift examples, a useful mistakes/checklist pair, and exemplary progressive disclosure into two substantial reference files. The main weaknesses are small actionability gaps (no LocalizedStringResource or plural-config example) and a mild implement-path sequencing gap.

Suggestions

Add a one-line executable LocalizedStringResource example in the String Types section, since the Review Checklist mandates it but the body never demonstrates it.

Show a concrete plural-variation snippet (e.g., the interpolated key with zero/one/other states in the .xcstrings entry) instead of only mentioning the visual catalog editor.

Trim the Contents TOC (redundant at this length) and tighten Common Mistakes entries that restate generally known i18n pitfalls, keeping only the non-obvious ones like eager localization in static constants.

DimensionReasoningScore

Conciseness

The body is lean and directive with short code blocks, but minor tokens could be trimmed: the 10-line Contents TOC in a ~90-line file, and Common Mistakes entries like "Use leading/trailing" and "concatenating strings breaks syntax" that restate widely known i18n pitfalls. Efficient with minor trimmable instances matches score 4 rather than the every-token-earns-its-place level of 5.

4 / 5

Actionability

Swift snippets for extraction, String(localized:), plural interpolation, and FormatStyle currency/date/relative are executable and copy-paste ready, and the checklist is concrete. Minor gaps keep it below 5: LocalizedStringResource is mandated by the checklist but never shown in code, and plural-variation configuration is described only as happening "in the visual catalog editor" without a concrete example.

4 / 5

Workflow Clarity

For the review path the "Review Checklist" provides explicit checkpoints, and sections are logically ordered (catalog → string types → plurals → formatting → RTL), but the implement path is presented as parallel topic sections rather than a sequenced workflow. This lands between the simple-skill exception (5) and the checkpoint-gap level (3), fitting score 4's clear-guidance-with-minor-gaps anchor; no destructive/batch operations apply, so no cap.

4 / 5

Progressive Disclosure

The ~100-line body is a genuine overview with a TOC and a References section clearly signaling two one-level-deep files (references/formatstyle-locale.md, references/string-catalogs.md), which exist, total ~1,200 lines of real detail, and contain no nested file references. This matches the clear-overview/well-signaled-references anchor exactly.

5 / 5

Total

17

/

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.

The description is a strong two-sentence what/when pair: concrete capability list plus an explicit trigger clause, all in third-person imperative voice. The only gap is synonym coverage in the trigger clause (e.g., "translations", "i18n", ".xcstrings").

DimensionReasoningScore

Specificity

"Implement or review Apple-platform localization with String Catalogs, generated symbols, plurals, locale-aware formatting, package resources, and right-to-left layout" names the domain plus six concrete capabilities, matching the comprehensive-coverage anchor. It clearly exceeds score 4, which expects only several actions with minor gaps.

5 / 5

Completeness

The first sentence explicitly states what the skill does, and "Use for multi-language UI, translation keys, localized values, or localization testing" gives an explicit when-clause with concrete triggers. Not score 4, because the when-clause is already specific and trigger-anchored rather than merely present.

5 / 5

Trigger Term Quality

Trigger terms "multi-language UI, translation keys, localized values, or localization testing" are phrases users would plausibly say, but common variations like "translations", "i18n", "internationalization", and the ".xcstrings" extension are missing. This fits the good-coverage-with-a-few-missing-terms anchor rather than the comprehensive synonym/extension coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

"Apple-platform localization" scoped with String Catalogs, generated symbols, and RTL layout carves a clear niche unlikely to fire for non-Apple or non-localization skills. Conflict risk is minimal, matching the score 5 anchor.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

thienqo/ios-skills

Path

skills/ios-localization/SKILL.md

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.