Total Skills
6
Author Profile: corewebvitals
Skills published by corewebvitals with real stars/downloads and source-aware metadata.
Total Stars
54
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
cwv-superpower
9
Stars
9
Downloads
0
diagnosing-cls
9
Stars
9
Downloads
0
diagnosing-inp
9
Stars
9
Downloads
0
diagnosing-lcp
9
Stars
9
Downloads
0
setting-up-coredash
9
Stars
9
Downloads
0
tracing-with-chrome
9
Stars
9
Downloads
0
Published Skills
cwv-superpower
Orchestrator for full Core Web Vitals diagnosis. Use when the user asks for a site audit, "find my biggest CWV issue", general page speed help, or multi-metric analysis. Dispatches to peer skills diagnosing-lcp, diagnosing-inp, diagnosing-cls, tracing-with-chrome, and setting-up-coredash. For a single named metric, the agent may invoke the matching diagnosing-* skill directly instead.
Repository SourceNeeds Review
diagnosing-cls
Use when diagnosing CLS (Cumulative Layout Shift) issues — visual layout jumps, content shifting during load, poor CLS at p75, or when the cwv-superpower orchestrator dispatches at Step 2B. Matches the shifting element to one of 5 cause patterns (images without dimensions, FOUT, injected content, late-loading resources, non-composited animations). Requires CoreDash MCP.
Repository SourceNeeds Review
diagnosing-inp
Use when diagnosing INP (Interaction to Next Paint) issues — slow/laggy clicks, delayed interactions, poor INP at p75, or when the cwv-superpower orchestrator dispatches at Step 2B. Identifies the slow interaction element, the bottleneck phase (INPUTDELAY/PROCESSING/PRESENTATION), and the responsible LOAF script. Requires CoreDash MCP.
Repository SourceNeeds Review
diagnosing-lcp
Use when diagnosing LCP (Largest Contentful Paint) issues — slow hero images, slow page loads, poor Largest Contentful Paint at p75, or when the cwv-superpower orchestrator dispatches at Step 2B. Identifies the LCP element, the bottleneck phase (TTFB/LOADDELAY/LOADTIME/RENDERDELAY), and the cause pattern. Requires CoreDash MCP.
Repository SourceNeeds Review
setting-up-coredash
Use when setting up the CoreDash MCP server for Core Web Vitals diagnosis — "how do I connect CoreDash", "set up CoreDash", "get a CoreDash API key", "CoreDash isn't connected", or when the cwv-superpower orchestrator has no CoreDash connection and the user wants to connect. Walks through client detection, account setup, API key generation, and per-client MCP configuration.
Repository SourceNeeds Review
tracing-with-chrome
Use when running a Chrome lab trace for a specific CWV bottleneck — investigating LCP/INP/CLS with browser tools after RUM has identified the target phase, element, and cause. Typically called by the cwv-superpower orchestrator at Step 3. Requires Chrome via chrome-devtools MCP.
Repository SourceNeeds Review