Use ao investigar ou melhorar o desempenho do WordPress (agente apenas de backend): criação de perfil e medição (WP-CLI profile/doctor, Server-Timing, Query Monitor via cabeçalhos REST), otimização de banco de dados/consultas, opções carregadas automaticamente, cache de objetos, cron, chamadas à API HTTP e verificação segura.
Esta skill especializada permite que agentes de IA (como Claude Code, Cursor ou Codex) atuem como especialistas em desempenho de sites WordPress, exclusivamente no backend. Ela fornece ferramentas e orientações para diagnosticar e solucionar gargalos de performance comuns, como consultas lentas ao banco de dados, opções 'autoload' excessivas, configurações inadequadas de cache de objetos (Redis/Memcached), cron jobs mal otimizados e chamadas HTTP externas lentas. A skill integra-se perfeitamente com o ecossistema nativo do WordPress, utilizando WP-CLI (comandos 'profile' e 'doctor'), cabeçalhos Server-Timing de servidores modernos (Nginx, Apache) e, em ambientes com Query Monitor presente, seus cabeçalhos REST para medição precisa. O workflow recomendado é sempre iniciar com a coleta de métricas via WP-CLI 'profile stage' para análise de hooks lentos e, em seguida, usar 'doctor' para verificar a integridade da instalação, antes de prosseguir com otimizações específicas. A skill enfatiza uma abordagem segura e baseada em evidências, evitando alterações sem verificação prévia.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-performanceInstalled? Explore more Produtividade e Colaboração skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
Use ao investigar ou melhorar o desempenho do WordPress (agente apenas de backend): criação de perfil e medição (WP-CLI profile/doctor, Server-Timing, Query Monitor via cabeçalhos REST), otimização de banco de dados/consultas, opções carregadas automaticamente, cache de objetos, cron, chamadas à API HTTP e verificação segura.
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.