Skip to content
TrustedSkillsbeta
Back to all skills

Core Web Vitals

Checked
tech-leads-club·vlatest·frontend

Analyzes Core Web Vitals on your frontend codebase, providing actionable insights for performance optimization and user experience.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tech-leads-club/agent-skills --skill core-web-vitals -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tech-leads-club

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tech-leads-club/agent-skills at 6df68d5202.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6df68d5202
Manifest
packages/skills-catalog/skills/(performance)/core-web-vitals/SKILL.md
Scanned
2 files, 611 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill analyzes your frontend codebase to assess Core Web Vitals performance, providing insights for optimization and improved user experience. It focuses on three key metrics – Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS) – which directly impact Google Search ranking. The analysis considers the 75th percentile of page visits as a benchmark for good performance, aligning with how Google measures these metrics.

When to use it

  • You want to improve your website's Google Search ranking.
  • You’re experiencing user experience issues related to slow loading times or visual instability.
  • You need to identify and address specific bottlenecks affecting LCP, INP, or CLS performance.
  • You are performing a frontend audit and want data-driven insights for optimization.

Key capabilities

  • Core Web Vitals Analysis: Evaluates LCP, INP, and CLS metrics.
  • Metric Thresholds: Provides clear "Good," "Needs Work," and "Poor" classifications based on established thresholds.
  • Issue Identification: Highlights common issues impacting LCP (e.g., slow server response, render-blocking resources, slow resource load times, client-side rendering delays).
  • Optimization Suggestions: Offers potential fixes for identified LCP problems, such as using CDNs, inlining critical CSS, preloading resources, and implementing server-side or static rendering.

Example prompts

  • "Analyze the Core Web Vitals performance of my frontend codebase."
  • "What are the common issues affecting Largest Contentful Paint (LCP)?"
  • "Suggest optimizations for Cumulative Layout Shift (CLS)."

Tips & gotchas

  • The skill focuses specifically on Core Web Vitals and doesn’t cover other aspects of website performance.
  • Google measures these metrics at the 75th percentile, so ensure your optimization efforts address this benchmark.
  • Pay attention to the provided checklists for LCP optimization – implementing suggested changes can significantly improve performance.