Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Performance

Listed
b-open-io·vlatest·frontend

Helps with frontend development, performance optimization as part of agent workflows 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 b-open-io/prompts --skill frontend-performance --full-depth -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

b-open-io

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No obfuscated payloads: failed

    Contains 1 obfuscated or encoded payload pattern.

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

    What it found

    • modules/web-dev/skills/frontend-performance/.clawnet/unsigned-skill.json:411394-character base64 literal
      "opReturnHex": "6a2231394878696756345179427633744870515663554551797131707a5a56646f4175744dfb132d2d2d0a6e616d653a2066726f6e74656e642d706572666f726d616e63650a766…

  • 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 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 b-open-io/prompts at 3e198cc712.

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

Commit
3e198cc712
Manifest
modules/web-dev/skills/frontend-performance/SKILL.md
Scanned
2 files, 212 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

frontend-performance

What it does

This skill equips AI agents to analyze and optimize the runtime performance of web applications. It focuses on identifying bottlenecks in rendering, resource loading, and execution efficiency to ensure smooth user experiences.

When to use it

  • Diagnosing slow page load times or high Time-to-Interactive (TTI) metrics.
  • Refactoring codebases to reduce unnecessary re-renders in frameworks like React or Vue.
  • Optimizing asset delivery strategies, such as image compression and lazy loading implementation.
  • Analyzing bundle sizes to minimize JavaScript payload overhead.

Key capabilities

  • Runtime performance profiling and bottleneck detection.
  • Rendering optimization analysis for single-page applications.
  • Resource loading efficiency evaluation.
  • Code execution speed assessment.

Example prompts

  • "Analyze the current rendering cycle of this React component and suggest optimizations to reduce re-renders."
  • "Identify the primary bottlenecks causing high latency in this web application's initial load."
  • "Review the JavaScript bundle size and propose strategies to minimize payload overhead without losing functionality."

Tips & gotchas

Ensure you have access to the application's source code or a live environment where profiling tools can be injected. Performance gains are often context-dependent; an optimization valid for one device type may not yield results on another, so always test across target platforms.