What other skill should we add?

[Jameswlepage]

Interested in folks' ideas on what other skills would make sense to bring to this WordPress repository.

[juanmaguitar]

Skills to help contributors with tasks related to WordPress DotOrg project. For example triaging issues.

[ben104]

would be great if there were skills around checking the code, so for example when you build a plugin with wp-plugin-development you could then run a wp-plugin-check skill, which would work similarly to the official 'Plugin Check Plugin (PCP)' it could improve code quality, or is this be better in the plugin development skill?

[Xilonz]

I cant think of skills specifically for WordPress core.

I'm not sure if this is in scope (yet):
How do you envision third-party plugin authors extending this? For example, if a plugin author wants to register a custom skill specific to their plugin (like "Clear Cache" or "Working with products").

In my opinion, it would be beneficial to this project to integrate into the WordPress ecosystem.

[flexseth]

I'd love to see individual skills that create, per the documentation, WordPress Core Components.

One of the greatest discrepancies I've seen is the basic aspect of creating a component.

Between Storybook, Devhub, Gutenberg repo (has examples), and the documentation for Core Components, is a lack of consistency. Which makes sense because things change and very few people get paid for writing documentation :D

Having skills that build Core Components the WordPress Way would be 💯

[gcapnias]

In my opinion, the ability to convert plain HTML into WordPress Block Markup is an essential skill.

• When creating themes, part of the work involves transforming CSS-styled HTML into WordPress Block Markup for pattern creation.
• Since there’s no official documentation on WordPress Block Markup, developers often need to search the block registry to find block names before they can use them.

[juanmaguitar]

Skills to help contributors with tasks related to WordPress DotOrg project. For example triaging issues.

Pinging @sirreal as he has developed some interesting WP-related AI tools: https://github.com/sirreal/agent-skills

[sirreal]

I've been working on a WordPres Trac Claude plugin. I has skills for getting information from Trac tickets and changesets as well as for searching Trac or exploring the timeline.

I'd love to get an MCP plugin on Trac that could make the whole plugin redundant.

[owlot]

I came here through Automattic/agent-skills#10
Would love to see an wp-env skill

[yfxlabs]

wp-martech-integration - Patterns for properly integrating third-party SDKs into WordPress. Correct enqueueing, consent management hooks, data layer setup, async loading. AI assistants routinely generate integration code that ignores WordPress conventions and breaks in production when caching and consent tools are in play.

wp-b2b-patterns - B2B sites have specific content and conversion patterns (progressive profiling forms, gated content, structured data for service pages) that AI assistants miss because they default to blog or ecommerce assumptions.

Supporting @gcapnias on HTML-to-block-markup conversion.

[Xilonz]

For block development is would be nice to have a skills that understands usesContext and what context to use when, which is crucial for the block to be template or post-id aware (if in a query loop for example). There is currently 0 documentation for the available context's in WordPress core, so a skill would help tremendously.

[dknauss]

I've opened a PR with two skills for Studio — one for general development use that handles some common conflicts with other tools, and another dedicated to Xdebug. If your experience is like mine, you might find Claude complaining about Studio and saying you can't do things like set up Xdebug — these skills are the fix, developed with Claude after feeding it the relevant docs and pushing it along.

I'd also love to have some official WP agents and skills for aligning technical documentation with the current state of core code and docs. This is my attempt at that: https://github.com/dknauss/ai-assisted-docs — please use it if it's useful or leave me feedback for improvements.

[westonruter]

A skill for core committers would be very helpful. It's something I want to work on when I have a chance. It should help ensure proper formatting of an SVN commit message, putting together the the props list, finding the Follow-up ticket references, any related See tickets, and so on.

[dknauss]

Ooh, yes — seconding @westonruter's suggestion. It would be a great teaching tool — not something to mechanically adopt and bury, but also make a point of having learners read through it and reflect on it.

[sirreal]

A skill for core committers would be very helpful.

@westonruter I've been using some skills for exactly the things you describe. It automates that data gathering and writing the commit message, but it's made the routine work much faster and easier for me. It could be a good starting point, although several things are designed to work together:

• /wp-commit skill is the instructions to produce a commit message
• A WP Trac plugin provides tools the commit skill relies on.

If they're a good fit and folks are interested, things could certainly be moved here.