
This is your go-to when users complain about janky scrolling, frozen pages, or slow interactions. It wraps Joan Leon's webperf-snippets with smart decision trees that automatically chain diagnostics. If an interaction takes over 200ms, it'll break down the latency phases, hunt for long animation frames, then attribute blame to specific scripts. The workflows handle common scenarios like INP debugging and third-party script impact without you needing to remember which snippet runs next. Works through Chrome DevTools MCP, so you're running real performance APIs, not guessing. Best part is the cross-skill integration: it knows when to pull in script execution analysis from the loading skill or correlate layout shifts from Core Web Vitals.
$ npx -y skills add nucliweb/webperf-snippets --skill webperf-interaction --agent claude-codeInstalls into .claude/skills of the current project.
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.Sponsors