CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

text-expansion

Use when reviewing CSS for fixed dimensions, truncation, or overflow rules on elements that render translatable strings.

Quality

83%

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

85%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, efficient overview body with an appropriately deferred one-level reference. The Check->Fix flow is clear for a simple single-purpose skill; the only notable gap is that the pseudo-locale testing advice names no concrete mechanism or example in the body itself.

DimensionReasoningScore

Conciseness

The body is lean, assumes competence, and avoids explaining basics; every section carries domain facts (expansion percentages, logical-property swaps). It sits at 4 rather than 5 because the Check and Code Review sections partially duplicate each other's pattern lists, and the trailing 'Rule page: URL' duplicates the frontmatter url metadata; it is well above 3 since there is no real padding.

4 / 5

Actionability

The guidance is concrete and directly followable: 'Replace fixed inline-size with min-inline-size', 'remove overflow: hidden from interactive elements', and an exact scan list ('fixed widths, overflow: hidden, white-space: nowrap, text-overflow: ellipsis on buttons, labels, navigation items, and headings'). It misses 5 because 'add a pseudo-locale build step' and 'Test with a pseudo-locale that inflates strings' name no concrete mechanism (e.g., en-XA, a specific command) in the body, deferring all implementation to the reference.

4 / 5

Workflow Clarity

This is a simple, single-purpose review skill under 50 lines, and its Check -> Fix sequence is unambiguous with a precisely delimited single action (the Code Review section enumerates exactly what to scan). The simple-skill exception applies, and no destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that was verified to exist and contain exactly those materials. Content is appropriately split between the overview and the reference, matching the top anchor exactly.

5 / 5

Total

18

/

20

Passed

Description

75%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 solid, third-person description with an explicit 'Use when' clause and a well-defined niche. Its main weakness is trigger coverage: it lacks the natural synonyms (translation, i18n, localization, text expansion) users would likely say, and the when-clause mirrors the what instead of naming distinct user contexts.

Suggestions

Add natural trigger synonyms such as 'translation', 'i18n', 'localization', or 'text expansion' so the skill surfaces when users phrase the need differently.

Make the when-clause name concrete user contexts (e.g., 'Use when the user mentions translations, internationalization, or overflowing/truncated UI text') instead of restating the review scope.

Consider mentioning the pseudo-locale testing capability in the description, since it is a core part of the skill the description currently omits.

DimensionReasoningScore

Specificity

The description names the domain ('reviewing CSS') and several concrete review targets ('fixed dimensions, truncation, or overflow rules on elements that render translatable strings'), matching the anchor for several specific actions with minor gaps. It stays at 4 rather than 5 because it covers a single verb ('reviewing') and omits capabilities the skill actually has (pseudo-locale testing guidance), and is above 3 because it lists more than 1-2 concrete, explicit focus areas.

4 / 5

Completeness

Both what ('reviewing CSS for fixed dimensions, truncation, or overflow rules on elements that render translatable strings') and when (an explicit 'Use when...' clause, satisfying the cap guideline) are present. It falls short of 5 because the when-clause restates the what rather than offering distinct concrete trigger phrases (e.g., 'when the user mentions translation or i18n'), and exceeds 3 because the when is explicit, not merely implied.

4 / 5

Trigger Term Quality

Natural terms users would say are present ('reviewing CSS', 'truncation', 'overflow rules', 'translatable strings'), giving good keyword coverage. It is not 5 because common synonyms like 'translation', 'i18n', 'localization', and 'text expansion' are missing, and not 3 because the included keywords are relevant and naturally phrased rather than partial.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (i18n text expansion within CSS review) via the 'translatable strings' qualifier, but 'fixed dimensions, truncation, or overflow rules' could still overlap with general CSS code-review skills. This matches 'mostly distinct; minor overlap risk with closely related skills' — above 3 because the i18n qualifier keeps it distinguishable, below 5 because of the overlap with generic CSS review triggers.

4 / 5

Total

16

/

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/text-expansion/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.