CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/currency-formatting/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 reasonably lean overview with actionable, API-specific guidance and a well-signaled single reference file. Its weaknesses are redundancy — a background paragraph copied from the reference and overlapping Check/Code Review sections — and the absence of any verification checkpoint in the body even though a solid Verification section exists in references/rule.md.

Suggestions

Delete the opening locale-comparison paragraph (concepts Claude already knows, duplicated verbatim in references/rule.md) and merge the overlapping 'Check' and 'Code Review' sections into one, tightening the body.

Add a validation step or pointer at the end of the workflow, e.g. 'Verify fixes against the Verification section of references/rule.md (search for toFixed/regex comma insertion, confirm explicit locale args, check formatter caching).' — this would close the workflow_clarity gap.

Include one minimal inline example in 'Fix' (e.g., new Intl.NumberFormat(locale, { style: 'currency', currency }).format(amount)) so the primary action is executable without opening the reference.

DimensionReasoningScore

Conciseness

The opening paragraph ('a value formatted as "$1,234.56" in the US is written "1.234,56 $" in Germany') explains a concept Claude already knows and is duplicated verbatim in references/rule.md's 'Why It Matters' section, and the 'Check' and 'Code Review' sections overlap substantially. The rest is tight bullets, so this sits at 3 rather than 2 (no extensive padding) or 4 (the duplicated background paragraph and redundant sections are clear trim candidates).

3 / 5

Actionability

As an instruction-only skill the guidance is actionable and names exact APIs ('Replace manual number and currency formatting with Intl.NumberFormat and replace manual date formatting with Intl.DateTimeFormat, passing the user locale explicitly. Use Intl.Collator for locale-aware sorting'). Not 5 because the body contains no executable example and omits key specifics (e.g., how to 'resolve a supported fallback locale' — Intl.NumberFormat.supportedLocalesOf — which only appears in the reference file).

4 / 5

Workflow Clarity

The Check → Fix → Explain sections imply a review-fix-explain sequence, but no validation checkpoint appears in the body — the reference file's detailed 'Verification' section is never pointed to — and 'Code Review' duplicates 'Check', muddying the process. This matches anchor 3 (steps listed but checkpoints missing or implicit) rather than 4 (most checkpoints present).

3 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled, one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that resolves to a real file. Not 5 because the intro paragraph duplicates rule.md's 'Why It Matters' content and the reference's useful Verification section is not surfaced from the body — minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

87%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: it explicitly answers both what (check Intl API correctness) and when (reviewing formatting code for numbers, prices, dates) with concrete, natural trigger phrases in a tight single sentence. The only gap is missing common synonyms such as 'currency', 'locale', and 'i18n' that users of this domain would naturally say.

DimensionReasoningScore

Specificity

Concrete review targets are named ('utility functions, component props, or template strings that format numbers, prices, or dates') along with a concrete check ('whether Intl APIs are used correctly'). It stays at 4 rather than 5 because it describes essentially one composite review action across several targets rather than multiple distinct concrete actions.

4 / 5

Completeness

Both questions are explicitly answered: 'Use when reviewing utility functions, component props, or template strings that format numbers, prices, or dates' gives concrete when-triggers, and 'to check whether Intl APIs are used correctly' gives a clear what. Third-person/neutral voice is used with no fluff.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('format numbers, prices, or dates', 'Intl APIs', 'reviewing utility functions'). Not 5 because the most common synonyms for this domain — 'currency', 'locale', 'i18n', 'internationalization' — are absent; 'prices' only partially covers 'currency'.

4 / 5

Distinctiveness Conflict Risk

Clear niche — verifying correct Intl API usage in number/price/date formatting code — with distinct trigger terms that are unlikely to fire for unrelated skills. Overlap risk with a generic code-review skill is minimal.

5 / 5

Total

18

/

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/currency-formatting/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.