CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

font-loading

Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize web font loading. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

68%

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

Quality

Content

57%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 compact, well-structured overview that correctly pushes code examples to a single one-level-deep reference file. Its weaknesses are internal: the Quick Reference, Check, and Fix sections repeat the same three recommendations, the fix guidance lacks the executable details needed to work standalone, and the workflow has no explicit validation checkpoint before or after making changes.

Suggestions

Consolidate the duplicated guidance: Quick Reference, Check, and Fix all restate the same font-display/preload/WOFF2 advice — merge Check and Fix into one section and drop the redundant bullets.

Add an explicit validation step to the workflow, e.g. 'Re-run Lighthouse or check field data after the change to confirm CLS and load time improved', and mirror the description's verify-the-bottleneck-first guidance in the body.

Include one minimal executable example inline (a complete @font-face with font-display and a correct <link rel='preload' as='font' crossorigin=...> tag) since the omitted attributes are the difference between a working and broken preload.

DimensionReasoningScore

Conciseness

Quotes: 'Use `font-display: swap` to prevent invisible text during load' / 'Preload critical fonts to discover them earlier' (Quick Reference) are repeated nearly verbatim in '## Check' ('verify that `font-display` is used and critical fonts are preloaded') and '## Fix' ('Add `font-display: swap` to `@font-face` declarations and use `<link rel='preload'>`'). The intro line 'negatively impacting both user experience and Core Web Vitals' also explains what Claude already knows. Mostly efficient, but the three-way repetition could be consolidated — matching anchor 3 (could be tightened) rather than anchor 4 (only minor trimmable instances).

3 / 5

Actionability

Quotes: 'Add `font-display: swap` to `@font-face` declarations and use `<link rel='preload'>` for the most important fonts' — concrete property and tag names are given, but the body contains no complete executable snippet, and the preload guidance omits key working details (as='font', crossorigin, which URL to preload), deferring all code to references/rule.md. This is concrete-but-incomplete guidance (anchor 3) rather than mostly-executable guidance with minor gaps (anchor 4).

3 / 5

Workflow Clarity

The '## Check' → '## Fix' → '## Explain' sections give a rough audit-then-fix sequence, but checkpoints are implicit: there is no step confirming the bottleneck is actually fonts before changing code (that guidance lives only in the frontmatter description), and no post-fix verification step such as re-running Lighthouse to confirm the improvement. Anchor 3 (sequence present, checkpoints missing or implicit) fits; anchor 4 would require most checkpoints to be explicit.

3 / 5

Progressive Disclosure

The body is a well-organized overview under 50 lines (Quick Reference, Check, Fix, Explain, Code Review) with a single, clearly signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and references/rule.md exists in the bundle and delivers exactly what is promised. This matches anchor 5: clear overview, appropriately split content, easy navigation.

5 / 5

Total

14

/

20

Passed

Description

66%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 an explicit and well-formed 'Use when...' trigger clause with specific verification tools named, which is its main strength. However, it describes only the audit/verify side of the skill, never stating the concrete font optimizations it guides, and its leading trigger terms are generic performance language that risks overlap with sibling performance skills.

Suggestions

State the skill's concrete fix actions in the description, e.g. 'Applies font-display: swap, font preloading, and WOFF2 formats to @font-face declarations' so the 'what' is complete.

Add font-specific trigger synonyms users would naturally say — 'layout shift', 'CLS', 'flash of invisible text', 'FOIT', 'fonts not loading' — to improve trigger coverage.

Narrow the leading trigger terms to font-specific symptoms (e.g. 'Use when fonts cause slow rendering, invisible text, or layout shifts') to reduce overlap with sibling performance-audit skills.

DimensionReasoningScore

Specificity

Quotes: 'auditing slow page loads, heavy assets, or rendering delays' and 'Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes' — the domain (web font loading) plus two concrete actions are named, but the description never states the optimization actions the skill actually performs (font-display, preloading, WOFF2), so coverage is incomplete. It fits anchor 3 (domain + 1-2 concrete actions, not comprehensive) better than anchor 4, which expects several specific actions with only minor gaps.

3 / 5

Completeness

Quotes: 'Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize web font loading' — an explicit 'when' with concrete triggers, and the 'what' ('Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes') is stated. Not anchor 5 because the 'what' covers only auditing/verifying; it never says the skill applies font-loading optimizations, leaving the core capability implicit.

4 / 5

Trigger Term Quality

Quotes: 'slow page loads', 'heavy assets', 'rendering delays', 'DevTools', 'Lighthouse', 'field data' — good coverage of natural performance phrasing a user would say. Not anchor 5 because common font-specific variations users actually say are missing: 'layout shift', 'CLS', 'flash of invisible text', 'FOIT', 'fonts not loading'.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'related to Optimize web font loading' scopes the skill to a clear niche, but the leading triggers 'slow page loads, heavy assets, or rendering delays' are generic performance phrasing that overlaps heavily with sibling performance-audit skills (image optimization, caching, bundle size). This lands between anchor 3 (could still overlap with similar skills) and anchor 4 (mostly distinct), and the broad leading triggers pull it to 3.

3 / 5

Total

14

/

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