CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/lighthouse-perf

Configures Lighthouse CI (`@lhci/cli`) to audit Web Vitals (LCP, INP, CLS) on every PR, asserts against canonical thresholds (LCP ≤2.5s, INP ≤200ms, CLS ≤0.1 at the 75th percentile), uploads Lighthouse reports as build artifacts, and posts deltas as PR comments. Includes a budget-authoring reference: per-route LCP/INP/CLS thresholds by traffic class (cached / dynamic / api-heavy / form-heavy / media-heavy) via `assertMatrix`, plus `budget.json` resource-size caps (JS / CSS / images / total bytes). Use when the project ships a web frontend and the team needs continuous Web Vitals monitoring tied to PR gating, or needs its first Lighthouse budgets drafted.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

80%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 highly actionable, well-structured skill with clean progressive disclosure and copy-paste-ready code. The main weakness is workflow clarity: the CI-gating flow lists steps but omits explicit validation/verification checkpoints expected of a batch/gating operation.

Suggestions

Add an explicit validation/checkpoint step to the CI flow, e.g. verify the dev server is reachable before lhci autorun and confirm LHCI_GITHUB_APP_TOKEN is set when PR-comment deltas are expected.

Trim the Overview metrics table since the LCP/INP/CLS thresholds and 75th-percentile standard already appear in the description; keep only the INP-replaces-FID note that is not common knowledge.

Add a short 'verify' note after the GitHub Actions workflow that the .lighthouseci/ artifact directory is produced and the run exits non-zero on error-level assertion failures.

DimensionReasoningScore

Conciseness

Dense, assume-competent content with minimal padding, but the Overview metrics table and some Lab-vs-field framing lightly restate threshold values already in the description/frontmatter and broadly-known context.

4 / 5

Actionability

Fully executable: install command, complete .lighthouserc.js config, lhci autorun phase breakdown, single-URL commands, a complete GitHub Actions workflow, and a copy-paste mobile/desktop two-config pattern.

5 / 5

Workflow Clarity

Install/Configure/Run/CI sequence is clear and phases are enumerated, but the core CI gating flow lacks explicit validation checkpoints (verify server reachable, confirm LHCI_GITHUB_APP_TOKEN set, check artifact path) for a batch/gating operation.

3 / 5

Progressive Disclosure

Overview body with a single well-signaled one-level-deep reference to references/budgets.md (verified real), no onward nesting, and an appropriate split of detail into that reference.

5 / 5

Total

17

/

20

Passed

Description

92%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, specific, third-person description that answers both what and when with concrete triggers and clear boundaries. Its only gap is slightly incomplete synonym coverage (Core Web Vitals, performance budgets) in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (configures Lighthouse CI, asserts thresholds, uploads reports, posts PR deltas, authors per-route budgets via assertMatrix and budget.json) with comprehensive coverage rather than just several actions.

5 / 5

Completeness

Explicitly answers both what (configures/asserts/uploads/posts/authoring reference) and when ('Use when the project ships a web frontend and the team needs continuous Web Vitals monitoring tied to PR gating, or needs its first Lighthouse budgets drafted') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms (Web Vitals, LCP/INP/CLS, Lighthouse, PR gating, web frontend, Lighthouse budgets) but omits common synonyms like 'Core Web Vitals' and 'performance budgets'.

4 / 5

Distinctiveness Conflict Risk

Clear Lighthouse-CI-for-Web-Vitals niche with distinct triggers and explicit boundaries (backend/CLI deferred to k6-load-testing), giving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents

DiscoveryImplementationValidation