Name: wp-performance
Rating: 61.6 (1 reviews)
Author: WordPress

wp-performance

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.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/wp-performance/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is a well-structured, actionable backend-only WordPress performance workflow with concrete WP-CLI commands, a guardrails-first sequence, and a verify step backed by reference files. Main weaknesses are a version-specific 6.9 narrative that pads the body and an orphaned reference file.

Suggestions

Move the 'WordPress 6.9 performance improvements' section into a versioned reference file (e.g. references/version-notes.md) or a clearly marked 'old/version notes' section, and reconcile the 7.0+ vs 6.9 version mismatch in the frontmatter.

Reference references/server-timing.md from the relevant procedure step (e.g. measurement or deep profiling) so it is discoverable, or remove it if unused.

Tighten high-level hints like 'Authenticate (nonce or Application Password)' and 'add timeouts, caching, batching' with a one-line concrete example inline before deferring to the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullets and commands, but the 'WordPress 6.9 performance improvements' section is version-specific narrative not placed in a deprecated/old-patterns section, and it conflicts with the frontmatter's 'WordPress 7.0+' target, which the conciseness guideline penalizes.	3 / 5
Actionability	Concrete copy-pasteable commands appear throughout (wp profile stage/hook/eval, wp doctor check, the perf_inspect.mjs script), with a few high-level hints like 'Authenticate' or 'add timeouts, caching, batching' deferring specifics to the reference files.	4 / 5
Workflow Clarity	A clear 0-6 sequence with guardrails, baseline capture, a Verify step, a Verification checklist, and a Failure-modes section; the verify-to-retry feedback loop lives in a separate debugging section rather than being an explicit inline checkpoint.	4 / 5
Progressive Disclosure	The body is an overview pointing to nine real one-level-deep reference files clearly signaled with 'Read: references/...', but references/server-timing.md is an orphan never linked from the body, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

76%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly answers both what the skill does and when to use it, with an explicit 'Use when' clause and a concrete capability list. It is slightly weakened by thin natural-language trigger variation and a generic umbrella verb.

Suggestions

Add natural user-facing trigger phrases such as 'slow WordPress site', 'speed up WP', or 'high TTFB' so the description matches how users actually phrase the need.

Lead with a crisp action verb (e.g. 'Profiles and optimizes WordPress backend performance') instead of the generic 'investigating or improving'.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capability areas (profiling/measurement, DB/query optimization, autoloaded options, object caching, cron, HTTP API, safe verification), but they read as sub-domains under the generic umbrella 'investigating or improving', so coverage is strong yet not crisply action-verb framed.	4 / 5
Completeness	It has an explicit 'Use when investigating or improving WordPress performance...' trigger clause and a concrete list of what the skill does, matching the anchor that clearly answers both what and when.	5 / 5
Trigger Term Quality	The natural trigger is essentially 'WordPress performance'; common user variations like 'slow site', 'speed up', 'optimize', or the 'WP' abbreviation are missing, and the remaining terms (autoloaded options, object caching, cron) are technical jargon users rarely say.	3 / 5
Distinctiveness Conflict Risk	The 'backend-only agent' qualifier plus specific WP-CLI/Server-Timing/Query-Monitor tooling carves a clear niche, but there is minor overlap risk with a broader WordPress admin or general performance skill.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: WordPress/agent-skills
Path: skills/wp-performance/SKILL.md
Commit: d87ee69

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.