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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%

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

A concise, well-structured overview with clean progressive disclosure to a single real reference file. It is weakened by mostly descriptive (rather than executable) guidance in the body and an implicit rather than explicitly sequenced, checkpointed workflow.

Suggestions

Add one concrete, copy-paste-ready snippet in the body (e.g. a small locale-aware image lookup map with a neutral fallback) so the core action is executable without opening the reference.

Turn the Check/Fix/Explain/Code Review sections into an explicitly numbered sequence with a validation checkpoint (e.g. 'confirm no embedded text remains; verify a neutral fallback exists for every locale-specific image').

In Code Review, give a short concrete checklist of what to flag (hardcoded image paths, flag-as-language icons, gesture icons, embedded-text images) rather than narrating the categories.

Dimension	Reasoning	Score
Conciseness	The body is lean — short Quick Reference, Check/Fix/Explain/Code Review sections — and does not explain concepts Claude already knows; the only repeated framing ('thumbs-up is vulgar...', 'checkmark means wrong') reinforces the rule rather than padding.	3 / 3
Actionability	Guidance is largely descriptive ('Identify image assets...', 'Replace culturally specific images...', 'implement a locale-aware image lookup with a neutral fallback') rather than executable; no concrete lookup-map example or code pattern appears in the body, with detail deferred to the reference file.	2 / 3
Workflow Clarity	The Check/Fix/Explain/Code Review sections imply a loose sequence but there are no explicit validation checkpoints or feedback loops; steps are present but ordering and verification are implicit.	2 / 3
Progressive Disclosure	The body is a tight overview that delegates full implementation to a single one-level-deep, well-signaled reference (references/rule.md), which exists as a real file — appropriate splitting and easy navigation.	3 / 3
	Total	10 / 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, concise description with an explicit 'Use when' trigger, concrete named actions, and natural terminology scoped to a distinct i18n-imagery niche. It answers both what and when without padding.

Dimension	Reasoning	Score
Specificity	Names concrete actions across a defined domain — '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' — covering identify, override, and replace.	3 / 3
Completeness	Explicit 'Use when...' trigger answers when, and the rest of the sentence answers what (identify culture-specific content, provide locale overrides or neutral alternatives); both are present and explicit.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered: 'image assets', 'icon libraries', 'illustrations', 'culture-specific content', 'locale overrides', 'neutral alternatives' — terms a reviewer would plausibly say.	3 / 3
Distinctiveness Conflict Risk	The niche is clearly bounded to i18n imagery review; the culture/locale framing makes it unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/locale-images/SKILL.md
Commit: 48405aa

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.