Skip to content
TrustedSkillsbeta
Back to all skills

Wp Performance

Official
wordpress·vlatest·backend

Analyzes WordPress site speed, identifies optimization opportunities, and suggests actionable performance improvements.

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 wordpress/agent-skills --skill wp-performance -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

wordpress

Matched to the vendor's own GitHub organisation.

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 wordpress/agent-skills at 3cf7f6f701.

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

Commit
3cf7f6f701
Manifest
skills/wp-performance/SKILL.md
Scanned
12 files, 533 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

The Wp Performance skill analyzes the speed of a WordPress site, page, or endpoint without requiring access to a browser UI. It identifies performance bottlenecks and suggests actionable improvements for areas like database queries, autoloaded options, object caching, cron tasks, and remote HTTP calls. The skill relies on tools accessible via command line (WP-CLI), logs, and HTTP requests.

When to use it

  • When a WordPress site or page is loading slowly (frontend TTFB, admin area, REST API endpoints, WP-Cron).
  • To receive recommendations for profiling plans and tooling (e.g., WP-CLI profile/doctor, Query Monitor, Xdebug/XHProf).
  • When optimizing database queries, autoloaded options, object caching, cron tasks, or remote HTTP calls is needed.
  • For diagnosing performance issues in development, staging, or production environments.

Key capabilities

  • Backend-only analysis: Operates without requiring a browser UI.
  • WP-CLI utilization: Leverages WP-CLI for profiling and diagnostics (if available).
  • Performance report generation: Creates deterministic performance reports using perf_inspect.mjs.
  • Diagnostic checks: Runs wp doctor to identify common WordPress configuration issues.
  • Profiling: Uses wp profile to analyze time spent in different phases of WordPress execution (bootstrap, main query, template).
  • Query Monitor integration: Provides headless access to Query Monitor data via REST API headers and response properties.

Example prompts

  • "Analyze the performance of my WordPress site at [URL] using WP-CLI."
  • "Run a wp doctor check on my WordPress installation located at [path]."
  • "Generate a backend performance report for the admin dashboard, targeting path [path]."

Tips & gotchas

  • Environment Restrictions: Be aware of any restrictions in the target environment (e.g., limitations on write operations like plugin installs or configuration changes).
  • Baseline Measurement: Always measure baseline performance before making any changes to ensure improvements are tracked accurately.
  • WP-CLI Dependency: The skill heavily relies on WP-CLI being available and functional on the WordPress server.