wordpress/agent-skills
15 skills25.4k installs24.7k starsGitHub
Install
npx skills add https://github.com/wordpress/agent-skillsSkills in this repo
1Wp Plugin Developmentwp-plugin-development is a WordPress-focused agent skill for solo builders and small agencies shipping plugins to the.org ecosystem, client sites, or Woo-adjacent products. It tells your agent when to apply structured procedures for bootstrap architecture, actions and filters, lifecycle hooks, Settings API options pages, cron tasks, and the security trio of nonces, capability checks, and sanitize-or-escape discipline. The workflow starts with deterministic triage scripts so the agent finds the real plugin main file under wp-content/plugins or mu-plugins instead of guessing paths. Targets WordPress 6.9+ and PHP 7.2.24+, including multisite and WP.com convention awareness when you declare context. Use it during Build backend implementation, extend into Ship security when hardening options and SQL, and into Ship launch prep when packaging zips and readme assets for distribution.2.9kinstalls2Wp Rest Apiwp-rest-api is an agent skill for solo builders shipping WordPress plugins, themes, mu-plugins, or headless sites who need reliable REST surfaces without guessing WordPress internals. It walks from triage—detecting project layout and existing register_rest_route, rest_api_init, and show_in_rest usage—through namespace design, controller implementation, permission callbacks, and response shaping including links, embedding, and pagination. Use it when you are exposing custom post types, attaching meta to REST payloads, or chasing authentication failures that block editors or mobile clients. The procedure assumes a filesystem-based agent with bash and Node, and notes when WP-CLI or sub-6.9 WordPress constraints matter. It fits builders who want checklist-driven API work aligned to modern WordPress REST patterns rather than one-off snippets in chat.2.3kinstalls3Wp Block ThemesWP Block Themes is an agent skill for solo builders and small agencies shipping on modern WordPress who live in the Site Editor instead of classic PHP templates. It guides editing theme.json global settings and styles, adding or changing block templates and template parts, registering patterns, and shipping style variations—all while troubleshooting the frustrating cases where styles apply on the frontend but not in the editor, or vice versa. The documented procedure starts with automated triage to find the correct theme root when multiple themes exist, then walks creation, modification, and debugging steps with explicit inputs: repo location, WordPress version range, and where the bug appears. Compatibility is stated for WordPress 6.9+ and PHP 7.2.24+, with node scripts and optional WP-CLI for detection and scaffolding tasks. Use it when you are actively building or fixing a block theme rather than wiring unrelated plugins or infrastructure.2.2kinstalls4Wp PerformanceWP Performance is an agent skill for solo builders and small teams running WordPress in production who need a systematic, CLI-first way to investigate slowness on the frontend, admin, REST endpoints, or cron. It assumes the agent cannot drive a browser and instead favors WP-CLI profile and doctor commands, logs, HTTP requests, and optional Query Monitor signals. You define the install path, environment restrictions, and whether spikes are constant or sporadic before following a procedure that starts with guardrails and reproducible measurement. From there the skill guides optimization of database load, autoloaded options bloat, object caching strategy, scheduled tasks, and outbound HTTP without jumping straight to risky plugin installs or blind cache flushes. It fits operators who already ship WordPress sites and want agent-assisted diagnosis that respects staging boundaries and documents verification steps after each change.2.1kinstalls5Wp Block DevelopmentWP Block Development is an agent skill for solo builders and small teams maintaining WordPress products that rely on the block editor. It walks you from triage—detecting whether you are in a plugin, theme, or full site—through listing every block.json in the repo and editing the right block root. You use it when creating a new block, changing scripts, styles, supports, or attributes, wiring dynamic PHP rendering, or debugging classic editor failures like “block invalid,” missing saves, or attributes that reset on reload. The procedure aligns with modern WordPress APIs (register_block_type from metadata, deprecated versions, viewScriptModule on 6.9+) and the standard @wordpress/scripts and @wordpress/create-block toolchain, including wp-env when you need a local loop. It expects a filesystem agent with bash and Node; some flows optionally use WP-CLI. For Prism’s journey, it is a build-phase frontend integration skill: you install it when the product surface is the block library itself, not when you are only writing marketing copy or running production monitors.2kinstalls6Wordpress RouterWordPress Router is an agent skill for solo builders and small teams who touch WordPress codebases—plugins, classic themes, block themes, Gutenberg blocks, or core checkouts—and need the agent to stop guessing before it edits the wrong layer. It runs a triage script from the repo root, reads project kind and available test tooling, then maps user intent through a decision tree to specialized WordPress workflows such as blocks, theme.json, REST API work, WP-CLI automation, performance, security, testing, or release packaging. You invoke it at the beginning of a task when constraints mention WP versions, WP.com specifics, or release requirements. The skill does not implement features itself; it applies guardrails and delegates so follow-up skills land in the correct domain. That reduces costly mistakes like treating a block theme as a classic PHP theme or skipping PHPUnit when the repo already has it wired.2kinstalls7Wp Project TriageWP Project Triage is an agent skill for solo builders and small teams who inherit a WordPress repository and need a fast, repeatable picture of what they are working in before touching code. You point the agent at the repo root and run the Node detector, which prints a structured JSON report aligned to the bundled triage schema. The report captures project kind, filesystem signals, available PHP and Node tooling, whether tests exist, and version hints so downstream skills and human reviewers can apply the right conventions for plugins, classic themes, block themes, Gutenberg packages, or broader site layouts. It targets WordPress 6.9+ environments and assumes a filesystem agent with bash and Node; some related workflows may still need WP-CLI. Verification is straightforward: parse the JSON, confirm required fields, and re-run after structural changes such as adding `theme.json`, `block.json`, or build config. When signals are missing, the skill tells you to extend the detector rather than improvising, which keeps agent guardrails honest on real client and OSS WordPress work.1.7kinstalls8Wp Wpcli And OpsWP-CLI and Ops is a WordPress agent skill for solo builders and small teams who operate real sites on local, staging, or production environments. It activates when tasks involve WP-CLI rather than clicking wp-admin: URL migrations with search-replace, database export and import, plugin and theme management, cron inspection, rewrite and cache flushing, and multisite commands scoped with path and URL flags. The skill emphasizes guardrails first—know which environment you are hitting, confirm blast radius, and take backups before risky writes—because a wrong --path or prod slip can wipe data. It also bridges into Ship when you are executing a domain or protocol migration under a maintenance window. Builders automating content businesses, client sites, or Woo-style SaaS on WordPress use it to script repeatable ops instead of one-off manual steps. You need WP-CLI available where commands run and clarity on whether the site is multisite. It is not a substitute for application-feature development in PHP themes or plugins; it is the operational playbook around the wp binary.1.7kinstalls9Wp PhpstanWP PHPStan is an agent skill for solo and indie builders shipping WordPress plugins, themes, or site code who want PHPStan to stay useful instead of noisy. It targets WordPress 6.9+ on PHP 7.2.24+ with a Composer-based PHPStan setup. Use it when you are creating or updating `phpstan.neon` or dist variants, refreshing baselines, or fixing errors with WordPress-friendly annotations. The workflow starts with triage output from wp-project-triage, then inspects the repo with a bundled script, aligns with composer scripts when present, and insists on loading WordPress core stubs because most real repos fail without them. It also documents how to handle foreign plugin classes without turning ignores into spaghetti. The skill fits builders who treat static analysis as part of the pre-ship gate, not an optional lint.1.4kinstalls10Wp Abilities Apiwp-abilities-api is a WordPress-focused agent skill for solo builders and small agencies shipping agent-ready sites on 6.9+. It walks through confirming whether Abilities API lives in core or needs the standalone package, locating existing registrations in the repo, and implementing abilities and categories in the right layer—plugin, theme, or mu-plugin. The procedure emphasizes REST exposure under wp-abilities/v1, permission callbacks, and JavaScript consumption via @wordpress/abilities, which matters when Claude or other clients must discover callable capabilities instead of guessing wp-admin flows. Run wp-project-triage first when the repo layout is unknown. The skill is task-specific to WordPress extension work: it does not replace general REST design courses, but it compresses the official registration contract into searchable steps for “ability doesn’t show up” and “client can’t see ability” failures common in indie plugin shops.1.4kinstalls11Wp Playgroundwp-playground is an agent skill that walks solo builders through WordPress Playground workflows: launching fast, disposable WordPress sites in the browser or locally with @wp-playground/cli (server, run-blueprint, build-snapshot). It covers auto-mounting plugins and themes, choosing WP/PHP versions, running blueprints, building snapshots, and debugging with Xdebug. The skill targets WordPress 6.9+ and Node.js 20.18+ for the CLI, using WebAssembly with SQLite under the hood. Use it when you need to validate a plugin or theme, iterate on blueprint JSON, or bisect version-specific bugs without standing up MySQL, Apache, or a staging server. Outputs are procedural commands and checks (Node version, clean mounts, port conflicts) so agents do not paste production secrets into Playground copies.1.4kinstalls12Wp Interactivity ApiWP Interactivity API is an agent skill for solo builders and small teams shipping WordPress 6.9+ blocks, themes, and plugins that use the modern module-based interactivity stack. It walks agents through discovering how interactivity is wired today, choosing the right integration style (block viewScriptModule, theme-level, or plugin-side enhancement), and applying the official interactive block scaffold when starting fresh rather than patching ad hoc scripts. The workflow assumes filesystem access, bash and Node tooling, and often WP-CLI, and it explicitly depends on prior wp-project-triage so the agent knows repo layout and constraints before changing directives or stores. Use it when mentions of data-wp-on, data-wp-bind, data-wp-context, @wordpress/interactivity stores, or hydration issues appear—not for unrelated classic jQuery front ends. The outcome is diagnosable, performant client behavior aligned with WordPress core patterns instead of one-off React islands that fight the block editor pipeline.1.4kinstalls13Wpdswpds is an agent skill that steers UI work toward the WordPress Design System (WPDS): components, design tokens, spacing scales, typography variables, and patterns. It is aimed at solo and indie builders shipping WordPress plugins, themes, WooCommerce experiences, or Gutenberg blocks who want consistent, system-aligned interfaces rather than one-off CSS. The skill assumes a configured WPDS MCP server so the agent pulls canonical reference pages, component lists, per-component specs, and token catalogs via wpds:// resources instead of scraping the open web. Use it when the user mentions WPDS, design tokens, WordPress UI review, or core component packages. Pair it with your normal Build workflow once MCP is running; the main payoff is fewer design drift issues and faster alignment with WordPress’s official UI language before you ship.1.4kinstalls14BlueprintBlueprint is an agent skill for solo WordPress builders, plugin authors, and agency-of-one consultants who need trustworthy, shareable demos without provisioning a full server. WordPress Playground blueprints are JSON documents that declare how a sandbox should boot: which PHP and WordPress versions to use, where to land after setup, which plugins or themes to install, and which scripted steps run next. The skill encodes schema rules so generated files stay valid—documented keys only, required meta fields when present, and feature flags limited to supported networking and intl toggles. Use it when someone asks for a playground link, a contributor reproduction box, or a sales demo that mirrors a specific site configuration. It shines in validation and prototyping phases, but the same artifacts support Build-time documentation and Launch distribution when you embed demos in READMEs or launch posts. Compatibility targets WordPress 6.9+ and PHP 7.2.24+ with optional Playground CLI or browser entry points.969installs15Wp Plugin Directory Guidelineswp-plugin-directory-guidelines is an agent skill that acts as a compliance reviewer for WordPress plugins targeting WordPress.org. Solo builders shipping free or freemium extensions use it when they need to verify GPL licensing, file headers, bundled dependency licenses, naming and trademark rules, and restricted monetization patterns before submission—or when decoding a rejection notice. The skill expects plugin source (and optionally readme and header metadata) and walks a structured procedure from license headers through common violation classes. It is framed for WordPress 6.9+ and PHP 7.2.24+, so checks align with current directory expectations rather than generic PHP linting. For indie developers who cannot afford a manual directory review cycle, running this skill reduces back-and-forth with plugin reviewers and avoids reputation hits from guideline breaches. Pair it with your own security review; this skill focuses on directory policy, not full appsec.615installs