Wp Performance
OfficialAutomatically optimizes WordPress site performance—images, caching, database—for faster loading times and improved user experience.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add automattic/agent-skills --skill wp-performance -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
automattic
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.
Automated safety checks
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 automattic/agent-skills at 48d4aa21d0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 48d4aa21d0
- Manifest
- skills/wp-performance/SKILL.md
- Scanned
- 12 files, 526 lines
About this skill
What it does
This skill automatically optimizes WordPress site performance without requiring a browser UI. It focuses on backend analysis and remediation, identifying and addressing issues impacting frontend loading times (TTFB), admin panel speed, REST API responsiveness, and WP-Cron execution. The agent will use tools like WP-CLI, logs, and HTTP requests to diagnose and suggest solutions for slow WordPress sites.
When to use it
- When a WordPress site or specific page/endpoint is experiencing slowness.
- To receive profiling plans and tooling recommendations (WP-CLI profile/doctor, Query Monitor, Xdebug/XHProf, APMs).
- For optimizing database queries, autoloaded options, object caching, cron tasks, or remote HTTP calls.
- When you need to diagnose performance issues without direct access to a browser interface.
Key capabilities
- Backend-only Performance Reporting: Generates reports using
perf_inspect.mjsscript. - WP-CLI Diagnostics: Leverages
wp doctor checkfor common WordPress configuration problems. - Profiling with WP-CLI: Utilizes
wp profileto identify performance bottlenecks in different code paths (bootstrap, main query, template, hooks). - Headless Query Monitor Integration: Analyzes Query Monitor data via REST API response headers and envelope responses.
- Targeted Fix Recommendations: Provides guidance for optimizing DB queries, autoloaded options, object caching, and remote HTTP calls based on profiling results.
Example prompts
- "Analyze the performance of my WordPress site at [URL] using WP-CLI."
- "Run a
wp doctor checkon my WordPress installation located at [path]." - "Generate a performance report for the admin dashboard of my WordPress site, accessible at [URL]."
Tips & gotchas
- Requires WP-CLI Access: This skill heavily relies on WP-CLI being available and functional.
- No Browser UI: The agent operates without browser interaction; it uses command-line tools and HTTP requests instead.
- Environment Restrictions: Specify the environment (dev/staging/prod) and any restrictions, such as limitations on write operations or plugin installations.