Web Quality Audit
Run an evidence-led web quality audit: performance, accessibility, SEO, best practices
- What
- Run an evidence-led web quality audit: performance, accessibility, SEO, best practices
- Cost
- Free
- Needs
- none beyond a working agent; browser tooling (Chrome DevTools MCP or Lighthouse CLI) recommended for the full audit
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an evidence-led web quality audit orchestrator: establish the audit target, collect a live baseline, then review Performance (Core Web Vitals — LCP < 2.5s, INP < 200ms, CLS < 0.1), Accessibility (WCAG AA: alt text, contrast, keyboard, focus), SEO, Best Practices, and Agentic Browsing — keeping measured findings separate from code-only hypotheses, categorizing by user impact, and re-running checks after fixes. Routing: live browser traces or Lighthouse audits where available, Lighthouse CLI/PageSpeed Insights as fallback, plus a static analyzer as a fast smoke test (never a substitute for a rendered-page audit). Partly overlaps the already-listed addyosmani-performance — the Performance section points at that skill's measurement workflow — but this is a broader audit orchestrator, not a duplicate: five categories, source inspection, and fix verification instead of performance alone. By @addyosmani, listed here with credit to its creator. Honest caveats: it audits — it doesn't fix; some findings will need field data or human validation; best run with browser tooling (Chrome DevTools MCP or Lighthouse CLI) available. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Web Quality Audit is a free Muse skill that runs an evidence-led web quality audit: establish the target, collect a live baseline, then review performance, accessibility, SEO, best practices and agentic browsing. It keeps measured findings separate from code-only hypotheses, categorizes by user impact, and re-runs checks after fixes, using live browser traces or Lighthouse audits where available.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit afa8da9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none beyond a working agent; browser tooling (Chrome DevTools MCP or Lighthouse CLI) recommended for the full audit Install "Web Quality Audit" for me. Run an evidence-led web quality audit: performance, accessibility, SEO, best practices Repository: https://raw.githubusercontent.com/addyosmani/web-quality-skills/afa8da942115f2961fdbfa80807ea0b232ff6c00/skills/web-quality-audit/SKILL.md Pinned version: install the code at commit afa8da942115f2961fdbfa80807ea0b232ff6c00 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the addyosmani-web-quality-audit skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "addyosmani-web-quality-audit". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- afa8da9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.