- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nucliweb/webperf-snippets --skill webperf-core-web-vitals -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nucliweb/webperf-snippets --skill webperf-core-web-vitals -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nucliweb/webperf-snippets --skill webperf-core-web-vitals -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add nucliweb/webperf-snippets --skill webperf-core-web-vitals -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/nucliweb/webperf-snippets/tree/HEAD/.claude/skills/webperf-core-web-vitals게시자 제공
JavaScript snippets for measuring web performance in Chrome DevTools.
mcp__chrome-devtools__evaluate_script, passing the file instead of its code: sourcePath with the absolute path of scripts/<Name>.js in this skill, and format: "script", since a script runs by itself and is not a function. Read the object it returns. The scripts have no console output, so the returned object is the result: script, status and the metric data (value, rating, details, items, issues), as described in references/schema.md.status is "tracking", the script keeps observing the page. After the interactions, call the function named in getDataFn with another mcp__chrome-devtools__evaluate_script call, as an arrow function in function, for example () => getINP(), and read the object it returns.status is "error" or "unsupported", read error: the page may not have loaded yet, or the browser lacks the API.sourcePath and format need Chrome DevTools MCP 1.11.0 or later, and the server only reads files inside its workspace roots: the project, the temp folder and each --workspace=<folder> in its arguments. When it answers Access denied, as it does for a skill installed outside the project, such as in ~/.claude/skills/, read the file and pass its code in function, still with format: "script". A --workspace with the real folder of the skills makes the path work; the server follows symlinks, so a link to the folder is not enough.
Without Chrome DevTools MCP, run the same snippet with the webperf-snippets CLI, which loads the page in headless Chromium and prints the same result objects: npx webperf-snippets <url> --snippet <Name> --json, where <Name> is the script name without .js. It needs Playwright and Chromium (npm install --save-dev webperf-snippets playwright, then npx playwright install chromium), and tracking snippets take --interact-script <file> to drive the interactions.
scripts/CLS.js — Cumulative layout shift (CLS)scripts/INP.js — Interaction to next paint (INP)scripts/LCP-Image-Entropy.js — LCP image entropyscripts/LCP-Subparts.js — LCP subpartsscripts/LCP-Trail.js — LCP trailscripts/LCP-Video-Candidate.js — LCP video candidatescripts/LCP.js — Largest contentful paint (LCP)When the user asks for a comprehensive Core Web Vitals analysis or "audit CWV":
When LCP is slow or the user asks "debug LCP" or "why is LCP slow":
When layout shifts are detected or the user asks "debug CLS" or "layout shift issues":
When interactions feel slow or the user asks "debug INP" or "slow interactions":
getINP() after interactions, getINPDetails() for the 15 slowest interactionsWhen LCP is a video element (detected by LCP-Video-Candidate.js):
When LCP is an image (most common case):
Use this decision tree to automatically run follow-up snippets based on results:
getINPDetails() for the 15 slowest interactions, slowest first (useful for identifying patterns across multiple slow interactions)status: "error" → Check if the page has finished loading:
status: "error" → Tell the user: "LCP data is not available yet. Please ensure the page has fully loaded, then run the analysis again."getINP() returns status: "error" → The getDataFn: "getINP" field signals the agent can retry after user interaction. Prompt the user to click, type, or scroll, then call getINP() again.Context fork note: This skill runs with
context: fork. Cross-skill triggers below are recommendations to report back to the parent agent, not direct calls this subagent can execute. When a cross-skill trigger fires, tell the user which skill and script to run next. Scripts marked (pending) are not yet available — skip them and note the limitation.
These triggers recommend using snippets from other skills:
If LCP > 2.5s and TTFB phase is dominant → Use webperf-loading skill:
If LCP image is lazy-loaded → Use webperf-loading skill:
If LCP has no fetchpriority → Use webperf-loading skill:
If CLS caused by fonts → Use webperf-loading skill:
If CLS caused by images → Use webperf-media skill:
When multiple CWV metrics are poor, prioritize investigation:
If LCP > 2.5s AND CLS > 0.1 → Likely shared root cause:
If LCP > 2.5s AND INP > 200ms → Main thread congestion:
If CLS > 0.1 AND INP > 200ms → Layout thrashing or interaction-triggered shifts:
references/snippets.md — Descriptions and thresholds for each scriptreferences/schema.md — Return value schema for interpreting script outputIntelligent Core Web Vitals analysis with automated workflows and decision trees. Measures LCP, CLS, INP with guided debugging that automatically determines follow-up analysis based on results. Includ
---name: webperf-core-web-vitalsdescription: Intelligent Core Web Vitals analysis with automated workflows and decision trees. Measures LCP, CLS, INP with…---# .claude/skills/webperf-core-web-vitals/SKILL.md개요
Intelligent Core Web Vitals analysis with automated workflows and decision trees. Measures LCP, CLS, INP with guided debugging that automatically determines follow-up analysis based on results. Includes workflows for LCP deep dive (5 phases), CLS investigation (loading vs interaction), INP debugging (latency breakdown + attribution), and cross-skill integration with loading, interaction, and media skills. Use when the user asks about Core Web Vitals, LCP optimization, layout shifts, or interaction responsiveness. Compatible with Chrome DevTools MCP.
FAQ
게시자에게서 .claude/skills/webperf-core-web-vitals/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/nucliweb/webperf-snippets에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.