web-quality-skills MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

In der Praxis

web-quality-skill.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren 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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.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 nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

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
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "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
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.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 nutzt ein Array von Serverobjekten statt einer 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"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: web-quality-skills

Fix a slow LCP on a product landing page

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

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

Voraussetzungen

Target URL — Live or staging URL — not just local

Ablauf

Run the core-web-vitals skill

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

→ 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.✓ Kopiert

→ Concrete HTML changes
Re-measure

How do I verify the improvement?✓ Kopiert

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

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

Fallstricke

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

Wann einsetzen: Legal is asking about WCAG compliance for the checkout.

Ablauf

Run the accessibility skill

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

→ Structured findings per WCAG success criterion with severity
Prioritize fixes

Group by fix-effort vs user impact.✓ Kopiert

→ Ordered backlog

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

Fallstricke

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

Kombinieren mit: playwright-skill

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

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

Wann einsetzen: Big campaign starts Monday and you want no nasty surprises.

Ablauf

Run the combined audit

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

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

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

→ Go/no-go triage

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

Fallstricke

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

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.✓ Kopiert

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: 2-5k per skill loaded
Kosten in €: Free — skill is local
Tipp: Audit one URL at a time; batch audits balloon context.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — skill is prompts

Datenabfluss: None from the skill itself

Fehlerbehebung

Häufige Fehler und Lösungen

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.

Alternativen

web-quality-skills vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen