CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

92%

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%

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 and highly actionable with concrete thresholds, a clear audit checklist including verification, and a properly signaled one-level reference. The main drag is conciseness: a motivational opening and px/rem advice repeated across sections add tokens Claude does not need.

Suggestions

Trim the motivational intro paragraph (the '1 in 3 adults over 65' rationale) or move it to references/rule.md; keep the body focused on what to check and how to fix.

Consolidate the px/rem advice so it appears once (Quick Reference or Fix) rather than restated across Quick Reference, Fix, and Explain.

Consider moving the WCAG 1.4.4 explanation in 'Explain' into the reference file, since it largely restates guidance already in Quick Reference and Fix.

DimensionReasoningScore

Conciseness

Mostly efficient, but the motivational intro ('Approximately 1 in 3 adults over 65 increases their browser's default font size...') and the px/rem guidance repeated across Quick Reference, Fix, and Explain add redundancy Claude does not need; not a score 1 because core guidance is tight and domain-specific.

2 / 3

Actionability

Concrete, copy-paste-ready guidance: '14px becomes 0.875rem', 'html { font-size: 62.5% }', 'at least 0.75rem (12px)', and explicit 16px/12px/200%-zoom thresholds — fully actionable for an instruction/review skill.

3 / 3

Workflow Clarity

Check and Fix are structured as numbered checklists, and Check embeds an explicit verification ('test in Chrome DevTools ... at 200% zoom', 'text remains readable and layout does not break'); the single audit task is unambiguous, satisfying the simple-skill allowance.

3 / 3

Progressive Disclosure

Well-organized overview sections with a clearly signaled one-level-deep pointer — 'see `references/rule.md`' — to a verified existing reference file containing implementation details and code examples.

3 / 3

Total

11

/

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 covers concrete actions, natural trigger terms, both what-and-when, and a distinctive niche, scoring well across all dimensions. Its main weakness is a grammatically broken opening clause ('Use when applies to all CSS font-size declarations') that muddies scope versus trigger phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'auditing mobile responsiveness and accessibility compliance' and 'Check for `font-size` in media queries targeting small screens' — with specific targets (px units, body text, UI labels, navigation); the 'applies to all CSS font-size declarations' clause is scope rather than an action but does not outweigh the concrete actions present.

3 / 3

Completeness

Both 'what' (audit/check font-size declarations) and 'when' ('Use when auditing mobile responsiveness and accessibility compliance', 'Check for ... media queries targeting small screens') are explicitly present; the opening 'Use when applies to all CSS `font-size` declarations' is grammatically tangled but does not remove either coverage.

3 / 3

Trigger Term Quality

Natural developer-facing terms are well covered — 'CSS `font-size`', 'px units', 'mobile responsiveness', 'accessibility compliance', 'media queries', 'small screens' — terms a user would plausibly say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to CSS font-size accessibility on mobile, with distinct triggers unlikely to fire for unrelated skills.

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.