wp-performance
Audited by Runlayer on Feb 22, 2026
Malicious tool definition detected
Tool: SKILL.md Description: --- 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 6.9+ (PHP 7.2.24+).
Malicious tool definition detected
Tool: references/autoload-options.md Description: # Autoloaded options Autoloaded options are loaded on *every request*, so large autoload payloads can hurt performance site-wide.
Malicious tool definition detected
Tool: references/cron.md Description: # WP-Cron performance Use this file when cron causes spikes or request-time slowness.
Malicious tool definition detected
Tool: references/database.md Description: # Database / query performance Use this file when profiling points to DB time or high query counts.
Malicious tool definition detected
Tool: references/http-api.md Description: # HTTP API (remote requests) Use this file when profiling shows slow external requests (`wp_remote_get`, etc.).
Malicious tool definition detected
Tool: references/measurement.md Description: # Measurement (profiling vs benchmarking) Backend-only measurement options: - **WP-CLI profiling** (`wp profile`): best for pinpointing slow hooks/stages without a browser.
Malicious tool definition detected
Tool: references/object-cache.md Description: # Object caching Use this file when profiling indicates repeated queries or low cache hit rate.
Malicious tool definition detected
Tool: references/query-monitor-headless.md Description: # Query Monitor (headless / backend-only) Query Monitor is UI-first, but it can expose useful data to backend-only tooling.
Malicious tool definition detected
Tool: references/server-timing.md Description: # Server-Timing (Performance Lab) Use this file when you can enable Server-Timing metrics and want backend-only inspection via HTTP headers.
Malicious tool definition detected
Tool: references/wp-cli-doctor.md Description: # WP-CLI doctor (`wp doctor`) Use this for quick “production readiness” checks.
Malicious tool definition detected
Tool: references/wp-cli-profile.md Description: # WP-CLI profiling (`wp profile`) Use this when you need actionable profiling without a browser.
Malicious tool definition detected
Tool: scripts/perf_inspect.mjs Description: import fs from "node:fs"; import path from "node:path"; import { spawnSync } from "node:child_process"; const TOOL_VERSION = "0.1.0"; function parseArgs(argv) { const args = { path: null, url: null, allowRoot: false }; for (const a of argv) { if (a === "--allow-root") args.allowRoot = true; if (a.startsWith("--path=")) args.path = a.slice("--path=".length); if (a.startsWith("--url=")) args.url = a.slice("--url=".length); } return args; } function exist