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 호출 및 안전한 검증을 다룹니다.
이 스킬은 WordPress 사이트의 성능을 종합적으로 분석하고 개선하기 위한 백엔드 전용 AI 에이전트 도구입니다. WP-CLI의 profile, doctor 명령어, Server-Timing 헤더, 그리고 REST API를 통한 Query Monitor 데이터를 활용하여 병목 지점을 식별합니다. 데이터베이스 쿼리 최적화, 자동 로드된 옵션(autoloaded options) 정리, 객체 캐싱(Object Caching) 도입, 크론(Cron) 작업 관리, 외부 HTTP API 호출 최적화 등 다양한 성능 개선 작업을 안전하게 수행합니다. 또한, 변경 사항 적용 전후의 성능을 비교하여 검증하는 프로세스를 포함하여 실제 운영 환경에서도 안심하고 사용할 수 있도록 설계되었습니다.
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.