CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webfont-format

Use when reviewing stylesheets, component styles, and responsive behavior related to Optimize web font formats. Check the rendered layout across breakpoints and interaction states before proposing a fix.

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

Quality

Content

65%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 an efficient, well-structured overview that appropriately delegates implementation detail to a real one-level reference file. Its weakness is actionability and workflow clarity in SKILL.md itself: the Fix/Check sections are abstract one-liners with no inline code, commands, or explicit validation steps.

Suggestions

Inline one copy-paste-ready example in the Fix section (e.g. a minimal @font-face block with WOFF2/WOFF sources and font-display: swap) so the most common fix is executable without opening the reference.

Convert the Check section from a single sentence into a short concrete checklist (formats present, fallback order, font-display value, preload tags) that explicitly gates the Fix step.

DimensionReasoningScore

Conciseness

The body is lean (~45 lines) with tight Quick Reference bullets ('Use WOFF2 as primary format (~30% smaller than WOFF)'). Minor trimmable padding: the opening 'Core Web Vitals' sentence states a fact Claude already knows, and the one-line 'Explain' section describes what to say rather than adding guidance. Not 5 because of those two instances; not 3 since most tokens earn their place.

4 / 5

Actionability

The Quick Reference is concrete ('Apply font-display: swap', 'Preload critical fonts and subset'), but the Check/Fix/Explain/Code Review sections are abstract one-liners with no code or commands in the body — no @font-face example or font conversion command, those live in references/rule.md. Fits anchor 3 ('some concrete guidance but incomplete'); not 4 because the Fix section lacks executable steps.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review sections give a rough sequence and 'Check' loosely gates the fix, but there are no explicit validation checkpoints or error-recovery guidance ('Verify that web fonts use modern formats…' is a single sentence, not a step). Fits anchor 3; not 4 because no checkpoint is made explicit. This is not a destructive or batch operation, so the ≤3 cap does not apply.

3 / 5

Progressive Disclosure

The body is a concise overview with a single, clearly signaled, one-level-deep pointer — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — verified to exist (21KB of implementation detail with no nested file references). Fits the anchor 5 example exactly.

5 / 5

Total

15

/

20

Passed

Description

58%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 'Use when' trigger and a rough what, but the phrasing is garbled ('related to Optimize web font formats') and the actions are template-generic rather than font-specific. It would mostly trigger correctly but reads awkwardly and lacks natural font-related terms.

Suggestions

Rewrite the first sentence so the capability is stated as an action, e.g. 'Reviews web font loading (format choice, @font-face, font-display, preloading) in stylesheets and proposes fixes' instead of 'reviewing stylesheets… related to Optimize web font formats'.

Add natural trigger terms users would actually say: 'web fonts', 'font loading', '@font-face', 'WOFF2', so the skill surfaces for those phrasings.

State concrete font-specific actions (convert to WOFF2, add font-display: swap, preload critical fonts) to distinguish it from sibling CSS review rules that share the same 'check rendered layout' template.

DimensionReasoningScore

Specificity

Names the domain (web fonts, stylesheets) and 1-2 actions ('Check the rendered layout across breakpoints and interaction states before proposing a fix'), but the actions are generic review moves with no font-specific operations (no WOFF2 conversion, font-display, or preloading). Anchor 4 doesn't fit because the actions listed would apply to any CSS review skill.

3 / 5

Completeness

Both are present: an explicit 'Use when reviewing stylesheets…' trigger clause and a what ('Check the rendered layout… before proposing a fix'). Not 5 because the core capability is only weakly conveyed — 'related to Optimize web font formats' reads as a title jammed into a sentence rather than a stated capability.

4 / 5

Trigger Term Quality

Contains relevant keywords ('stylesheets', 'component styles', 'responsive behavior', 'web font formats', 'breakpoints') but misses common natural phrases users would say, such as 'web fonts', 'font loading', '@font-face', or 'WOFF2'. Anchor 4 doesn't fit because more than a few natural terms are missing.

3 / 5

Distinctiveness Conflict Risk

'web font formats' is a distinct niche, but 'reviewing stylesheets, component styles, and responsive behavior… Check the rendered layout across breakpoints' overlaps heavily with sibling CSS review rules built from the same template, so it could still trigger for the wrong skill.

3 / 5

Total

13

/

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/webfont-format/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.