performance-testing

Performance testing with Lighthouse and Web Vitals integration in Playwright. Use when measuring page load times, Core Web Vitals, Lighthouse audits, or performance budgets.

Quality

70%

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/performance-testing/SKILL.md

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.

A code-rich, actionable reference for Lighthouse and Web Vitals testing in Playwright, but it reads as an inlined catalog with redundant examples, no validation-gated workflow, and a broken reference link. Consolidating duplicates and moving deep-dive material into the (currently missing) reference files would materially improve it.

Suggestions

Consolidate the redundant Lighthouse audit examples (Quick Start, Basic Audit, With Thresholds) into one parameterized example to remove duplication.

Add a validation checkpoint to the performance-testing workflow (e.g., run audit → if a threshold fails, inspect the failing metric and re-run) so multi-step processes have explicit feedback loops.

Create the missing 'references/lighthouse-config.md' file (or remove the dangling reference) and move the mobile/desktop config blocks, resource-timing, reporting, and CI details into reference files, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The prose is lean and code-focused, but there is notable redundancy — 'Quick Start', 'Basic Audit', and 'With Thresholds' are near-identical playAudit examples, and the mobile/desktop audits duplicate boilerplate that differs only in config values — that could be tightened or consolidated.	3 / 5
Actionability	Mostly executable, copy-paste-ready TypeScript covering the common cases (audits, thresholds, throttling, reporting, CI), but minor gaps like the web-vitals addInitScript using an ES import in injected content and reliance on the deprecated FID metric keep it just below anchor 5.	4 / 5
Workflow Clarity	The content is a topic catalog rather than a sequenced process; only the CI section offers a real sequence, and no section provides validation checkpoints (e.g., run audit → on failure → diagnose → re-run), so it sits at anchor 3.	3 / 5
Progressive Disclosure	Section headers give reasonable structure and the References section signals files clearly, but bulk detailed content (mobile/desktop configs, resource timing, reporting, CI) is inlined rather than split into reference files, and one referenced path ('references/lighthouse-config.md') does not exist.	3 / 5
	Total	13 / 20 Passed

Description

83%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 strong, well-structured description that clearly states both capability and trigger conditions with concrete, natural-sounding keywords. Minor room to add action diversity and synonyms (e.g., 'page speed', 'web performance') to push specificity and trigger coverage to the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete measurement areas — 'measuring page load times, Core Web Vitals, Lighthouse audits, or performance budgets' — but they share a single verb (measuring) across metric categories rather than distinct concrete actions, so it falls short of the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Performance testing with Lighthouse and Web Vitals integration in Playwright') and 'when' ('Use when measuring page load times, Core Web Vitals, Lighthouse audits, or performance budgets') with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Includes natural terms users would say — 'page load times', 'Core Web Vitals', 'Lighthouse audits', 'performance budgets', 'Playwright' — but misses common synonyms like 'page speed' or 'web performance', placing it just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The Lighthouse/Web Vitals/performance-budget niche is distinct, but the 'in Playwright' framing creates minor overlap risk with general Playwright or e2e testing skills, so it sits at anchor 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/performance-testing/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.