CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pluralization

Use when reviewing string concatenation involving counts, translation key lookups, or i18n library configurations to check whether plural forms are handled correctly for all target locales.

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/pluralization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well-structured as an overview with excellent progressive disclosure to a substantive reference file, but it pads space with pluralization facts Claude already knows and lacks a validation checkpoint in its check→fix workflow. Tightening the intro and surfacing the reference's verification steps would lift the weakest dimensions.

Suggestions

Cut or trim the intro paragraph and the Quick Reference's plural-form counts (e.g., 'English has 2 plural forms but Arabic has 6 and Russian has 3') — Claude already knows CLDR plural category rules, and they duplicate references/rule.md's 'Why It Matters' section.

Add an explicit verification step to the workflow (e.g., 'Verify: confirm every plural category key required by each target locale is present in the translation files, and render count components with a locale like Arabic at counts 0, 1, 2, 5, 11 — see references/rule.md') so the batch check→fix loop has a validation checkpoint.

Include one short inline example of the correct pattern in the Fix section (e.g., a two-line ICU snippet like '{count, plural, one {# item} other {# items}}') so the core replacement syntax is visible without opening the reference.

DimensionReasoningScore

Conciseness

The intro paragraph ('Pluralization rules vary dramatically across languages — what works as a simple singular/plural branch in English produces grammatically wrong output in Arabic, Russian, Polish...') and Quick Reference facts ('English has 2 plural forms but Arabic has 6 and Russian has 3') re-explain CLDR concepts Claude already knows and duplicate references/rule.md's 'Why It Matters' section. Mostly efficient, but the known-concept padding keeps it below the 4 anchor.

3 / 5

Actionability

The Check/Fix/Code Review sections name specific APIs (Intl.PluralRules, ICU MessageFormat, react-intl, i18next) and concrete anti-patterns (count concatenation, binary singular/plural ternaries), and defer to references/rule.md which contains complete executable code. Not a 5 because the body itself has no inline example of the replacement pattern; not a 3 because the guidance is concrete and the full executable detail is one clearly signaled file away.

4 / 5

Workflow Clarity

A rough sequence exists (Check → Fix → Explain → Code Review) but there are no validation checkpoints in the body, even though the workflow is a batch codebase-wide review ('Find all places in this codebase...'). The verification steps exist in references/rule.md but are not surfaced or linked from the body, matching 'sequence present but checkpoints missing or implicit' — which also caps it at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

The body is a lean overview with a single, clearly signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and that file exists in the bundle and contains the implementation detail without further nested internal references. This matches the clear-overview anchor exactly.

5 / 5

Total

15

/

20

Passed

Description

83%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 trigger-style description that explicitly pairs concrete review contexts with a specific checking action in a well-defined i18n niche. Keyword coverage is good but would benefit from synonyms like 'pluralization' and framework names.

DimensionReasoningScore

Specificity

Names several concrete review targets ('string concatenation involving counts, translation key lookups, or i18n library configurations') and a concrete action ('check whether plural forms are handled correctly for all target locales'), but centers on a single checking action rather than a comprehensive list of capabilities, so it falls between the 3 and 5 anchors.

4 / 5

Completeness

Explicitly answers both parts: 'Use when reviewing string concatenation involving counts, translation key lookups, or i18n library configurations' (when, with concrete trigger phrases) and 'to check whether plural forms are handled correctly for all target locales' (what). Not a 4 because the 'when' is not weak or implicit — both elements are explicit with concrete triggers.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say ('plural forms', 'locales', 'i18n', 'translation key', 'string concatenation'), but common synonyms like 'pluralization', 'plurals', and framework names (react-intl, i18next) are missing, which matches the 'good coverage, a few natural terms missing' anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

The plural-form/i18n locale niche is distinct with clear triggers, but the broad 'string concatenation involving counts' trigger creates minor overlap risk with general code-review and string-formatting skills, matching 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict anchor.

4 / 5

Total

17

/

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/pluralization/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.