Utilisez cette compétence lorsque vous travaillez avec WP-CLI (wp) pour les opérations WordPress : recherche-remplacement sécurisée, exportation/importation de base de données, gestion des plugins/thèmes/utilisateurs/contenu, cron, vidage du cache, multisite et scripts/automatisation avec wp-cli.yml.
Cette compétence est conçue pour les développeurs et les administrateurs système qui utilisent WP-CLI pour gérer des sites WordPress de manière efficace et automatisée. Elle prend en charge une large gamme d'opérations essentielles, notamment le remplacement sécurisé de chaînes de caractères dans la base de données (search-replace), l'exportation et l'importation de bases de données, ainsi que la gestion complète des plugins, thèmes, utilisateurs et contenus. De plus, elle facilite la gestion des tâches cron, le vidage du cache, et la configuration de réseaux multisite. La compétence met également l'accent sur l'automatisation et les scripts grâce à l'utilisation de fichiers de configuration wp-cli.yml, permettant de définir des paramètres et des commandes réutilisables pour des flux de travail reproductibles. Elle est compatible avec les agents AI comme Claude Code, Cursor, et Codex, et s'intègre facilement dans des pipelines DevOps ou des scripts shell. En résumé, cette compétence est un outil puissant pour tout professionnel cherchant à optimiser et automatiser la gestion de sites WordPress via la ligne de commande.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-wpcli-and-opsInstalled? Explore more Rédaction et édition skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →
Utilisez cette compétence lorsque vous travaillez avec WP-CLI (wp) pour les opérations WordPress : recherche-remplacement sécurisée, exportation/importation de base de données, gestion des plugins/thèmes/utilisateurs/contenu, cron, vidage du cache, multisite et scripts/automatisation avec wp-cli.yml.
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 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.
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.
Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.
The agent engineering platform.
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors