cloudflare-web-perf — Claude Code skill: what it does, how to install
cloudflare-web-perf audits Core Web Vitals, render-blocking assets, and Lighthouse performance scores. It diagnoses and fixes LCP, INP, and CLS bottlenecks using Chrome DevTools traces.
MIT 221 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill cloudflare-web-perf -a claude-codeWhat cloudflare-web-perf does
This skill audits page loading speed and interaction metrics. It directs the agent to fetch up-to-date metric thresholds directly from web.dev and Chrome documentation instead of relying on training weights. Every fix proposed by the model must quantify its anticipated impact.
Full diagnostic depth depends on the chrome-devtools-mcp server. Without this MCP tool, the skill falls back to inspecting static source code and network waterfalls, flagging any missing measurements. Recommendations remain vendor-agnostic and work outside Cloudflare infrastructure.
The guidance explicitly avoids accessibility audits such as ARIA roles or color contrast. For tuning React and Next.js component rendering, upstream documentation advises alternative skill sets.
What it helps with
- diagnose slow Largest Contentful Paint (LCP) causes
- identify interaction delays and fix poor INP scores
- detect Cumulative Layout Shift (CLS) and render-blocking assets
- prioritize Lighthouse optimizations with estimated impact
Example prompts for the agent
- Audit Core Web Vitals on the home page and spot render-blocking files
- Why is our mobile LCP score degraded? Analyze the trace and quantify fixes
- Inspect interaction latency to improve INP before our next release
How to install cloudflare-web-perf
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill cloudflare-web-perf -a claude-code2Manually: put the files in place
~/.claude/skills/cloudflare-web-perf/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cloudflare-web-perf/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill cloudflare-web-perf -a codex2Manually: put the files in place
.agents/skills/cloudflare-web-perf/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill cloudflare-web-perf -a cursor2Manually: put the files in place
.cursor/skills/cloudflare-web-perf/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/cloudflare-web-perf2Manually: put the files in place
.github/skills/cloudflare-web-perf/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill cloudflare-web-perf -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/cloudflare-web-perfManually: put the files in place
.devin/skills/cloudflare-web-perf/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill cloudflare-web-perf -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cloudflare-web-perf
How do I install cloudflare-web-perf in Claude Code?
Run npx skills add podo/design-agent-skills --skill cloudflare-web-perf -a claude-code. The skill configuration is placed at ~/.claude/skills/cloudflare-web-perf/SKILL.md.
What does the cloudflare-web-perf skill do?
It guides the agent through auditing Core Web Vitals (LCP, INP, CLS) and Lighthouse scores. The agent identifies render-blocking files, retrieves fresh thresholds from web.dev, and quantifies improvements.
Is the Chrome DevTools MCP server strictly required?
The chrome-devtools-mcp server is required for performance traces. Without it, the skill relies on source code and network inspection while noting uncollected measurements.
Source text
SKILL.md · MIT
--- name: cloudflare-web-perf description: | Audit Core Web Vitals and render-blocking resources. Official skill published by Cloudflare for diagnosing and fixing LCP, INP, CLS and Lighthouse performance issues, driven by Chrome DevTools performance traces. triggers: - "web performance" - "Core Web Vitals" - "LCP" - "CLS" - "INP" - "render blocking" - "cloudflare performance" das: category: accessibility-quality upstream: "https://github.com/cloudflare/skills" upstream_path: "skills/web-perf/SKILL.md" version: latest install: true --- # cloudflare-web-perf > Catalogue stub — full skill: [cloudflare/skills](https://github.com/cloudflare/skills/blob/main/skills/web-perf/SKILL.md) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **Is the full skill already installed?** Upstream names this skill `web-perf`, so it installs next to this pointer (the pointer is not replaced). - Global: `f=~/.agents/skills/web-perf/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - Project: `f=.agents/skills/web-perf/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → the skill is installed as `web-perf`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/cloudflare-web-perf ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add cloudflare/skills --skill web-perf -g -y ``` **Project:** ```bash npx skills add cloudflare/skills --skill web-perf -y ``` > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation. **Heads-up** - **Requires:** Chrome DevTools MCP server (chrome-devtools-mcp) for performance traces; without it the skill falls back to source and network analysis and says which measurements it could not collect - **License:** Apache-2.0 <!-- das:install:end --> ## Invoke after install - Skill name: `web-perf` - Trigger phrases: "web performance", "Core Web Vitals", "LCP", "CLS", "render blocking" ## What it does Cloudflare's official skill for auditing and diagnosing website loading and interaction performance: Core Web Vitals (LCP, INP, CLS), Lighthouse performance scores and render-blocking resources. It tells the agent to retrieve current thresholds from web.dev and Chrome documentation rather than rely on memory, to use Chrome DevTools MCP traces when available, and to quantify the impact of each recommendation. The guidance is generic; it is not specific to Cloudflare products. ## When NOT to use - Accessibility audits (ARIA, keyboard, contrast) — use `fixing-accessibility` or `wcag-audit-patterns` - React or Next.js render performance specifically — use `vercel-skills`
© podo · MIT · podo/design-agent-skills