CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

font-size

Use when applies to all CSS `font-size` declarations, particularly those using `px` units for body text, UI labels, and navigation. Use when auditing mobile responsiveness and accessibility compliance. Check for `font-size` in media queries targeting small screens.

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

Quality

Content

77%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 well-structured, actionable audit workflow with exact thresholds, conversion math, an explicit 200% zoom verification step, and a clean one-level-deep pointer to references/rule.md for code examples. Its main weakness is redundancy: the WCAG 1.4.4 requirement is stated twice and the Explain section re-teaches px-vs-rem concepts Claude already knows, which costs tokens without adding guidance.

Suggestions

Remove the duplicated WCAG 2.1 SC 1.4.4 explanation — it appears in full in both Quick Reference and Explain; state it once and cross-reference.

Trim the Explain section to only what Claude does not already know (e.g., keep the iOS Safari sub-12px auto-inflation heuristic, drop the generic px-vs-rem primer), and cut the "1 in 3 adults over 65" statistic or move it to references/rule.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but WCAG 2.1 SC 1.4.4 is stated in full in both "Quick Reference" and again in "Explain", and the Explain section re-explains px-vs-rem concepts Claude already knows; the "1 in 3 adults over 65" statistic is motivational padding. It fits anchor 3 (mostly efficient with some unnecessary explanation) rather than 4 because the duplication and concept re-explanation are clearly trimmable.

3 / 5

Actionability

The guidance is concrete and executable: exact thresholds (16px/1rem floor, 12px minimum, 0.75rem for intentional small text), an exact conversion procedure ("divide the pixel value by 16" — 14px becomes 0.875rem), a specific replacement pattern (html { font-size: 62.5% }), and a verification method (Chrome DevTools at 200% zoom). It is not 5 because fully copy-paste-ready code examples live only in the reference file, not inline.

4 / 5

Workflow Clarity

This is a simple, single-purpose audit skill under 50 lines with an unambiguous sequence (Quick Reference → Check → Fix → Explain → Code Review) and an explicit validation step ("Check that text remains readable and layout does not break at 200% zoom" tested via Chrome DevTools). Non-destructive, so the validation cap does not apply, and the simple-skill exception holds: the single action is unambiguous.

5 / 5

Progressive Disclosure

SKILL.md is a concise ~30-line overview with clear sections, and full implementation details, code examples, and framework-specific guidance are appropriately split into references/rule.md (verified to exist, 65 lines), explicitly signaled at the end of the body and exactly one level deep. This matches the clear-overview anchor with well-signaled one-level-deep references.

5 / 5

Total

17

/

20

Passed

Description

70%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.

The description has explicit when-guidance and reasonable trigger keywords scoped to a distinct CSS niche, but the opening clause is grammatically broken ("Use when applies to all CSS font-size declarations") and the set of concrete capabilities (flag, fix, px-to-rem conversion) is understated. It communicates scope adequately but would misfire less and surface more often with a rewritten action-first opening and added synonyms like rem/em and "text too small".

Suggestions

Rewrite the opening clause to lead with concrete actions, e.g. "Flags and fixes CSS `font-size` declarations that use `px` units or fall below readable minimums; converts `px` to `rem`." — this fixes the garbled "Use when applies to all..." construction and raises specificity.

Add natural trigger terms users would actually say: "rem/em units", "text too small", "zoom", "readable font size", and ".css" — to improve trigger_term_quality from good to comprehensive.

State the fix capability (px-to-rem conversion at the 16px base) in the description, not just the check/audit actions, so the "what" is complete.

DimensionReasoningScore

Specificity

The description names the domain ("CSS `font-size` declarations") and one or two concrete actions ("Check for `font-size` in media queries", "auditing mobile responsiveness"), but the opening clause "Use when applies to all CSS font-size declarations" is garbled scope language rather than an action, and no flag/fix/convert capabilities are stated. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4 because several concrete capabilities are missing or muddled.

3 / 5

Completeness

Both what ("Check for `font-size` in media queries targeting small screens", "auditing") and when ("Use when auditing mobile responsiveness and accessibility compliance") are explicitly present, matching anchor 4. It is not 5 because the "what" is weakened by the grammatically broken opening clause, and not 3 because the when guidance is explicit and concrete rather than weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "CSS `font-size`", "`px` units", "body text", "UI labels", "mobile responsiveness", "accessibility compliance", "media queries", "small screens". It is not 5 because common natural variations users would say are missing, such as "rem/em", "text too small", "zoom", or ".css" files.

4 / 5

Distinctiveness Conflict Risk

The description is scoped narrowly to CSS font-size declarations, px units, and media queries — a clear niche with distinct triggers. It is not 5 because the broad phrases "auditing mobile responsiveness and accessibility compliance" could overlap with general accessibility-audit skills.

4 / 5

Total

15

/

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/font-size/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.