largest-contentful-paint

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/largest-contentful-paint/SKILL.md

Quality

Content

78%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 content is a concise, well-structured overview that points cleanly to a real reference file for code examples, with only minor gaps in explicit re-measurement feedback loops and a touch of restated general knowledge.

Dimension	Reasoning	Score
Conciseness	The body is lean with tight Quick Reference bullets and one-line sections, though the opening sentence about perceived load speed and SEO restates knowledge Claude already has and could be trimmed.	4 / 5
Actionability	Provides named, concrete tools (Lighthouse, PageSpeed Insights) and named techniques (preload, CDN, image optimization) plus a specific Code Review framing, with executable code appropriately deferred to the reference file.	4 / 5
Workflow Clarity	A clear Check→Fix→Explain→Code Review sequence with a 2.5s measurement checkpoint exists, but an explicit measure→fix→re-measure feedback loop is only implicit rather than stated.	4 / 5
Progressive Disclosure	Well-organized overview sections with a single clearly signaled one-level-deep reference to the verified references/rule.md, splitting detail appropriately for a simple skill.	5 / 5
	Total	17 / 20 Passed

Description

75%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 is well-constructed with an explicit trigger clause, named tools, and concrete verification guidance, but it relies on the rule title for the core term and has minor overlap with sibling performance skills.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete activities (auditing slow page loads, verifying bottlenecks in DevTools/Lighthouse/field data, recommending changes), but does not provide a comprehensive list of distinct capabilities to reach a 5.	4 / 5
Completeness	Explicit 'Use when...' clause gives concrete triggers and the body states the verification action, but the 'what' leans toward trigger/verification framing rather than a clean capability statement, keeping it just below a 5.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('slow page loads', 'heavy assets', 'rendering delays') and named tools, but the key term appears only as the awkward rule title and omits the common synonym 'LCP'.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific Core Web Vital with distinct triggers, but 'slow page loads' and 'heavy assets' overlap with sibling performance skills (CLS, INP, TTFB), so minor overlap risk remains.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/largest-contentful-paint/SKILL.md
Commit: 30756a7

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.