perf-lighthouse

Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, and set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget. Do NOT use for fixing specific performance issues (use perf-web-optimization or core-web-vitals) or Astro-specific optimization (use perf-astro).

Quality

89%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

79%

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

This is a strong, highly actionable skill that provides comprehensive, executable guidance for running Lighthouse audits across CLI, Node API, and CI contexts. Its main strengths are conciseness and actionability—every section delivers real, copy-paste ready code. The main weakness is that it functions more as a reference document than a guided workflow, lacking explicit validation checkpoints and decision points between steps.

Suggestions

Add a brief workflow overview at the top showing the recommended progression (e.g., 'Start with CLI → Set budgets → Integrate into CI') to help Claude choose the right approach for the user's context.

Add validation/verification guidance after key steps, such as checking that a JSON report was generated successfully before parsing, or verifying budget violations in CI output.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient throughout. It avoids explaining what Lighthouse is or how Chrome works, jumping straight into executable commands and code. Every section delivers actionable content without padding.	3 / 3
Actionability	Every section provides copy-paste ready code: CLI commands with real flags, complete Node API usage with chrome-launcher, full GitHub Actions workflow, LHCI config, JSON parsing, and comparison scripts. All examples are executable and complete.	3 / 3
Workflow Clarity	Individual sections are clear, but the overall workflow lacks explicit sequencing and validation checkpoints. For example, the 'Compare Builds' section doesn't validate that reports were generated successfully before comparing, and there's no guidance on interpreting results to decide next steps. The CI sections are well-structured but the skill as a whole reads more like a reference than a guided workflow.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers, but it's a fairly long monolithic document (~180 lines of content). The GitHub Actions, LHCI, and comparison script sections could reasonably be split into separate reference files. However, for a standalone skill with no bundle, the flat structure is acceptable and navigable.	2 / 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.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, natural trigger terms, explicit 'Use when' and 'Do NOT use' clauses, and clear boundaries distinguishing it from related skills. The description is concise yet comprehensive, serving as a strong example of how skill descriptions should be written.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, and set performance budgets.' These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (run audits, parse reports, set budgets) and 'when' (explicit 'Use when...' clause plus trigger terms). Also includes explicit 'Do NOT use' guidance for disambiguation, which goes beyond the minimum requirements.	3 / 3
Trigger Term Quality	Explicitly lists natural trigger terms users would say: 'lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.' These cover common variations of how users would phrase requests.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with explicit boundary-setting via 'Do NOT use for fixing specific performance issues (use perf-web-optimization or core-web-vitals) or Astro-specific optimization (use perf-astro).' This directly addresses potential overlap with related skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Commit: 5f9b25d

Reviewed: 4 days 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.