html-size

Use when auditing page weight for crawl efficiency, investigating why certain page content is not appearing in Google's index, or reviewing server-rendered pages that embed large JSON payloads in HTML.

Quality

86%

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

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear Check→Fix flow and a properly signaled one-level reference file. Its weaknesses are repetition of the same crawl-limit facts across sections and the absence of a post-fix verification step.

Suggestions

Remove the duplicated ~15MB / crawl-budget statements: keep them in the intro and delete the overlapping Quick Reference bullet and Explain paragraph, or fold Explain into Quick Reference.

Add an explicit post-fix verification step to the Fix workflow (e.g., re-run the curl measurement to confirm the page is under the 2MB target after remediation).

Consolidate the 'Check' and 'Code Review' sections, which overlap on measuring raw HTML bytes and inspecting __NEXT_DATA__ blocks, to tighten the body further.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but the ~15MB/crawl-budget fact is restated across the intro, the Quick Reference bullets, and the Explain section, which is repetition a tightening pass would remove; this fits the score-2 anchor rather than the lean score-3 anchor.	2 / 3
Actionability	Provides an executable curl one-liner, concrete thresholds (2MB investigate / 5MB critical, flag blocks over 500KB), and specific per-cause fixes — copy-paste-ready actionable guidance matching the score-3 anchor.	3 / 3
Workflow Clarity	The Check→Fix sequence is clearly present with a diagnostic checkpoint, but there is no post-fix verification/re-measure step confirming the HTML dropped below target, fitting the score-2 anchor for missing checkpoints.	2 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a one-level-deep reference ('see references/rule.md', a verified file), matching the score-3 anchor for well-organized, appropriately split content.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 strong, third-person description with an explicit 'Use when…' trigger and multiple concrete actions that cover both what the skill does and when to use it. It is specific, naturally worded, and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'auditing page weight for crawl efficiency', 'investigating why certain page content is not appearing in Google's index', and 'reviewing server-rendered pages that embed large JSON payloads in HTML' — matching the score-3 anchor rather than the domain-only score-2 anchor.	3 / 3
Completeness	Opens with an explicit 'Use when…' trigger and the listed actions answer what the skill does, so both what and when are present; the missing-trigger cap at 2 does not apply.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'page weight', 'crawl efficiency', 'Google's index', 'server-rendered pages', 'large JSON payloads in HTML' — giving good natural-keyword coverage per the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Targets a specific niche (HTML crawl-size / crawl budget) with distinct triggers unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	12 / 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/html-size/SKILL.md
Commit: 48405aa

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