Seo unlighthouse

Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/seo-unlighthouse

Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and cited by AI systems.

Install

npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill seo-unlighthouse

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Multi-page Lighthouse audit via the MIT-licensed Unlighthouse CLI. Free-tier alternative to running PageSpeed against every URL on a site — no API quota burn, runs locally.

SKILL.md

1.7 KB, as published. Nobody here has run it

seo-unlighthouse

Run Lighthouse against every URL on a site (up to a configurable cap) and aggregate the results. Useful when:

PageSpeed Insights' free quota (25k QPD) isn't enough for a large site.
You want offline / local CWV measurement (CI integration, restricted environments).
You need a quick site-wide regression check after a deploy.

Prerequisites

Run extensions/unlighthouse/install.sh (no API key needed).
Node 18+ on $PATH.

Routing

Command	Effect
`/seo unlighthouse <url>`	Mobile audit, up to 200 routes, JSON+HTML report in a temp dir
`/seo unlighthouse <url> --device desktop`	Desktop form factor
`/seo unlighthouse <url> --max-routes 50 --output-dir ./reports`	Cap + persist

All flags forward to scripts/unlighthouse_run.py which handles url_safety pre-flight and subprocess timeout management.

Output handling

The wrapper reads ci-result.json from the Unlighthouse output dir and returns it parsed. Aggregate fields:

score.performance (median across audited routes)
score.accessibility, score.bestPractices, score.seo
Per-route breakdown is available in <output_dir>/ci-result.json

Cross-skill delegation

For single-URL field data (CrUX), use seo-google psi / seo-google crux.
For LCP subpart decomposition on slow pages, use the scripts/lcp_subparts.py workflow (Phase C).