CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The SKILL.md body is a lean, well-structured overview that gives concrete, actionable review/fix guidance and cleanly defers code examples and framework details to a one-level-deep reference. The Check→Fix→Code Review workflow is clear and unambiguous for a single-purpose review skill.

DimensionReasoningScore

Conciseness

The ~34-line body is lean — tight Quick Reference bullets and short Check/Fix/Explain/Code Review directives — and offloads detail to references; the single motivating intro sentence is brief enough to earn its place rather than the padded level-2 case.

3 / 3

Actionability

Gives concrete, specific guidance — "Find all places... where a count value is concatenated with a string or where only singular/plural branching is used" and "Replace... with Intl.PluralRules-based key selection or ICU MessageFormat plural syntax" — naming exact patterns to find and fix; per the instruction-only scoring note, the absence of inline code is not penalized since the guidance is actionable.

3 / 3

Workflow Clarity

Presents a clear, unambiguous review workflow (Quick Reference → Check → Fix → Explain → Code Review) where the Code Review section acts as the verification pass; for this single-purpose review skill the simple-skills note supports a top score, and it is not a destructive/batch operation that the cap-at-2 rule targets.

3 / 3

Progressive Disclosure

The body is a well-organized overview that signals a single one-level-deep reference — "see references/rule.md" — for full implementation details, and that file exists, matching the clear-overview-with-well-signaled-reference anchor rather than the inline-bloated or under-signaled lower levels.

3 / 3

Total

12

/

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 concise, third-person imperative in standard trigger form, and cleanly states both what the skill does and when to use it with concrete, natural review terms. It is distinctive within the i18n pluralization niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete review actions — "reviewing string concatenation involving counts", "translation key lookups", and "i18n library configurations" — plus the explicit goal of checking plural forms, matching the "lists multiple specific concrete actions" anchor rather than the partial level 2.

3 / 3

Completeness

Opens with an explicit "Use when reviewing..." trigger (the when) and states the what — "to check whether plural forms are handled correctly for all target locales" — clearly answering both what and when, which the level-2 anchor only half-satisfies.

3 / 3

Trigger Term Quality

Uses natural developer vocabulary a user would say when hitting this problem — "string concatenation", "counts", "translation key lookups", "i18n library configurations", "plural forms", "target locales" — giving good coverage rather than the sparse level-2 set.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (i18n plural handling) with distinct triggers around count concatenation and plural forms, making it unlikely to fire for an unrelated skill; not the generic, overlapping level-2 case.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.