From Respira WordPress Skills Library
Migrates full WordPress sites from Brizy Builder to Gutenberg by auditing pages, mapping components to block equivalents, and converting 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-brizy-to-gutenbergThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Full-site migration from Brizy Builder to the WordPress block editor (Gutenberg). Audits every Brizy-built page, maps components 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 Brizy to Guten...
Full-site migration from Brizy Builder to the WordPress block editor (Gutenberg). Audits every Brizy-built page, maps components 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 Brizy to Gutenberg, switching from Brizy to blocks, converting Brizy pages to the block editor, or moving away from Brizy to native WordPress.
Brizy uses a proprietary content format with its own component system, storing data in brizy_post_uid and related custom meta fields. Gutenberg uses a flat block structure in post_content with HTML comment delimiters. The migration requires extracting Brizy's custom format, identifying each component type, and translating it to equivalent core Gutenberg blocks.
This skill reads every Brizy page, extracts the builder content, translates each component 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: Brizy
brizy_post_uid and Brizy's custom formatwordpress_extract_builder_content with builder=brizyTarget: 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, spacer, 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=brizy — find Brizy-managed pageswordpress_extract_builder_content with builder=brizyPresent a structured migration plan:
## Brizy → Gutenberg Migration Plan
### Site Overview
- Total Brizy pages: X
- Simple pages (direct mapping): X
- Moderate pages (some manual review needed): X
- Complex pages (significant manual work): X
### Component Mapping
| Brizy Component | Gutenberg Block | Notes |
|---|---|---|
| Section | Group | Container mapping |
| Row / Columns | Columns / Column | Layout structure |
| Text | Paragraph / Heading | Content parsed into blocks |
| Image | Image | Direct mapping |
| Button | Buttons > Button | Wrapped in container |
| ... | ... | ... |
### Migration Order
1. [Page Title] — Simple — estimated 2 min
2. [Page Title] — Moderate — estimated 5 min
...
### Items Requiring Manual Attention
- [Page X] — Brizy popup (no Gutenberg equivalent)
- [Page Y] — Brizy form (needs form plugin replacement)
- Global styles — must be configured in theme settings
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=brizy<!-- 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:video --> or <!-- wp:embed --> block<!-- wp:spacer --> block<!-- 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 Brizy 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-brizy-to-gutenbergNever block user flow on telemetry failure.
Built by Respira Team https://respira.press/skills/migrate-brizy-to-gutenberg
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.
Generates or edits WordPress Gutenberg blocks for the Greenshift/GreenLight plugin and converts data or vanilla HTML+CSS+JS to WordPress blocks.
Converts a page's raw HTML into WordPress block-editor markup using design tokens and a screenshot. Call per-page after extraction to produce `post_content` that renders with the theme's tokens and patterns.