CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

first-contentful-paint

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

Quality

75%

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/first-contentful-paint/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 clean, well-structured overview that practices good progressive disclosure — a lean body delegating full code examples to a clearly signaled references/rule.md — with a sensible Check→Fix sequence and concrete tool/threshold guidance. Its weaknesses are small but real: a redundant "Explain" section covering a concept Claude already knows, a Fix sentence duplicating the Quick Reference, and no explicit re-validation step after applying fixes.

Suggestions

Drop the "Explain" section (Claude already knows what FCP measures) or fold a one-line framing into the intro instead.

Merge the "Fix" sentence with the Quick Reference bullets to remove the duplicated technique list.

Add an explicit post-fix verification step in the body (e.g. "Re-measure FCP and confirm it is under 1.8s"), possibly pointing at rule.md's Verification section.

DimensionReasoningScore

Conciseness

The body is short and mostly efficient, but it includes unnecessary material: the "Explain" section instructs Claude to explain what FCP measures (a concept Claude already knows, explicitly penalized), and the "Fix" sentence ("eliminating render-blocking resources, inlining critical CSS, and reducing server response time") duplicates the Quick Reference bullets. This matches the 3 anchor (mostly efficient, some unnecessary explanation, could be tightened) rather than 4's minor-trimmable instances.

3 / 5

Actionability

Concrete, specific guidance is present throughout: named tools ("Measure FCP using Lighthouse or PageSpeed Insights"), an explicit threshold ("within 1.8 seconds"), and named techniques ("Inline critical CSS", "Use preconnect for third-party origins"), with executable code deferred one level to references/rule.md — the intended instruction-plus-reference pattern. It falls short of 5 only because the body itself contains no copy-paste code or commands.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a clear measure-then-fix sequence with an explicit pre-checkpoint ("Verify first content appears within 1.8 seconds"), and the Code Review section says to "describe the measurement method used to confirm the issue". It stops short of 5 because there is no explicit post-fix re-validation loop in the body — the verification section lives only in rule.md and is not surfaced as a step.

4 / 5

Progressive Disclosure

The body is a short, well-sectioned overview whose implementation detail is appropriately split into a single, real, one-level-deep reference, clearly signaled with its contents: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" (the file exists and contains exactly that). This matches the 5 anchor: clear overview, well-signaled reference, easy navigation.

5 / 5

Total

16

/

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.

A serviceable description with a genuine, natural 'Use when' trigger and a concrete verify-before-recommending behavior, but the templated "related to Optimize first contentful paint" phrase garbles the what-clause, and it omits the concrete actions (and the 'FCP' synonym) that would make it comprehensive.

Suggestions

Rewrite the mid-sentence "related to Optimize first contentful paint" into a proper what-clause, e.g. "Diagnoses and fixes first contentful paint (FCP) issues: render-blocking resources, critical CSS inlining, preconnect, and server response time."

Add the natural synonym "FCP" (used throughout the body) and common user phrasings like "page speed" to the trigger clause.

Name the concrete optimization techniques the skill covers so the 'what' goes beyond 'recommending changes'.

DimensionReasoningScore

Specificity

The one concrete action is "Verify the actual bottleneck in DevTools, Lighthouse, or field data", which names specific tools; the surrounding verbs ("auditing", "recommending changes") are generic. It never states the actual optimization actions the skill covers (inlining critical CSS, preconnect, deferring render-blocking resources), so coverage is not comprehensive — matching the 3 anchor (1-2 concrete actions) rather than 4 (several actions, minor gaps).

3 / 5

Completeness

The "when" is explicit ("Use when auditing slow page loads, heavy assets, or rendering delays…") and a "what" is present (verify the bottleneck before recommending changes). The "what" is weakened by the awkward "related to Optimize first contentful paint" clause — a rule title pasted mid-sentence — and "recommending changes" never says what kind of changes, so it fits the 4 anchor (both present, 'what' could be more explicit) rather than 5 (clearly and explicitly both).

4 / 5

Trigger Term Quality

Natural phrases a user would say are present ("slow page loads", "heavy assets", "rendering delays") plus tool names ("DevTools", "Lighthouse", "field data"), giving good coverage. A few common terms are missing — notably the "FCP" abbreviation the body itself leans on, plus "page speed" and "Core Web Vitals" — so it falls short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche (FCP / page-load rendering performance) is specific and the triggers would not fire for unrelated skills, so it is mostly distinct. There is minor overlap risk with closely related web-performance skills (LCP, page speed, Core Web Vitals), which matches the 4 anchor rather than 5's minimal-conflict clear niche.

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/first-contentful-paint/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.