- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nucliweb/webperf-snippets --skill webperf-interaction -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nucliweb/webperf-snippets --skill webperf-interaction -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nucliweb/webperf-snippets --skill webperf-interaction -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add nucliweb/webperf-snippets --skill webperf-interaction -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/nucliweb/webperf-snippets/tree/HEAD/dist/antigravity/webperf-interactionVom Herausgeber
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/DOM-Size-and-Depth.js — DOM size and depthscripts/Forced-Synchronous-Layout.js — Forced synchronous layout detectorscripts/Input-Latency-Breakdown.js — Input latency breakdownscripts/Interactions.js — Interactionsscripts/Layout-Shift-Loading-and-Interaction.js — Layout shift trackingscripts/Long-Animation-Frames-Helpers.js — LoAF helpersscripts/Long-Animation-Frames-Script-Attribution.js — Long animation frames script attributionscripts/Long-Animation-Frames.js — Long animation frames (LoAF)scripts/LongTask.js — Long tasksscripts/Scroll-Performance.js — Scroll performance analysisWhen the user asks for interaction analysis or "audit responsiveness":
When INP is slow (>200ms) or the user asks "debug INP" or "slow interactions":
When the user reports "scroll jank", "choppy scrolling", or "scroll performance issues":
When the page feels unresponsive or the user asks "why is the page frozen":
When the user reports "things move when I click" or CLS issues during interaction:
When animations feel sluggish or the user asks "debug animation performance":
When interactions are slow and third-party scripts are suspected:
Use this decision tree to automatically run follow-up snippets based on results:
This is a utility snippet, use results to:
Use these thresholds to automatically trigger follow-up analysis:
INP Thresholds:
Long Animation Frames:
Long Tasks:
Scroll Performance:
Interaction Frequency:
When multiple interaction metrics are poor:
If Long Tasks AND Long Animation Frames both detected → Shared root cause:
If INP slow AND CLS high → Interaction-triggered layout shifts:
If Scroll jank AND Long Animation Frames → Scroll handlers blocking main thread:
references/snippets.md — Descriptions and thresholds for each scriptreferences/schema.md — Return value schema for interpreting script outputIntelligent interaction performance analysis with automated workflows for INP debugging, scroll jank investigation, and main thread blocking. Includes decision trees that automatically run script attr
---name: webperf-interactiondescription: Intelligent interaction performance analysis with automated workflows for INP debugging, scroll jank…---# dist/antigravity/webperf-interaction/SKILL.mdÜbersicht
Intelligent interaction performance analysis with automated workflows for INP debugging, scroll jank investigation, and main thread blocking. Includes decision trees that automatically run script attribution when long frames detected, break down input latency phases, and correlate layout shifts with interactions. Features workflows for complete interaction audit, third-party script impact analysis, and animation performance debugging. Cross-skill integration with Core Web Vitals (INP/CLS correlation) and Loading (script execution analysis). Use when the user asks about slow interactions, janky scrolling, unresponsive pages, or INP optimization. Compatible with Chrome DevTools MCP.
FAQ
Laden Sie dist/antigravity/webperf-interaction/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/nucliweb/webperf-snippets.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.