← ClaudeAtlas

lighthouselisted

Run and interpret Google Lighthouse audits for performance, accessibility, best practices, and SEO; compare reports, diagnose and verify improvements, audit authenticated user flows, and configure Lighthouse CI budgets and regression gates. Not for general browser debugging, Playwright test or harness work, backend load testing, custom audit/plugin development, or the Lighthouse ticketing service.
n-n-code/n-n-code-skills · ★ 4 · Testing & QA · score 75
Install: claude install-skill n-n-code/n-n-code-skills
# Google Lighthouse Turn a page-quality question into reproducible measurements, actionable findings, and verification appropriate to the claim. This is a portable workflow skill. It uses upstream Lighthouse and Lighthouse CI (LHCI), without a bundled runner or required host-specific interface. Reading an existing report needs no browser; native execution needs a compatible Node runtime, Lighthouse, and Chrome/Chromium. Scripted flows additionally need Puppeteer; CI collection needs LHCI. ## Choose the job and owner | Requested job | Work and output | Change boundary | |---|---|---| | Interpret existing reports | Explain findings, compare compatible evidence, identify gaps | Read supplied artifacts; no new audit or source changes unless requested | | Audit a URL or page state | Execute the relevant measurement and retain local reports | Browser activity and report files within the requested scope | | Improve measured behavior | Inspect causes, implement requested fixes, rebuild and remeasure | Scoped source changes under existing authorization | | Configure CI | Establish collection, assertions, and artifact handling | Requested tooling, configuration, and pipeline changes | Let this skill own Lighthouse measurement and interpretation. Use `chrome-devtools-axi` for general Chrome investigation and AXI execution rules; honor an explicitly chosen browser, wrapper, or direct tool interface. Use `playwright-testing` for existing Playwright tests and `setup-playwright` for the