core-web-vitals-tuner
Systematically improves Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) with prioritized fixes and verification. Use for "Core Web Vitals", "performance", "LCP", "INP", or "CLS".
Works with
---
name: core-web-vitals-tuner
description: Systematically improves Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) with prioritized fixes and verification. Use for "Core Web Vitals", "performance", "LCP", "INP", or "CLS".
license: MIT
---
# Core Web Vitals Tuner
Improve LCP, INP, and CLS systematically.
## LCP Optimization (<2.5s)
**Prioritized Fixes:**
1. **Optimize images** (Biggest impact)
```html
<!-- Before -->
<img src="hero.jpg" />
<!-- After -->
<img
src="hero.jpg"
srcset="hero-400.webp 400w, hero-800.webp 800w, hero-1200.webp 1200w"
sizes="(max-width: 600px) 400px, (max-width: 1200px) 800px, 1200px"
loading="eager"
fetchpriority="high"
/>
```
2. **Preload LCP resource**
```html
<link rel="preload" as="image" href="/hero.webp" fetchpriority="high" />
```
3. **Inline critical CSS**
```html
<style>
/* Above-the-fold styles */
.hero {
display: flex;
height: 100vh;
}
</style>
```
4. **Use CDN**
- Serve images from CloudFront/Cloudflare
- Enable HTTP/2 or HTTP/3
## INP Optimization (<200ms)
**Fixes:**
1. **Debounce expensive interactions**
```typescript
import { debounce } from "lodash";
const handleSearch = debounce((query) => {
fetchResults(query);
}, 300);
```
2. **Use Web Workers for heavy tasks**
```typescript
const worker = new Worker("processor.js");
worker.postMessage(largeData);
worker.onmessage = (e) => console.log(e.data);
```
3. **Code splitting**
```typescript
const HeavyComponent = lazy(() => import("./HeavyComponent"));
```
## CLS Optimization (<0.1)
**Fixes:**
1. **Reserve space for images/ads**
```html
<img src="banner.jpg" width="1200" height="600" />
```
2. **Use CSS aspect-ratio**
```css
.video-container {
aspect-ratio: 16 / 9;
}
```
3. **Avoid injecting content above existing**
```css
.notification {
position: fixed;
top: 0;
}
```
## Verification
```bash
# Lighthouse CI
npm run lighthouse -- --url=https://example.com
# Web Vitals in production
import { getCLS, getFID, getLCP } from 'web-vitals';
getCLS(console.log);
getFID(console.log);
getLCP(console.log);
```
## Output Checklist
- [ ] LCP optimized (<2.5s)
- [ ] INP optimized (<200ms)
- [ ] CLS optimized (<0.1)
- [ ] Monitoring in place
- [ ] Performance regression tests
ENDFILEMore 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.

