From Respira WordPress Skills Library
Audits every Beaver Builder page, maps modules to Bricks equivalents, builds an approval migration plan, and converts pages to Bricks JSON via duplicates without touching the live site.
How this skill is triggered — by the user, by Claude, or both
Slash command
/respira-wordpress-skills:migrate-beaver-builder-to-bricksThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Full-site migration from Beaver Builder to Bricks Builder. Audits every Beaver Builder page, maps modules to their Bricks equivalents, builds a migration plan for approval, and executes page-by-page conversion into Bricks' JSON format — all through duplicates so your live site stays untouched. Use this skill whenever someone mentions migrating from Beaver Builder to Bricks, switching from BB to...
Full-site migration from Beaver Builder to Bricks Builder. Audits every Beaver Builder page, maps modules to their Bricks equivalents, builds a migration plan for approval, and executes page-by-page conversion into Bricks' JSON format — all through duplicates so your live site stays untouched. Use this skill whenever someone mentions migrating from Beaver Builder to Bricks, switching from BB to Bricks, converting Beaver Builder pages to Bricks, or replacing Beaver Builder with Bricks.
Beaver Builder and Bricks are both visual page builders, but they differ significantly in architecture. Beaver Builder uses a module-based system with rows, columns, and modules stored in _fl_builder_data. Bricks uses a more modern, flexbox-first approach with sections, containers, and elements stored as a JSON array in _bricks_page_content_2. The migration requires translating BB's row/column grid into Bricks' container model and mapping each module to its Bricks element equivalent.
This skill reads every Beaver Builder page, extracts the module structure, translates each row/column/module to its Bricks equivalent, and writes the result to duplicate pages in Bricks format — giving you a complete parallel version of your site to review before going live.
Handles:
Source: Beaver Builder
_fl_builder_data and _fl_builder_data_settingswordpress_extract_builder_content with builder=beaver or builder=beaver-builderrich-text, photo, button, heading, html, video, icon, separator, callout, cta, numbers, content-slider, etc.Target: Bricks Builder
_bricks_page_content_2 as a JSON arrayid, name, parent, settings, childrenwordpress_inject_builder_content with builder=brickssection, container, heading, text, image, button, video, code, divider, icon, etc.wordpress_get_site_context. If unavailable, stop and show setup guidance.wordpress_get_builder_info or wordpress_list_plugins.wordpress_list_pages and wordpress_list_posts — identify all contentwordpress_find_builder_targets with builder=beaver — find BB-managed pageswordpress_extract_builder_content with builder=beaverPresent a structured migration plan:
## Beaver Builder → Bricks Migration Plan
### Site Overview
- Total Beaver Builder pages: X
- Simple pages (direct mapping): X
- Moderate pages (some manual review needed): X
- Complex pages (significant manual work): X
### Module-to-Element Mapping
| BB Module | Bricks Element | Notes |
|---|---|---|
| Row | Section | BB row maps to Bricks section |
| Column | Container | Flex-based layout in Bricks |
| Text Editor | Text / Heading | Content parsed into elements |
| Photo | Image | Direct mapping |
| Button | Button | Direct mapping |
| ... | ... | ... |
### Migration Order
1. [Page Title] — Simple — estimated 2 min
2. [Page Title] — Moderate — estimated 5 min
...
### Items Requiring Manual Attention
- [Page X] — PowerPack Tabs module (no direct Bricks equivalent)
- [Page Y] — Content slider (needs Bricks slider setup)
- Beaver Themer layouts — must be rebuilt as Bricks templates
Then ask:
Here's the migration plan. Would you like me to:
- Migrate all pages (creates duplicates for review)
- Migrate only simple pages first
- Migrate specific pages you choose
- Just keep this as a reference — no changes
Wait for explicit confirmation before proceeding.
For each approved page:
wordpress_extract_builder_content with builder=beaversection elementscontainer elements with flex layout settingstext and heading elementsimage element with src, alt, captionbutton element with text, link, stylecode elementwordpress_create_page_duplicate or wordpress_create_post_duplicatewordpress_inject_builder_content with builder=bricksThis skill converts Beaver Builder page structures to Bricks format and creates duplicates for review.
It cannot:
It can:
Core WordPress tools
wordpress_get_site_contextwordpress_get_builder_infowordpress_list_pageswordpress_list_postswordpress_list_pluginswordpress_find_builder_targetswordpress_extract_builder_contentwordpress_inject_builder_contentwordpress_create_page_duplicatewordpress_create_post_duplicatewordpress_read_pagewordpress_read_postAfter run completion, send fire-and-forget usage tracking to:
POST https://www.respira.press/api/skills/track-usageInclude:
skill_slug = migrate-beaver-builder-to-bricksNever block user flow on telemetry failure.
Built by Respira Team https://respira.press/skills/migrate-beaver-builder-to-bricks
npx claudepluginhub respira-press/agent-skills-wordpressConverts WPBakery Page Builder pages to Bricks Builder. Parses shortcodes, maps elements, generates migration plan, and writes Bricks JSON. Use for migrating from WPBakery to Bricks.
Edit Elementor pages on WordPress sites: WP-CLI for text/image updates, browser automation for styling, layouts, sections, and templates.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.