We welcome contributions! This project is a great opportunity to share your WordPress expertise with the community in a unique way.
You don't need to be a coding wizard. Unlike typical open source projects, Agent Skills is primarily about capturing knowledge and best practices in a structured format. If you understand WordPress deeply—whether that's block development, performance optimization, plugin security, or any other domain—you can make a meaningful contribution.
Most of our skills are written in Markdown. The "code" is mostly procedural checklists, decision trees, and reference documentation. If you can explain a WordPress concept clearly, you can contribute here.
The easiest way to start:
- Fix outdated information — WordPress evolves quickly. If you spot something that's changed, open a PR.
- Add missing edge cases — Did you hit a gotcha that isn't documented? Add it to the "Failure modes" section.
- Clarify procedures — If a step confused you, it'll confuse others. Make it clearer.
- Expand references — Add deeper documentation on specific topics.
Have expertise in a WordPress area we don't cover yet? Consider adding a new skill.
Before starting:
- Check existing skills to avoid overlap
- Review the Authoring Guide for structure requirements
- Open an issue to discuss scope (optional but recommended for larger skills)
Scaffold a new skill:
node shared/scripts/scaffold-skill.mjs <skill-name> "<description>"Every skill needs test scenarios under eval/scenarios/. These are simple markdown files describing:
- A realistic prompt/task
- What the AI should do
- How to verify it worked
This is a great low-barrier contribution—you're essentially writing "what should happen when someone asks X?"
Found a skill giving bad advice? AI following a procedure that doesn't work? Open an issue with:
- Which skill
- What went wrong
- What the correct behavior should be
Each skill follows this structure:
skills/<skill-name>/
├── SKILL.md # Main instructions (short, procedural)
├── references/ # Deep-dive docs on specific topics
│ └── *.md
└── scripts/ # Deterministic helpers (optional)
└── *.mjs
Every SKILL.md needs:
- YAML frontmatter with
name,description, andcompatibility - When to use — Conditions that trigger this skill
- Inputs required — What the AI needs to gather first
- Procedure — Step-by-step checklist
- Verification — How to confirm it worked
- Failure modes / debugging — Common problems and fixes
- Escalation — When to ask for human help
See any existing skill for examples.
- Focus on what developers actually need to do
- Include concrete examples, not abstract theory
- Link to official docs for deep dives
- Target WordPress 6.9+ and PHP 7.2.24+
- Avoid legacy patterns (Classic themes, pre-Gutenberg APIs)
- Update compatibility frontmatter when requirements change
- Add at least one eval scenario for new skills
- Run
node eval/harness/run.mjsbefore submitting
- Prefer small, focused skills over mega-skills
- Keep
SKILL.mdshort—push depth intoreferences/ - One skill should do one thing well
- Fork the repo
- Create a branch (
git checkout -b improve-block-dev-skill) - Make your changes
- Run validation:
node eval/harness/run.mjs - Commit with a clear message
- Open a pull request
For significant changes, consider opening an issue first to discuss the approach.
Open an issue or start a discussion. We're happy to help you get started.
Your WordPress knowledge can help thousands of developers get better AI assistance. Thank you for contributing!