CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

locale-images

Use when reviewing image assets, icon libraries, or components that render illustrations to identify culture-specific content that may need locale overrides or replacement with neutral alternatives.

Quality

82%

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.

The body is a well-organized, appropriately brief overview for a single-purpose review skill: concrete identification and remediation checklists with a clean hand-off to one real reference file. The main improvable spots are slight redundancy between the intro/Quick Reference and later sections, and verification steps that live only in the reference.

Suggestions

Trim the intro paragraph's cultural-symbolism examples (thumbs-up, checkmark) since they are repeated nearly verbatim in references/rule.md's 'Why It Matters' section and largely restate knowledge Claude already has.

Dedupe Quick Reference bullets that restate Fix/Code Review content ('Never embed text inside images' vs. flagging 'any image that contains embedded text') so each section adds new information.

Surface the verification/audit checklist from references/rule.md with a one-line pointer in the body (e.g., after Fix) so the review workflow explicitly ends with a verification step.

DimensionReasoningScore

Conciseness

The body is lean and directive (Check/Fix/Explain/Code Review sections), but the intro paragraph re-explains cultural symbolism Claude already knows ('a thumbs-up is a vulgar gesture in parts of the Middle East and West Africa, and a checkmark means "wrong" in Japan') and several Quick Reference bullets duplicate the Fix and Code Review sections. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the level-5 'every token earns its place.'

4 / 5

Actionability

Concrete, specific checklists ('hand gestures, color symbolism, animals, or religious imagery'; 'hardcoded image paths, hand gesture icons, flag icons used to represent languages, and any image that contains embedded text') with executable code delegated to the clearly signaled references/rule.md. Not 5 because the body itself contains no code or examples (e.g., the locale-lookup pattern is only named, not shown); not 3 because the guidance is specific and complete enough to act on, with full details one reference away.

4 / 5

Workflow Clarity

A coherent Check → Fix → Explain → Code Review sequence with each stage unambiguous, and no destructive/batch operation requiring validation loops. Minor gap: the verification/audit steps exist only in references/rule.md and are not surfaced in the body, which keeps it at 'clear sequence with minor validation gaps' rather than the level-5 explicit-checkpoint anchor.

4 / 5

Progressive Disclosure

A concise, well-sectioned overview body with a single well-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and the bundle confirms that file exists and holds the detailed code, cultural pitfalls table, and framework guidance. Content is appropriately split with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

78%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 with an explicit and specific 'Use when' trigger clause paired with a clearly stated purpose, in proper third-person form. Its main limitations are moderate action coverage (one identify action rather than several) and trigger terms that omit common i18n vocabulary like 'internationalization' or 'localization'.

Suggestions

Enumerate the concrete actions the skill performs (e.g., 'Reviews image assets and icon components, flags culturally specific imagery such as gestures and flag-for-language icons, and replaces them with neutral alternatives or locale-keyed variants') to raise specificity from one compressed action to several.

Add natural trigger synonyms users would say, such as 'i18n', 'internationalization', 'localization', or 'SVG icons', to broaden natural keyword coverage.

Tighten the trigger clause so it fires on cultural/locale review contexts (e.g., 'Use when reviewing images, icons, or illustrations for internationalization or cultural sensitivity') to reduce overlap with generic asset-review skills.

DimensionReasoningScore

Specificity

The description names the domain ('image assets, icon libraries, or components that render illustrations') and one concrete action ('identify culture-specific content that may need locale overrides or replacement with neutral alternatives'), matching 'names domain and 1-2 concrete actions, but not comprehensive.' Not 2 because the action is specific rather than generic; not 4 because it does not list several distinct actions (e.g., reviewing, flagging, and replacing are compressed into one clause).

3 / 5

Completeness

Both parts are explicit: the 'when' is a clear trigger clause ('Use when reviewing image assets, icon libraries, or components that render illustrations') and the 'what' states the concrete action ('to identify culture-specific content that may need locale overrides or replacement with neutral alternatives'). This matches the anchor requiring both what AND when with concrete trigger phrases, with no weakness in either half.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'image assets', 'icon libraries', 'illustrations', 'culture-specific', 'locale overrides', 'neutral alternatives' are phrases a developer would plausibly use. Not 5 because common synonyms and extensions are missing ('i18n', 'internationalization', 'localization', 'SVG', 'cultural'); not 3 because multiple relevant natural terms are present rather than a single generic one.

4 / 5

Distinctiveness Conflict Risk

The cultural/locale-imagery niche is distinct, but the opening trigger clause 'Use when reviewing image assets, icon libraries, or components that render illustrations' is broad enough to overlap with generic image-optimization or asset-review skills before the cultural qualifier narrows it. Fits 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict level 5.

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/locale-images/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.