web-quality-audit

by addyosmani2.9k

Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add addyosmani/web-quality-skills --skill web-quality-audit -a cursor -y

Download skill skills/web-quality-audit/SKILL.md on GitHub

Related skills

View all

Questions

How do I install web-quality-audit?: Download skills/web-quality-audit/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does web-quality-audit live?: The publisher keeps it at https://github.com/addyosmani/web-quality-skills.
Which agents can use web-quality-audit?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: web-quality-audit description: Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website". license: MIT metadata: author: web-quality-skills version: "2.0"

Web quality audit

Comprehensive quality review that combines live browser evidence with source inspection. Covers Performance, Accessibility, SEO, Best Practices, and Agentic Browsing without treating an aggregate score as proof of quality.

Need	Preferred route	Fallback
Performance and Core Web Vitals	Record a browser performance trace and analyze focused insights; with Chrome DevTools MCP, use `performance_start_trace` then `performance_analyze_insight`	Lighthouse CLI or PageSpeed Insights lab data
Real-user performance	CrUX values included in current DevTools trace summaries	PageSpeed Insights/CrUX Vis; direct CrUX API only when a key is already available or automation is requested
Accessibility, SEO, Best Practices, Agentic Browsing	Run a live Lighthouse audit; with Chrome DevTools MCP, use `lighthouse_audit`	Category-specific Lighthouse CLI audits plus manual checks
Rendered semantics and interaction	Inspect the accessibility tree and exercise the UI; with Chrome DevTools MCP, use `take_snapshot` and focused `evaluate_script`	Browser/manual testing
Source smoke test	`scripts/analyze.sh <path>`	Direct source inspection

Level	Description	Action
Critical	Security vulnerabilities, complete failures	Fix immediately
High	Core Web Vitals failures, major a11y barriers	Fix before launch
Medium	Performance opportunities, SEO improvements	Fix within sprint
Low	Minor optimizations, code quality	Fix when convenient

web-quality-audit

Install

Related skills

Questions

Web quality audit

How it works

Tool routing

Audit categories

Performance

Accessibility

SEO

Best practices

Agentic browsing

Severity levels

Audit output format

Quick checklist

Before every deploy

Weekly review

Monthly deep dive

References