migrate-beaver-builder-to-gutenberg — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited migrate-beaver-builder-to-gutenberg (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Full-site migration from Beaver Builder to the WordPress block editor (Gutenberg). Audits every Beaver Builder page, maps modules to their Gutenberg block equivalents, builds a migration plan for approval, and executes page-by-page conversion into native block markup — all through duplicates so your live site stays untouched. Use this skill whenever someone mentions migrating from Beaver Builder to Gutenberg, switching from Beaver Builder to blocks, converting Beaver Builder pages to the block editor, or moving away from Beaver Builder to native WordPress.
Beaver Builder uses a module-based architecture with rows, columns, and modules stored in _fl_builder_data and _fl_builder_data_settings. Gutenberg uses a flat block structure in post_content with HTML comments as block delimiters. The architectural gap is moderate — Beaver Builder's row/column grid must be translated to Gutenberg's Group, Columns, and Column blocks, while individual modules map to core blocks.
This skill reads every Beaver Builder page, extracts the module structure, translates each row/column/module to its Gutenberg block equivalent, and writes the result to duplicate pages in native block markup — 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: Gutenberg (Block Editor)
post_content as HTML with block comment delimiters<!-- wp:paragraph --><p>Text</p><!-- /wp:paragraph -->wordpress_update_page / wordpress_update_post)paragraph, heading, image, buttons, columns, group, html, video, separator, embed, 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 → Gutenberg 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 Mapping
| BB Module | Gutenberg Block | Notes |
|---|---|---|
| Text Editor | Paragraph / Heading | Content parsed into appropriate blocks |
| Photo | Image | Direct mapping |
| Button | Buttons > Button | Wrapped in Buttons container |
| Row (2 col) | Columns (2 col) | Width ratios preserved where possible |
| ... | ... | ... |
### Migration Order
1. [Page Title] — Simple — estimated 2 min
2. [Page Title] — Moderate — estimated 5 min
...
### Items Requiring Manual Attention
- [Page X] — PowerPack module (no core block equivalent)
- [Page Y] — Content slider (basic fallback only)
- Beaver Themer layouts — must be rebuilt as block templatesThen ask:
Here's the migration plan. Would you like me to: 1. Migrate all pages (creates duplicates for review) 2. Migrate only simple pages first 3. Migrate specific pages you choose 4. Just keep this as a reference — no changes
Wait for explicit confirmation before proceeding.
For each approved page:
wordpress_extract_builder_content with builder=beaver<!-- wp:group --> blocks<!-- wp:columns --> with <!-- wp:column --> children<!-- wp:paragraph --> and <!-- wp:heading --> blocks<!-- wp:image --> with src, alt, caption<!-- wp:buttons --> wrapper with <!-- wp:button --> child<!-- wp:html --> block<!-- wp:paragraph --><p>[MIGRATION NOTE: ...]</p><!-- /wp:paragraph -->wordpress_create_page_duplicate or wordpress_create_post_duplicatepost_content with the Gutenberg markup via wordpress_update_page or wordpress_update_postThis skill converts Beaver Builder page structures to Gutenberg block markup 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_create_page_duplicatewordpress_create_post_duplicatewordpress_update_pagewordpress_update_postwordpress_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-gutenbergNever block user flow on telemetry failure.
Built by Respira Team https://respira.press/skills/migrate-beaver-builder-to-gutenberg
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.