/ Annuaire / Playground / web-quality-skills
● Communauté addyosmani ⚡ Instantané

web-quality-skills

par addyosmani · addyosmani/web-quality-skills

6 skills encoding 150+ Lighthouse audits and Core Web Vitals patterns — Claude diagnoses and fixes LCP, INP, CLS, and accessibility issues.

A focused skill bundle from addyosmani covering web-quality-audit, performance, core-web-vitals, accessibility (WCAG 2.2), seo, and best-practices. Skills auto-activate on relevant asks (e.g. 'speed up my site' loads the performance skill). Framework-agnostic — works for React, Vue, Svelte, Next, Astro, and plain HTML.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

web-quality-skill.replay ▶ prêt
0/0

Installer

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

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la 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
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.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 utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : web-quality-skills

Fix a slow LCP on a product landing page

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

Quand l'utiliser : CrUX shows LCP at 3.8s and you don't know where to start.

Prérequis
  • Target URL — Live or staging URL — not just local
Déroulement
  1. Run the core-web-vitals skill
    Use the core-web-vitals skill on https://site.com. Focus on LCP.✓ Copié
    → Diagnosis of the LCP element (hero image, web font, server response) with specific fix
  2. Apply the fix
    Apply the recommended priority hints and image format change.✓ Copié
    → Concrete HTML changes
  3. Re-measure
    How do I verify the improvement?✓ Copié
    → Guided re-measure via Lighthouse or web-vitals JS

Résultat : LCP under the 2.5s target with a documented fix path.

Pièges
  • 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

Quand l'utiliser : Legal is asking about WCAG compliance for the checkout.

Déroulement
  1. Run the accessibility skill
    Use the accessibility skill on our checkout flow. What WCAG 2.2 issues exist?✓ Copié
    → Structured findings per WCAG success criterion with severity
  2. Prioritize fixes
    Group by fix-effort vs user impact.✓ Copié
    → Ordered backlog

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

Pièges
  • Automated checks only catch ~30% of issues — Complement with keyboard-only and screen-reader manual testing
Combiner avec : playwright-skill

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

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

Quand l'utiliser : Big campaign starts Monday and you want no nasty surprises.

Déroulement
  1. Run the combined audit
    Use web-quality-audit on our campaign landing page.✓ Copié
    → Report spanning performance, CWV, accessibility, SEO, best-practices
  2. Triage for launch
    What must be fixed before launch vs can wait?✓ Copié
    → Go/no-go triage

Résultat : A launch-ready page and a week-2 backlog.

Pièges
  • Treating every finding as blocker — The skill prioritizes — trust the must-fix list

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié
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.✓ Copié
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.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
web-quality-audit URL Pre-launch or quarterly 0
performance URL Slow page 0
core-web-vitals URL Failing CWV 0
accessibility URL / component A11y review 0
seo URL SEO hygiene check 0
best-practices URL Hardening review 0

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
2-5k per skill loaded
Monétaire
Free — skill is local
Astuce
Audit one URL at a time; batch audits balloon context.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials — skill is prompts
Sortie de données : None from the skill itself

Dépannage

Erreurs courantes et correctifs

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 autres

AlternativeQuand l'utiliserCompromis
Lighthouse CI directlyYou want automated CI gates, not interactive guidanceScalable for CI; less explanatory
claude-seo-skillYou need SEO-first with broader audit surfaceBroader scope but less CWV depth

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills