CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

74%

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/html-size/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 compact, well-structured audit skill with concrete commands, thresholds, and a clean one-level reference split. Its weaknesses are repetition — the 15MB fact appears three times and check guidance is duplicated across sections — and the absence of an inline post-fix verification loop.

Suggestions

State the 15MB crawl limit once (Quick Reference) and cut its repetition from the intro and Explain sections.

Merge the Code Review section's overlapping checks with Check, or replace it with a pointer to the Verification section in references/rule.md.

Add a post-fix re-measurement step (e.g., 'Re-run the curl measurement and confirm the page is under 2MB') to close the workflow's feedback loop inline.

DimensionReasoningScore

Conciseness

The body is short and dense with specifics, but the ~15MB limit is stated three times (intro, Quick Reference, and Explain) and the Code Review section repeats checking guidance from Check. Mostly efficient yet clearly tightenable, matching the anchor for some unnecessary explanation; not a 2 because every section still carries unique actionable content.

3 / 5

Actionability

Provides an executable curl measurement command, explicit thresholds ('over 2MB (investigate) and over 5MB (critical)', 'any single block over 500KB'), and named patterns (__NEXT_DATA__, getServerSideProps, React Server Components). Not a 5 because steps like 'Verify HTML is served with gzip or Brotli encoding' and 'Minify HTML output' give directives without commands.

4 / 5

Workflow Clarity

A clear Check → Fix → Code Review sequence with explicit validation thresholds and a five-cause diagnostic taxonomy; this is an audit skill with no destructive/batch operations, so no validation cap applies. Not a 5 because there is no post-fix re-measure/confirm loop in SKILL.md itself (it lives only in references/rule.md).

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and a clearly signaled one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') to a real, substantive reference file with no nested references. This matches the anchor for a clear overview with appropriately split content and easy navigation.

5 / 5

Total

16

/

20

Passed

Description

66%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 well-targeted trigger-only description with specific, natural scenarios and a distinct SEO niche. Its main weakness is structural: it never states what the skill does, relying entirely on 'Use when...' clauses, and it omits common trigger synonyms like 'crawl budget' and 'page size'.

Suggestions

Lead with a capability statement (e.g., 'Measures HTML document size, flags pages over crawl-efficiency thresholds, and identifies/remedies causes of oversized HTML') before the 'Use when' clause so the 'what' is explicit.

Add missing natural trigger terms such as 'crawl budget', 'page size', 'HTML size', or 'SEO' to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description lists several concrete gerund actions ('auditing page weight for crawl efficiency', 'investigating why certain page content is not appearing in Google's index', 'reviewing server-rendered pages that embed large JSON payloads in HTML'), matching the anchor for several specific actions with minor gaps. It is not a 5 because the skill's core capabilities — measuring HTML size, diagnosing causes, applying fixes — are never stated.

4 / 5

Completeness

The description is entirely 'Use when...' clauses: the 'when' is explicit and concrete, but the 'what' is only weakly implied through the trigger gerunds rather than stated as capabilities. This sits between the anchor for 'when' present without 'what' (2) and a clear 'what' with weak 'when' (3).

3 / 5

Trigger Term Quality

Natural phrases users would say are present: 'page weight', 'crawl efficiency', 'not appearing in Google's index', 'large JSON payloads', 'HTML'. A few natural terms are missing ('crawl budget', 'page size', 'HTML size', 'SEO'), so it falls short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (HTML document size against Googlebot crawl limits) with distinct triggers like 'large JSON payloads in HTML'. Minor overlap risk remains with general SEO or site-performance audit skills via broader phrases like 'page weight' and 'crawl efficiency', keeping it below 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/html-size/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.