currency-formatting

Use when reviewing utility functions, component props, or template strings that format numbers, prices, or dates to check whether Intl APIs are used correctly.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/currency-formatting/SKILL.md

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, single-purpose review skill that delegates detail appropriately to a real reference file and gives concrete flagging guidance. It could be tightened by removing the duplicated locale background and strengthened by surfacing the verification checklist inline.

Suggestions

Trim the opening 'Number and currency formatting rules differ...' paragraph, which duplicates content already in references/rule.md and explains locale basics Claude already knows.

Bring the Verification checklist (or a condensed version) into the body so validation steps are visible without opening the reference, raising workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly lean with tight Quick Reference bullets and short Check/Fix/Explain sections, but the opening locale-example paragraph restates background Claude largely knows and duplicates content in references/rule.md.	4 / 5
Actionability	Gives concrete, specific review guidance ('flag locale-sensitive sorting that uses plain string comparison instead of Intl.Collator', 'resolve a supported fallback locale', 'Flag any hardcoded currency symbols, separators, or date format strings'), though no inline code examples are provided.	4 / 5
Workflow Clarity	A single-purpose review skill with a clear Check/Fix/Explain/Code Review sequence that is unambiguous, but the body itself lacks the explicit verification checkpoints that live in references/rule.md.	4 / 5
Progressive Disclosure	Body is a concise overview with a single, clearly signaled one-level-deep reference to references/rule.md (verified to exist), and detailed examples/code are appropriately split into that file.	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 focused, well-triggered description that clearly scopes the skill to reviewing locale-aware formatting code. Its main limitation is a thin 'what' that lists review targets rather than multiple distinct capabilities, and a few missing natural synonyms.

Suggestions

Add the natural terms users say — 'currency', 'locale', 'i18n' — to broaden trigger coverage.

Expand the 'what' to name multiple distinct actions (e.g., flag hardcoded symbols, verify explicit locale arguments, check Intl.Collator usage) rather than a single 'check whether' clause.

Dimension	Reasoning	Score
Specificity	Names several concrete review targets ('utility functions, component props, or template strings', 'Intl APIs are used correctly') but they are all variants of a single review action rather than a comprehensive multi-action list.	4 / 5
Completeness	Explicitly answers both what ('check whether Intl APIs are used correctly') and when ('Use when reviewing utility functions, component props, or template strings that format numbers, prices, or dates'), though the 'what' side describes a single review action rather than a rich capability set.	4 / 5
Trigger Term Quality	Includes natural developer terms ('utility functions', 'component props', 'template strings', 'numbers, prices, or dates', 'Intl APIs') but omits common synonyms a user might say such as 'currency', 'locale', or 'i18n'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Intl-based formatting review) with distinct, specific triggers tied to number/price/date formatting, giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 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/currency-formatting/SKILL.md
Commit: 30756a7

Reviewed: 20 days 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.