AI Skills

From Bricks v2.4, builder actions can be exposed through the WordPress Abilities API and MCP, letting compatible clients like Claude Code create or edit Bricks pages and global data directly, including BricksExtras settings. Understanding & implementing features takes more than a settings list, and that’s what skills are for.

Required: Bricks v2.4+(in beta) BricksExtras v1.7.3+

What are skills?

Skills document the practical usage details that a settings schema over MCP alone can’t capture. Having this knowledge upfront means less back-and-forth over MCP as the agent already has the information available before the connection is made.

What’s included

Each element or feature has its own skill with information an agent may otherwise only get by trial and error over MCP:

• Required child structure – the agent builds nested elements (slider slides, accordion items, etc.) correctly the first time, instead of guessing a structure that looks right but doesn’t actually work.
• Rendered DOM structure – the agent already knows the real markup an element outputs, so can write custom CSS that targets the right class on the first try, without needing to inspect the live page first.
• Verified working patterns – for common builds (synced sliders, dynamic content from a query loop, multi-step interactions), the agent starts from tested examples instead of assembling one from scratch.
• Known gotchas and silent failure modes – the agent avoids the mistakes that don’t throw an error and look fine in the settings, but quietly don’t work on the actual page.
• Targeting and linking mechanics – when two elements need to talk to each other (a button that opens a slider, a control that syncs two carousels), the agent knows how to wire them up including component scoping if needed.
• Local settings schema – All feature settings & what values can be used is known upfront, without having to keep fetching them live via the abilities.
• “Never do” lists – the agent already knows the handful of actions that reliably break functionality, so it steers clear of them instead of finding out & having to troubleshoot.

Workflow

• Setup the Bricks AI abilities & MCP (AI agent can connect to your site and control Bricks).
• Install the Bricks’ skills package. (AI agent has working knowledge of Bricks core before using abilities).
• Install the BricksExtras’ skills package. (AI agent also has working knowledge of BricksExtras’ elements and features).

Updating

Ask your AI agent: “Check for BricksExtras skills updates“

It’ll compare your installed skills pack against the BricksExtras plugin version running on the site you’re working on, and tell you whether you’re current or behind.

If you’re behind, ask your agent to update: “Update my BricksExtras skills“

Or run it yourself from a terminal:

git -C ~/.bricksextras/skills/bricksextras-skills pull

After updating, start a new chat. Most AI tools load their available skills once, when a session starts – so an update that happens mid-conversation won’t take effect until you start a fresh one.

Note that both skills packages are in beta and shouldn’t be used on live sites.