←Leaderboard/Software Engineering/agent-skills
Last commit on October 12, 2026·Created on January 20, 2026

WordPress/agent-skills

“A technical guide for constructing and validating WordPress Playground Blueprint configurations.”
Combined rank
#209
across all skills
In Software Engineering
#14
category rank
Stars
2.3k
+1.7% in last 7d
Forks
333
+0.9% in last 7d
Watchers
44
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This skill assists developers in creating, editing, and debugging WordPress Playground Blueprint JSON files and bundles. It provides a structured approach to selecting resources and validating schema keys to ensure environment configurations are accurate.

WHO IT'S FOR
WordPress theme developers
building block themes and configuring theme.json
WordPress plugin developers
implementing custom permissions via the Abilities API
WordPress platform engineers
creating and validating Playground Blueprint JSON files
Technical leads / architects
routing WordPress codebase tasks to specialized workflows
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

See the repository for installation instructions.

Open repository instructions ↗

Give it something to do.

Suggested first task

Understand a WordPress repository

Uses wp-project-triage

  • Open the target WordPress repository as the current working directory.
  • Provide filesystem access, bash, and Node.js.

Make sure wp-project-triage is installed in your agent before trying this task.

Use wp-project-triage to inspect the current repository root. Return the structured JSON report and briefly summarize the project kind, available PHP/Node tooling, tests, and version hints. Do not change files; identify missing signals rather than guessing.
README.md ↗ · Checked Oct 18, 2026skills/wp-project-triage/SKILL.md ↗ · Checked Oct 18, 2026
Suggested first task

Review one plugin settings handler

Uses wp-plugin-development

  • Repository root and target plugin main-file path.
  • The settings-save handler or settings page to review.
  • Single-site or multisite context, applicable WP.com conventions, and target WordPress/PHP versions.
  • Filesystem access, bash, and Node.js.

Make sure wp-plugin-development is installed in your agent before trying this task.

Use wp-plugin-development to review one settings-save handler in the plugin I identify. Check nonce protection, capability checks, input sanitization, and output escaping. Report the highest-priority findings with file references and suggested fixes, without changing files.
README.md ↗ · Checked Oct 18, 2026skills/wp-plugin-development/SKILL.md ↗ · Checked Oct 18, 2026
Suggested first task

Diagnose a block-theme style mismatch

Uses wp-block-themes

  • Repository root and target theme directory.
  • Target WordPress version range.
  • The specific style and expected appearance.
  • Where the mismatch occurs: Site Editor, post editor, frontend, or all.
  • Filesystem access, bash, and Node.js.

Make sure wp-block-themes is installed in your agent before trying this task.

Use wp-block-themes to investigate one theme.json style that is not appearing where expected. Confirm the target theme root, inspect the relevant settings or styles, and consider the core/theme/child-theme/user-customization hierarchy. Give a short diagnosis and the next checks to perform without changing files or stored customizations.
README.md ↗ · Checked Oct 18, 2026skills/wp-block-themes/SKILL.md ↗ · Checked Oct 18, 2026