229 skills · sorted by relevance
Capture an entire web page as a full-page screenshot using Chrome DevTools Protocol, Chrome's developer control interface. The workflow needs no additional dependencies and provides page images for portfolios, case studies, and audit reports.
Review early connections to third-party services such as fonts and APIs. Use loading measurements to identify essential domains, recommend preconnect hints that prepare connections in advance, and remove unnecessary hints that add overhead.
Audit web images that are larger than their displayed size and help serve suitable versions for different screens. Review image dimensions, responsive image settings, and Lighthouse findings, then provide updated HTML and steps to verify the changes.
Audit a page’s HTTP requests to find unnecessary network activity behind slow loading. Confirm bottlenecks with performance measurements, then suggest changes such as combining files, grouping icons, or embedding resources needed for the initial display.
Measure how quickly a webpage updates after user interactions using INP, a responsiveness metric. Identify confirmed bottlenecks and improve event handlers, split long tasks, or move heavy computation to web workers.
Investigate slow page loads and check whether resources use HTTP/2 or HTTP/3. Measure the actual bottleneck, then recommend server or CDN changes where appropriate, explaining how shared connections and compressed headers affect loading.
Audit page speed in a real browser to find delays in loading, script execution, and layout. Use measured results to identify bottlenecks, compare device and connection conditions, and guide performance improvements.
Audit slow page loads by measuring how static files, such as images and scripts, are delivered. Check CDN usage, a network of distributed servers, and identify caching or delivery settings that need improvement.
Find broken or fragile image references in markup, styles, and components. Correct paths, restore missing assets, and add fallback images, then verify how the page behaves when image requests fail.
Investigate growing memory usage in Qwen Code CLI by comparing heap snapshots, records of objects in memory. Trace what keeps objects alive, identify likely causes, and repeat the workload to verify a fix.
Debug json-render interfaces with an inspector panel that shows screen specifications, editable runtime state, action history, and streamed updates. Select a rendered page element to locate its definition and investigate display or interaction problems.
Plan, implement, or review chrome devtools work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests chrome devtools work.
The English summary is being prepared. Showing the original description.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
The English summary is being prepared. Showing the original description.
Verify web apps with browser DevTools—DOM, console, network, performance, and accessibility at runtime. Use with Chrome DevTools MCP or headless browser tools.
The English summary is being prepared. Showing the original description.
This skill provides guidance for using Chrome DevTools MCP for browser debugging and automation. Use when debugging web pages, analyzing performance, inspecting network requests, viewing console messages, or interacting with Chrome DevTools features programmatically.
The English summary is being prepared. Showing the original description.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
The English summary is being prepared. Showing the original description.
Uses the chrome-devtools-axi CLI for browser automation, accessibility-tree snapshots, console and network inspection, screenshots, Lighthouse audits, and performance traces. Use when interacting with Chrome from the shell, especially when the user mentions chrome-devtools-axi, AX snapshots, browser debugging, or DevTools automation from the command line.
The English summary is being prepared. Showing the original description.
Guide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.
The English summary is being prepared. Showing the original description.
Investigate Node.js bugs by pausing execution, examining variables, and stepping through code. Diagnose stalled asynchronous work and unreliable tests, or collect memory snapshots and CPU profiles to investigate growing memory use and slow execution.
Build web animations with GSAP plugins for text, SVG graphics, dragging, scrolling, and layout changes. It guides plugin selection, registration, configuration, and cleanup, with examples for implementing effects and reviewing existing animation code.
Measure page loading speed and identify what prevents a page from loading in under three seconds. Use performance measurements to guide improvements such as lazy loading, caching, CDN delivery, and reducing resource costs.
Review slow page loads and choose resource hints, browser instructions that start loading or connecting earlier. Use measurements to identify bottlenecks, then recommend preload, preconnect, prefetch, or dns-prefetch for important assets and likely next-page resources.
Measure the total size of a web page and its resources, identify what slows loading, and reduce unnecessary weight. Use a 1500KB limit to guide image optimization, code compression, and removal of unused resources.
Audit page loading and choose resource hints, browser instructions for fetching files or preparing connections early. Use measurements to identify delays, then suggest preload, preconnect, prefetch, or dns-prefetch for critical assets, external services, and likely next-page resources.