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

57%

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

The skill is well-structured with a clear overview and a genuine shallow reference to rule.md, but the body is instruction-only: it explains locale concepts Claude knows and lacks inline executable code examples or validation steps for the suggested refactor.

Suggestions

Trim the opening paragraph's explanation of locale formatting differences and hardcoding costs; Claude already knows this, so keep only the rule statement.

Add one small executable example (e.g. new Intl.NumberFormat(locale, { style: 'currency', currency }).format(amount)) inline so the Fix step is copy-paste ready rather than deferred entirely to the reference.

Add a verification checkpoint after Fix, such as comparing formatter output against an expected locale-specific string, to give the workflow an explicit pass/fail step.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the opening paragraph re-explains locale formatting differences ('$1,234.56' vs '1.234,56 ¥') and why hardcoding is bad — context Claude largely already knows and could be tightened.	2 / 3
Actionability	Guidance names the APIs to use (Intl.NumberFormat, Intl.DateTimeFormat, Intl.Collator) but provides no executable code in the body; concrete examples are deferred to references/rule.md, leaving the inline instructions descriptive rather than copy-paste ready.	2 / 3
Workflow Clarity	The Check/Fix/Explain/Code Review sections give a recognizable sequence, but there are no explicit validation checkpoints for verifying the refactor (e.g. confirming output matches locale expectations) and the 'Check' step lists what to find without a clear pass/fail criterion.	2 / 3
Progressive Disclosure	The body is a concise overview with a clearly signaled one-level-deep pointer — 'see references/rule.md' — and the referenced file exists, keeping navigation shallow and easy to follow.	3 / 3
	Total	9 / 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.

The description is specific, well-triggered, and complete, with concrete review targets and an explicit 'Use when' clause that distinguishes it from other skills. It uses third person and avoids fluff.

Dimension	Reasoning	Score
Specificity	Names concrete actions — 'reviewing utility functions, component props, or template strings that format numbers, prices, or dates to check whether Intl APIs are used correctly' — listing multiple specific targets (functions, props, template strings) and a concrete check (Intl API usage).	3 / 3
Completeness	Opens with an explicit 'Use when reviewing...' trigger and states the action (check whether Intl APIs are used correctly), answering both what and when clearly.	3 / 3
Trigger Term Quality	Natural user-facing terms — 'numbers, prices, or dates', 'format', 'Intl APIs', 'reviewing utility functions, component props, or template strings' — cover the phrasings a developer would actually say when requesting this review.	3 / 3
Distinctiveness Conflict Risk	Scoped to Intl API usage in formatting code, a clear niche with distinct triggers unlikely to fire 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/currency-formatting/SKILL.md
Commit: 48405aa

Reviewed: about 8 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.