wp-performance 是做什么的？
用于调查和优化 WordPress 性能（仅限后端代理）：性能分析与测量（WP-CLI profile/doctor、Server-Timing、通过 REST 头部的 Query Monitor）、数据库/查询优化、自动加载选项、对象缓存、定时任务、HTTP API 调用及安全验证。
用于调查和优化 WordPress 性能（仅限后端代理）：性能分析与测量（WP-CLI profile/doctor、Server-Timing、通过 REST 头部的 Query Monitor）、数据库/查询优化、自动加载选项、对象缓存、定时任务、HTTP API 调用及安全验证。
该技能专为后端代理（如 AI 助手）设计，用于诊断和优化 WordPress 网站的性能问题。它支持多种分析工具，包括 WP-CLI 的 profile 和 doctor 命令、Server-Timing 头以及通过 REST API 头获取的 Query Monitor 数据。技能涵盖数据库查询优化、自动加载选项管理、对象缓存配置、WordPress 定时任务（cron）分析和 HTTP API 调用调优。此外，它强调安全验证，确保所有性能改进建议都经过验证和测试。适用于需要深度排查 WordPress 性能瓶颈、优化 Core Web Vitals 或降低服务器负载的开发者。
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-performanceInstalled? Explore more 生产力与协作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
用于调查和优化 WordPress 性能（仅限后端代理）：性能分析与测量（WP-CLI profile/doctor、Server-Timing、通过 REST 头部的 Query Monitor）、数据库/查询优化、自动加载选项、对象缓存、定时任务、HTTP API 调用及安全验证。
This repo contains 13 individual skills — each has its own dedicated page.
Use when creating, editing, or reviewing WordPress Playground blueprint JSON files. Triggers on mentions of blueprints, playground configuration, or requests to set up a WordPress demo environment.
Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
Use 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 structured JSON report to guide workflows and guardrails.
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.