web-quality-skills MCP — Use Cases, Install & Live Demo

Why use it

Key features

6 skills covering the Lighthouse + Core Web Vitals matrix
Explicit targets: LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1
WCAG 2.2 accessibility auditing
Framework-agnostic recommendations
Auto-activation on matching requests

Live Demo

What it looks like in practice

web-quality-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "web-quality-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/addyosmani/web-quality-skills",
        "~/.claude/skills/web-quality-skills"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "web-quality-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/addyosmani/web-quality-skills",
        "~/.claude/skills/web-quality-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "web-quality-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/addyosmani/web-quality-skills",
        "~/.claude/skills/web-quality-skills"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "web-quality-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/addyosmani/web-quality-skills",
        "~/.claude/skills/web-quality-skills"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "web-quality-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/addyosmani/web-quality-skills",
        "~/.claude/skills/web-quality-skills"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "web-quality-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/addyosmani/web-quality-skills",
          "~/.claude/skills/web-quality-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add web-quality-skill -- git clone https://github.com/addyosmani/web-quality-skills ~/.claude/skills/web-quality-skills

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use web-quality-skills

Fix a slow LCP on a product landing page

👤 Frontend engineers trying to get a green CWV ⏱ ~40 min intermediate

When to use: CrUX shows LCP at 3.8s and you don't know where to start.

Prerequisites

Target URL — Live or staging URL — not just local

Flow

Run the core-web-vitals skill

Use the core-web-vitals skill on https://site.com. Focus on LCP.✓ Copied

→ Diagnosis of the LCP element (hero image, web font, server response) with specific fix
Apply the fix

Apply the recommended priority hints and image format change.✓ Copied

→ Concrete HTML changes
Re-measure

How do I verify the improvement?✓ Copied

→ Guided re-measure via Lighthouse or web-vitals JS

Outcome: LCP under the 2.5s target with a documented fix path.

Pitfalls

Fixing lab LCP but not field LCP (CrUX) — Always verify in CrUX, not just local Lighthouse

Run a WCAG 2.2 accessibility audit on a checkout flow

👤 Engineers preparing for an accessibility review ⏱ ~45 min intermediate

When to use: Legal is asking about WCAG compliance for the checkout.

Flow

Run the accessibility skill

Use the accessibility skill on our checkout flow. What WCAG 2.2 issues exist?✓ Copied

→ Structured findings per WCAG success criterion with severity
Prioritize fixes

Group by fix-effort vs user impact.✓ Copied

→ Ordered backlog

Outcome: A real accessibility backlog, not a checklist you can't act on.

Pitfalls

Automated checks only catch ~30% of issues — Complement with keyboard-only and screen-reader manual testing

Combine with: playwright-skill

Run the full web-quality-audit before a marketing campaign

👤 Teams about to drive paid traffic ⏱ ~30 min intermediate

When to use: Big campaign starts Monday and you want no nasty surprises.

Flow

Run the combined audit

Use web-quality-audit on our campaign landing page.✓ Copied

→ Report spanning performance, CWV, accessibility, SEO, best-practices
Triage for launch

What must be fixed before launch vs can wait?✓ Copied

→ Go/no-go triage

Outcome: A launch-ready page and a week-2 backlog.

Pitfalls

Treating every finding as blocker — The skill prioritizes — trust the must-fix list

Combinations

Pair with other MCPs for X10 leverage

web-quality-skill + chrome-devtools

Use DevTools MCP to grab live perf traces while the skill interprets them

Capture a perf trace via chrome-devtools, then have the performance skill analyze it.✓ Copied

web-quality-skill + playwright-skill

Playwright runs the site through real user flows, web-quality skills score each step

Use playwright to walk through checkout, capture metrics at each step, then accessibility-audit each screen.✓ Copied

web-quality-skill + claude-seo-skill

Technical SEO from claude-seo + CWV from this skill

Run /seo audit for link/schema issues, then web-quality-audit for CWV.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
web-quality-audit	URL	Pre-launch or quarterly
performance	URL	Slow page
core-web-vitals	URL	Failing CWV
accessibility	URL / component	A11y review
seo	URL	SEO hygiene check
best-practices	URL	Hardening review

Cost & Limits

What this costs to run

API quota: None
Tokens per call: 2-5k per skill loaded
Monetary: Free — skill is local
Tip: Audit one URL at a time; batch audits balloon context.

Security

Permissions, secrets, blast radius

Credential storage: No credentials — skill is prompts

Data egress: None from the skill itself

Troubleshooting

Common errors and fixes

Skill gives generic advice

Feed in a real Lighthouse JSON or CrUX record for specific findings.

Recommendations don't apply to your framework

Name the framework ('Next.js 15 app router') so the skill tailors suggestions.

Alternatives

web-quality-skills vs others

Alternative	When to use it instead	Tradeoff
Lighthouse CI directly	You want automated CI gates, not interactive guidance	Scalable for CI; less explanatory
claude-seo-skill	You need SEO-first with broader audit surface	Broader scope but less CWV depth

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills