Skip to content
TrustedSkillsbeta
Back to all skills

Debug Optimize Lcp

Checked
chromedevtools·vlatest·testing·Apache-2.0

Helps with debugging, optimization as part of testing, debugging, and quality assurance workflows.

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 chromedevtools/chrome-devtools-mcp --skill debug-optimize-lcp -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

chromedevtools

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 chromedevtools/chrome-devtools-mcp at 47c5b3753d.

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

Commit
47c5b3753d
Manifest
skills/debug-optimize-lcp/SKILL.md
Scanned
5 files, 289 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 enables AI agents to analyze and optimize Largest Contentful Paint (LCP) metrics directly within Chrome DevTools. It helps identify specific rendering bottlenecks that delay the loading of a page's most significant element, allowing for targeted performance improvements.

When to use it

  • Diagnosing why a hero image or main video fails to load quickly on mobile devices.
  • Tuning resource hints and preloading strategies to ensure critical content appears first.
  • Validating the impact of CSS/JS optimizations on core web vitals before deployment.
  • Investigating network latency issues affecting the primary content delivery path.

Key capabilities

  • Accesses real-time LCP metrics from Chrome DevTools performance traces.
  • Identifies specific resources or rendering steps causing delays.
  • Provides actionable insights to reduce time-to-interactive for critical content.

Example prompts

  • "Analyze the current page's LCP score and tell me which resource is blocking it."
  • "Optimize the Largest Contentful Paint by suggesting changes to the network requests."
  • "Run a performance audit focusing solely on improving the main image load time."

Tips & gotchas

Ensure the target website is fully loaded before invoking this skill, as LCP metrics require a complete render cycle. This tool relies on Chrome DevTools infrastructure, so it is most effective when used in environments where Chrome debugging protocols are accessible.