web-quality
Web quality optimization skills based on Google Lighthouse guidelines and Core Web Vitals. Use when asked to audit web quality, optimize performance, improve accessibility, fix SEO, apply best practices, or analyze Core Web Vitals (LCP, INP, CLS).
Works with
--- name: web-quality description: Web quality optimization skills based on Google Lighthouse guidelines and Core Web Vitals. Use when asked to audit web quality, optimize performance, improve accessibility, fix SEO, apply best practices, or analyze Core Web Vitals (LCP, INP, CLS). license: MIT --- # Web Quality Skills Comprehensive web quality optimization based on Google Lighthouse guidelines and Core Web Vitals. ## Available Sub-Skills | Skill | File | Triggers | |-------|------|----------| | Web Quality Audit | [web-quality-audit-SKILL.md](web-quality-audit-SKILL.md) | "audit", "quality review", "lighthouse" | | Performance | [performance-SKILL.md](performance-SKILL.md) | "speed up", "optimize", "load time" | | Core Web Vitals | [core-web-vitals-SKILL.md](core-web-vitals-SKILL.md) | "LCP", "INP", "CLS", "Core Web Vitals" | | Accessibility | [accessibility-SKILL.md](accessibility-SKILL.md) | "a11y", "WCAG", "accessible" | | SEO | [seo-SKILL.md](seo-SKILL.md) | "SEO", "meta tags", "search" | | Best Practices | [best-practices-SKILL.md](best-practices-SKILL.md) | "security", "best practices", "modern" | ## Key Thresholds **Core Web Vitals (Good):** - LCP: 2.5s or less - INP: 200ms or less - CLS: 0.1 or less **Performance Budgets:** - Total page weight: < 1.5 MB - JavaScript: < 300 KB - CSS: < 100 KB **Lighthouse Targets:** - Performance: 90+ - Accessibility: 100 - Best Practices: 95+ - SEO: 95+ ## Source From [addyosmani/web-quality-skills](https://github.com/addyosmani/web-quality-skills).
Related free tools on this site
More Performance skills
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
competitor-profiling
coreyhaines31/marketingskills
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
vercel-optimize
vercel-labs/agent-skills
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
