Agent skill · Security

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).

tech-leads-clubgithub.com/tech-leads-clubGitHub ↗
claude-codecopilotcursorNOASSERTION
Install
npx skills add tech-leads-club/agent-skills --skill perf-lighthouse --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: packages/skills-catalog/skills/(performance)/perf-lighthouse/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 4,983
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Lighthouse Audits ## CLI Quick Start ```bash # Install npm install -g lighthouse # Basic audit lighthouse https://example.com # Mobile performance only (faster) lighthouse https://example.com --preset=perf --form-factor=mobile # Output JSON for parsing lighthouse https://example.com --output=json --output-path=./report.json # Output HTML report lighthouse https://example.com --output=html --output-path=./report.html ``` ## Common Flags ```bash --preset=perf # Performance only (skip accessibility, SEO, etc.) --form-factor=mobile # Mobile device emulation (default) --form-factor=desktop # Desktop --throttling-method=devtools # More accurate throttling --only-categories=performance,accessibility # Specific categories --chrome-flags="--headless" # Headless Chrome ``` ## Performance Budgets Create `budget.json`: ```json [ { "resourceSizes": [ { "resourceType": "script", "budget": 200 }, { "resourceType": "image", "budget": 300 }, { "resourceType": "stylesheet", "budget": 50 }, { "resourceType": "total", "budget": 500 } ], "resourceCounts": [{ "resourceType": "third-party", "budget": 5 }], "timings": [ { "metric": "interactive", "budget": 3000 }, { "metric": "first-contentful-paint", "

What's inside
Steps it walks through
  1. CLI Quick Start
  2. Common Flags
  3. Performance Budgets
  4. Node API
  5. GitHub Actions
  6. Lighthouse CI (LHCI)
  7. Parse JSON Report
  8. Compare Builds
  9. Troubleshooting
Commands it runs
Install
npm install -g lighthouse
Basic audit
lighthouse https://example.com
Mobile performance only (faster)
lighthouse https://example.com --preset=perf --form-factor=mobile
Output JSON for parsing
lighthouse https://example.com --output=json --output-path=./report.json
Output HTML report
lighthouse https://example.com --output=html --output-path=./report.html
More from agent-skills
All skills →
About this skill
What does the perf-lighthouse skill do?

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).

How do I install it?

Run `npx skills add tech-leads-club/agent-skills --skill perf-lighthouse --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From tech-leads-club/agent-skills, a repository with 4,983 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going