page-weight

Use when auditing slow page loads, heavy assets, or rendering delays related to Keep page weight under 1500KB. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

73%

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/page-weight/SKILL.md

Quality

Content

57%

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 well-organized overview with excellent progressive disclosure, but it is held back by restated general knowledge, abstract non-executable guidance, and a workflow lacking validation checkpoints.

Suggestions

Trim the intro sentence and the "Explain" section, which restate page-weight concepts Claude already knows.

Add concrete, executable guidance in "Check" and "Fix" (e.g., specific DevTools/Lighthouse steps or commands) rather than deferring all detail to the reference.

Insert an explicit validation checkpoint in the workflow (e.g., re-measure page weight after changes to confirm it dropped below the target).

Dimension	Reasoning	Score
Conciseness	The body is mostly tight and sectioned, but the intro ("Page weight directly correlates with load time—a 1.5MB page takes 3-5 seconds on 4G mobile") and the "Explain" section restate general performance knowledge Claude already has, so it could be trimmed.	2 / 3
Actionability	Concrete thresholds (under 500KB, max 1500KB) and named techniques (image optimization, code minification) give some guidance, but sections like "Optimize this page to reduce its total weight…" stay abstract with no executable commands or code, deferring specifics to the reference.	2 / 3
Workflow Clarity	A Check→Fix→Explain→Code Review sequence is present, but there are no explicit validation checkpoints or feedback loops for confirming a fix actually reduced weight, which caps it at 2.	2 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference ("see references/rule.md"), and that file exists, giving clean navigation without nesting.	3 / 3
	Total	9 / 12 Passed

Description

90%

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 explicit trigger guidance, natural terminology, and a distinct page-weight niche; its only weakness is that the named actions lean slightly abstract rather than enumerating multiple concrete operations.

Dimension	Reasoning	Score
Specificity	Names the page-weight domain and actions ("auditing slow page loads", "Verify the actual bottleneck in DevTools, Lighthouse, or field data", "recommending changes") with concrete tool names, but the actions are somewhat abstract compared to a full list of specific concrete operations, so it stops short of a 3.	2 / 3
Completeness	An explicit "Use when auditing slow page loads, heavy assets, or rendering delays" clause answers when, and "Verify the actual bottleneck… before recommending changes" answers what, satisfying both halves.	3 / 3
Trigger Term Quality	Natural user-facing terms like "slow page loads", "heavy assets", "rendering delays", and "page weight" plus tool names (DevTools, Lighthouse) give good coverage of phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The page-weight-under-1500KB framing is a clear, narrow niche with distinct triggers unlikely to collide with unrelated skills.	3 / 3
	Total	11 / 12 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/page-weight/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours 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.