CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webpagetest

Use when reviewing templates, rendered HTML, or shared components related to Analyze performance with WebPageTest. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

71%

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/webpagetest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 a lean, well-organized overview with exemplary progressive disclosure, correctly pushing the heavy code examples into references/rule.md. Its weaknesses are vague Check/Fix/Explain sections that instruct without specifics and a Quick Reference that lists tips rather than a sequenced testing workflow.

Suggestions

Replace the abstract Check/Fix text with the concrete essentials inline, e.g. the WebPageTest URL, a minimal test configuration (location, browser, connection, 3+ runs), and the Core Web Vitals thresholds (LCP < 2.5s, CLS < 0.1) currently buried in references/rule.md.

Order the Quick Reference into an explicit sequence: configure the test → run 3+ tests from a user-proximate location → review filmstrip for visual progress → inspect the waterfall for blocking resources and slow third-parties.

Drop or merge the redundant Check section (it restates the title/intro) to tighten token usage.

DimensionReasoningScore

Conciseness

The ~30-line body is lean, assumes Claude's competence, and contains no concept tutorials; the intro sentence and the Check section both restate "analyze page performance", which is minor trimmable redundancy. Efficient with minor over-explanation fits anchor 4 rather than 5, where every token earns its place.

4 / 5

Actionability

Quick Reference gives concrete hints ("Run 3+ tests", "Use filmstrip view to identify visual progress", "Check waterfall for blocking resources and slow third-parties") but the Check/Fix/Explain sections are abstract ("Implement recommended optimizations from WebPageTest results") with no executable commands or metric thresholds in the body. Some concrete but incomplete guidance matches anchor 3, not 4 (no executable code/commands) and not 2 (the hints exceed minimal).

3 / 5

Workflow Clarity

The Quick Reference bullets are unordered tips rather than a sequenced procedure; there is no explicit run-test → read-metrics → flag-issues order or checkpoints, though as a read-only analysis skill the destructive-operation cap does not apply. Steps listed with implicit sequence and no checkpoints fits anchor 3 rather than 4 (no clear sequence present).

3 / 5

Progressive Disclosure

The body is a short, well-sectioned overview that defers the 1073-line bulk of code examples and framework guidance to a clearly signaled, verified one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). This matches anchor 5: clear overview, well-signaled single-level reference, easy navigation.

5 / 5

Total

15

/

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.

The description has an explicit and reasonable 'when' clause plus natural trigger terms anchored by the distinctive WebPageTest name, but the 'what' is generic markup-validation boilerplate that does not describe what this skill actually does (performance analysis). The shared HTML-review trigger phrasing also creates overlap risk with sibling skills in the same family.

Suggestions

State the skill's concrete capability in the description, e.g. "Analyzes page performance with WebPageTest: runs repeated tests from user-proximate locations, inspects filmstrip and waterfall views, and flags slow TTFB, render-blocking resources, and third-party script impact."

Add natural trigger synonyms such as "page speed", "site performance", or "load time" so users phrasing the need without the tool name still match.

Make the trigger specific to this rule rather than the shared family boilerplate, e.g. "Use when the user mentions WebPageTest, page-speed testing, or wants real-world loading metrics for rendered pages."

DimensionReasoningScore

Specificity

The only concrete action stated is "Validate the final browser-facing markup"; no performance-analysis actions (run tests, inspect waterfalls, check Core Web Vitals) are named. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

Both an explicit "when" ("Use when reviewing templates, rendered HTML, or shared components...") and a "what" ("Validate the final browser-facing markup...") are present. It sits above anchor 3 (where 'when' is missing or weakly implied) but below anchor 5 because the 'what' is generic validation boilerplate that never states the skill's actual capability (performance analysis).

4 / 5

Trigger Term Quality

Natural terms like "WebPageTest", "performance", "templates", "rendered HTML", and "shared components" are present, but common variations users would say ("page speed", "site performance", "load time") are missing. Good coverage with a few natural terms missing fits anchor 4, not 5.

4 / 5

Distinctiveness Conflict Risk

The trigger "reviewing templates, rendered HTML, or shared components" is boilerplate shared across sibling HTML-rule skills, creating real overlap risk; only the qualifier "related to Analyze performance with WebPageTest" narrows it. Somewhat specific but still overlappable matches anchor 3, not 4 (mostly distinct) or 2 (the WebPageTest qualifier provides a clear niche term).

3 / 5

Total

14

/

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