Skip to content
TrustedSkillsbeta
Back to all skills

Performance Profiling

Checked
davila7·vlatest·frontend·MIT

Analyzes frontend code performance bottlenecks using detailed metrics and visualizations for optimization by davila7.

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 davila7/claude-code-templates --skill performance-profiling -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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/performance-profiling/SKILL.md
Scanned
2 files, 219 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

The performance-profiling skill enables AI agents to analyze frontend application efficiency by executing browser DevTools commands. It specifically targets the Chrome Performance API to capture metrics like frame rates, memory usage, and network timing during user interactions.

When to use it

  • Diagnosing slow rendering or jank in complex React or Vue applications before production deployment.
  • Investigating high CPU or memory spikes triggered by specific user actions or data loads.
  • Validating the impact of code optimizations, such as lazy loading or image compression strategies.
  • Generating detailed performance reports for client deliverables or internal engineering reviews.

Key capabilities

  • Launches Chrome DevTools programmatically to access the Performance tab.
  • Captures real-time metrics including FPS (frames per second) and frame timing data.
  • Records network requests and their associated latency during profiling sessions.
  • Generates downloadable trace files for deep-dive analysis in external tools.

Example prompts

  • "Run a performance profile on the current page while I click through the checkout flow, then summarize any bottlenecks found."
  • "Capture a memory snapshot every 5 seconds during this video playback test and report total heap usage."
  • "Profile the network activity of this dashboard load and list all requests taking longer than 200ms."

Tips & gotchos

Ensure the target application is hosted on a secure connection (HTTPS) to allow DevTools access. Profiling adds overhead, so run tests in incognito mode or with caching disabled to get accurate baseline metrics.