WordPress Pro
Jeffallan/claude-skills
Develops WordPress themes, plugins, Gutenberg blocks and WooCommerce features with nonce, escaping and capability checks, phpcs linting and caching tuned for speed.
A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…
Install Wp Performance
$ npx skills add gambitph/Stackable --skill wp-performance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gambitph/Stackable wp-performance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/wp-performance .claude/skills/wp-performance && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wp-performance" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-performance into .claude/skills/wp-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-performance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-performanceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gambitph/Stackable --skill wp-performance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gambitph/Stackable wp-performance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/wp-performance .agents/skills/wp-performance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wp-performance" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-performance into .agents/skills/wp-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-performance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gambitph/Stackable --skill wp-performance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gambitph/Stackable wp-performance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/wp-performance .cursor/skills/wp-performance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wp-performance" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-performance into .cursor/skills/wp-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-performance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gambitph/Stackable.git --path .cursor/skills/wp-performance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gambitph/Stackable --skill wp-performance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gambitph/Stackable wp-performance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/wp-performance .gemini/skills/wp-performance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wp-performance" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-performance into .gemini/skills/wp-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-performance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gambitph/Stackable wp-performanceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gambitph/Stackable --skill wp-performance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/wp-performance .github/skills/wp-performance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wp-performance" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-performance into .github/skills/wp-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-performance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gambitph/Stackable --skill wp-performance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gambitph/Stackable wp-performance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/wp-performance .opencode/skills/wp-performance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wp-performance" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-performance into .opencode/skills/wp-performance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-performance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wp-performance- GitHub stars
- 350
- Used in
- 3 other repos
- Token cost
- ~1.5k tokens
- SKILL.md length
- 674 words
- Files
- 12 (incl. scripts, references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…
- Works in 7 steps: Guardrails: measure first, avoid risky ops → Generate a backend-only performance… → Fast wins: run diagnostics before deep… → …
- Improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor
- SKILL.md covers When to use, Inputs required, Procedure and WordPress 6.9 performance…, plus 3 more sections
- Runs JavaScript scripts from its folder; calls node
What it does
Wp Performance is an agent skill from gambitph/Stackable. Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `references/autoload-options.md`, `references/cron.md` and `references/database.md`). Compatibility notes: Targets WordPress 7.0+ (PHP 7.4.0+). Backend-only agent; prefers WP-CLI (doctor/profile) when available.
It sits in Backend & APIs, covering Scheduled and recurring tasks, REST APIs and Query optimization. It works with WordPress. The repository describes itself as: Page Builder Blocks for WordPress. An Amazing Block Library for the new WordPress Block Editor (Gutenberg). The licence is GPL-3.0.
When your agent uses it
- Improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor
- Query Monitor via REST headers)
- Database/query optimization
- Autoloaded options
Example prompts
- “/wp-performance”
Requirements
- Node.js
- Compatibility (from SKILL.md): Targets WordPress 7.0+ (PHP 7.4.0+). Backend-only agent; prefers WP-CLI (doctor/profile) when available.
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Guardrails: measure first, avoid risky ops
- Generate a backend-only performance report (deterministic)
- Fast wins: run diagnostics before deep profiling
- Deep profiling (no browser required)
- Query Monitor (backend-only usage)
- Fix by category (choose the dominant bottleneck)
- Verify (repeat the same measurement)
What it can do on your machine
Read from SKILL.md and the folder at commit 5c13d80. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
make.wordpress.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Targets WordPress 7.0+ (PHP 7.4.0+). Backend-only agent; prefers WP-CLI (doctor/profile) when available.
From compatibility in the SKILL.md frontmatter.
Context cost
Wp Performance loads about 1.5k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 674 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from gambitph/Stackable at commit 5c13d80, republished under its GPL-3.0 licence (© gambitph). 674 words, ~1,457 tokens.
Download SKILL.mdSave it as
.claude/skills/wp-performance/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- wp-performance
- description
- Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
- compatibility
- Targets WordPress 7.0+ (PHP 7.4.0+). Backend-only agent; prefers WP-CLI (doctor/profile) when available.
WP Performance (backend-only)
When to use
Use this skill when:
- a WordPress site/page/endpoint is slow (frontend TTFB, admin, REST, WP-Cron)
- you need a profiling plan and tooling recommendations (WP-CLI profile/doctor, Query Monitor, Xdebug/XHProf, APMs)
- you’re optimizing DB queries, autoloaded options, object caching, cron tasks, or remote HTTP calls
This skill assumes the agent cannot use a browser UI. Prefer WP-CLI, logs, and HTTP requests.
Inputs required
- Environment and safety: dev/staging/prod, any restrictions (no writes, no plugin installs).
- How to target the install:
- WP root
--path=<path> - (multisite/site targeting)
--url=<url>
- WP root
- The performance symptom and scope:
- which URL/REST route/admin screen
- when it happens (always vs sporadic; logged-in vs logged-out)
Procedure
0) Guardrails: measure first, avoid risky ops
- Confirm whether you may run write operations (plugin installs, config changes, cache flush).
- Pick a reproducible target (URL or REST route) and capture a baseline:
- TTFB/time with
curlif possible - WP-CLI profiling if available
- TTFB/time with
Read:
references/measurement.md
1) Generate a backend-only performance report (deterministic)
Run:
node skills/wp-performance/scripts/perf_inspect.mjs --path=<path> [--url=<url>]
This detects:
- WP-CLI availability and core version
- whether
wp doctor/wp profileare available - autoloaded options size (if possible)
- object-cache drop-in presence
2) Fast wins: run diagnostics before deep profiling
If you have WP-CLI access, prefer:
wp doctor check
It catches common production foot-guns (autoload bloat, SAVEQUERIES/WP_DEBUG, plugin counts, updates).
Read:
references/wp-cli-doctor.md
3) Deep profiling (no browser required)
Preferred order:
wp profile stageto see where time goes (bootstrap/main_query/template).wp profile hook(optionally with--url=) to find slow hooks/callbacks.wp profile evalfor targeted code paths.
Read:
references/wp-cli-profile.md
4) Query Monitor (backend-only usage)
Query Monitor is normally UI-driven, but it can be used headlessly via REST API response headers and _envelope responses:
- Authenticate (nonce or Application Password).
- Request REST responses and inspect headers (
x-qm-*) and/or theqmproperty when using?_envelope.
Read:
references/query-monitor-headless.md
5) Fix by category (choose the dominant bottleneck)
Use the profile output to pick one primary bottleneck category:
- DB queries → reduce query count, fix N+1 patterns, improve indexes, avoid expensive meta queries.
references/database.md
- Autoloaded options → identify the biggest autoloaded options and stop autoloading large blobs.
references/autoload-options.md
- Object cache misses → introduce caching or fix cache key/group usage; add persistent object cache where appropriate.
references/object-cache.md
- Remote HTTP calls → add timeouts, caching, batching; avoid calling remote APIs on every request.
references/http-api.md
- Cron → reduce due-now spikes, de-duplicate events, move heavy tasks out of request paths.
references/cron.md
Show full SKILL.md (282 more words)Show less
6) Verify (repeat the same measurement)
- Re-run the same
wp profile/wp doctor/ REST request. - Confirm the performance delta and that behavior is unchanged.
- If the fix is risky, ship behind a feature flag or staged rollout when possible.
WordPress 6.9 performance improvements
Be aware of these 6.9 changes when profiling:
On-demand CSS for classic themes:
- Classic themes now get on-demand CSS loading (previously only block themes had this).
- Reduces CSS payload by 30-65% by only loading styles for blocks actually used on the page.
- If you're profiling a classic theme, this should already be helping.
Block themes with no render-blocking resources:
- Block themes that don't define custom stylesheets (like Twenty Twenty-Three/Four) can now load with zero render-blocking CSS.
- Styles come from global styles (theme.json) and separate block styles, all inlined.
- This significantly improves LCP (Largest Contentful Paint).
Inline CSS limit increased:
- The threshold for inlining small stylesheets has been raised, reducing render-blocking resources.
Reference: https://make.wordpress.org/core/2025/11/18/wordpress-6-9-frontend-performance-field-guide/
Verification
- Baseline vs after numbers are captured (same environment, same URL/route).
wp doctor checkis clean (or improved) when applicable.- No new PHP errors or warnings in logs.
- No cache flush is required for correctness (cache flush should be last resort).
Failure modes / debugging
- “No change” after code changes:
- you measured a different URL/site (
--urlmismatch), caches masked results, or opcode cache is stale
- you measured a different URL/site (
- Profiling data is noisy:
- eliminate background tasks, test with warmed caches, run multiple samples
SAVEQUERIES/Query Monitor causes overhead:- don’t run in production unless explicitly approved
Escalation
- If this is production and you don’t have explicit approval, do not:
- install plugins, enable
SAVEQUERIES, run load tests, or flush caches during traffic
- install plugins, enable
- If you need system-level profiling (APM, PHP profiler extensions), coordinate with ops/hosting.
© gambitph, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files (scripts, references) in .cursor/skills/wp-performance of gambitph/Stackable.
- SKILL.md
- references/autoload-options.md
- references/cron.md
- references/database.md
- references/http-api.md
- references/measurement.md
- references/object-cache.md
- references/query-monitor-headless.md
- references/server-timing.md
- references/wp-cli-doctor.md
- references/wp-cli-profile.md
- scripts/perf_inspect.mjs
Open the folder on GitHubat commit 5c13d80
Used in 3 other repositories
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in gambitph/Stackable, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Wp Performance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wp Performance this skillgambitph/Stackable | 350 | 3 repos | ~1.5k | Automated safety check: Pass | GPL-3.0 | |
| WordPress ProJeffallan/claude-skills | 12k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 235 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| WordPress Code GuardamElnagdy/guard-skills | 1.3k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Frappe App Devfrappe/skills | 146 | — | ~943 | Automated safety check: Pass | None | |
| Workspace APIfriday-platform/friday-studio | 104 | — | ~9.3k | Automated safety check: Notes | Custom licence |
Similar skills
Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
WordPress Code Guard
amElnagdy/guard-skills
Reviews WordPress plugin, theme and block code after an agent writes or edits it, catching missing escaping, nonces, capability checks and unprepared queries.
Frappe App Dev
frappe/skills
Builds full-stack Frappe Framework applications end-to-end. An agent skill from frappe/skills.
Workspace API
friday-platform/friday-studio
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.
Sap Btp Job Scheduling
secondsky/sap-skills
This skill provides comprehensive guidance for SAP BTP Job Scheduling Service development, configuration, and operations.
More from gambitph/Stackable
All 18 skills in this repoWp Block Development
gambitph/Stackable
A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…
Wp Block Themes
gambitph/Stackable
A skill your agent uses when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style…
Wp Plugin Development
gambitph/Stackable
A skill your agent uses when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security…
Wp Project Triage
gambitph/Stackable
A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…
Wp Plugin Directory Guidelines
gambitph/Stackable
A skill your agent uses when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or…
Wp Abilities API
gambitph/Stackable
A skill your agent uses when working with the WordPress Abilities API (wpregisterability, wpregisterabilitycategory, /wp-json/wp-abilities/v1/, @wordpress/abilities) including defining abilities…
Related
Works with
Questions about Wp Performance
What does Wp Performance do?
A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…. Wp Performance is an agent skill from gambitph/Stackable. Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
When should I use Wp Performance?
Wp Performance fits situations like: improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor; query Monitor via REST headers); database/query optimization; autoloaded options.
How do I install Wp Performance in Claude Code?
Run `npx skills add gambitph/Stackable --skill wp-performance -a claude-code`. Or copy the skill folder (.cursor/skills/wp-performance in gambitph/Stackable) into .claude/skills/wp-performance in your project. Claude Code loads it when a task matches its description.
How do I install Wp Performance in Codex?
Run `npx skills add gambitph/Stackable --skill wp-performance -a codex`. Or copy the skill folder (.cursor/skills/wp-performance in gambitph/Stackable) into .agents/skills/wp-performance in your project. Codex loads it when a task matches its description.
Can I use Wp Performance in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gambitph/Stackable --skill wp-performance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wp-performance, .gemini/skills/wp-performance, .github/skills/wp-performance and .opencode/skills/wp-performance in your project.
What does Wp Performance need to run?
Going by SKILL.md and its folder, Wp Performance needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js. Compatibility (from SKILL.md): Targets WordPress 7.0+ (PHP 7.4.0+). Backend-only agent; prefers WP-CLI (doctor/profile) when available..
Does Wp Performance access the network?
SKILL.md names 1 domain. As links in the text: make.wordpress.org. This is read from the text; nothing was executed.
Is Wp Performance safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Wp Performance use?
Wp Performance is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wp Performance use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Wp Performance?
Skills that share tags, products or a category with Wp Performance: WordPress Pro (Jeffallan/claude-skills, 12k stars), Wp Performance Review (elvismdev/claude-wordpress-skills, 235 stars), WordPress Code Guard (amElnagdy/guard-skills, 1.3k stars) and Frappe App Dev (frappe/skills, 146 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wp Performance?
gambitph (a GitHub organization) maintains it in gambitph/Stackable, which has 350 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.
Source: gambitph/Stackable on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.