CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

70%

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/largest-contentful-paint/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 well-structured with clean progressive disclosure to a genuine, well-organized reference file, but it is thin on executable guidance — no code, commands, or concrete DevTools steps in-body — and it spends tokens explaining LCP and duplicating the fix list across sections. The auto-generated 'Explain' and 'Code Review' sections read as template filler.

Suggestions

Replace the generic Check/Fix guidance with one concrete in-body example, e.g., the exact DevTools/Lighthouse path to identify the LCP element and a preload snippet for a hero image.

Delete the LCP definition sentence and the redundant Quick Reference bullets (they restate the Fix section) to remove duplication and assumed-unknown concepts.

Add an explicit re-measure checkpoint after fixes ('re-run Lighthouse and confirm LCP < 2.5s') to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

The body explains what LCP is ('LCP is the most important Core Web Vital for perceived load speed—it measures when the main content becomes visible'), a concept Claude already knows, and the Quick Reference bullets largely duplicate the Fix sentence ('preloading critical resources, optimizing images...'). Mostly efficient but with unnecessary explanation and internal duplication that could be tightened.

3 / 5

Actionability

Some concrete guidance is present — the 2.5s threshold, named tools ('Lighthouse or PageSpeed Insights'), and named techniques (preload, CDN, TTFB) — but the body contains no executable steps or code; 'Optimize LCP by preloading critical resources, optimizing images, using CDN, and reducing server response time' is a high-level hint list with all executable detail deferred to the reference.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections provide a rough measure-then-fix sequence, and 'Verify the largest visible element renders within 2.5 seconds' gestures at validation, but there are no explicit checkpoints or feedback loops (e.g., re-measure after each fix), matching anchor 3's 'steps listed but validation gaps'.

3 / 5

Progressive Disclosure

The body is a concise overview that clearly signals a real, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md', which exists and is well-organized (Code Examples, Troubleshooting Flow, Verification). Content is appropriately split and navigation is trivial.

5 / 5

Total

14

/

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.

The description has an explicit and natural 'Use when...' trigger clause plus concrete verification guidance naming specific tools, which is solid. Its main weaknesses are an awkward template-concatenation phrase ('related to Optimize largest contentful paint') that clouds the what, and missing common synonyms like 'LCP' and 'Core Web Vitals'.

Suggestions

Rewrite the muddled clause as a clean capability statement, e.g., 'Audits and optimizes Largest Contentful Paint (LCP)...' so the what is stated as a third-person action.

Add the abbreviations and synonyms users naturally say — 'LCP', 'Core Web Vitals', 'PageSpeed score' — to trigger-term coverage.

Include the fix-side actions (preload hero images, optimize/size images, use CDN, reduce TTFB) so the capability list is comprehensive rather than audit-only.

DimensionReasoningScore

Specificity

Names the domain (LCP/page-load performance) and 1-2 concrete actions ('auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data'), but the fix-side actions (preloading, image optimization, CDN, TTFB) are absent, so coverage is not comprehensive.

3 / 5

Completeness

Both what ('Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes') and when ('Use when auditing slow page loads, heavy assets, or rendering delays...') are present, but the what is muddled by the template-like phrase 'related to Optimize largest contentful paint', keeping it below anchor 5.

4 / 5

Trigger Term Quality

Good natural-phrase coverage ('slow page loads', 'heavy assets', 'rendering delays', 'DevTools, Lighthouse') that users would actually say, but common synonyms like 'LCP' and 'Core Web Vitals' are missing, falling short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Tied to a specific metric (Largest Contentful Paint) with distinct measurement triggers, but broad phrases like 'slow page loads' and 'heavy assets' create minor overlap risk with sibling performance-audit skills, preventing a 5.

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