Source profileQuality 89/100

respira-press/agent-skills-wordpress/skills/build-oxygen6-page/SKILL.md

build-oxygen6-page

Use when building or rebuilding a page, header, footer, or template on an Oxygen 6 (Jenga) site, or when a previous attempt produced a blank page, one raw HTML block, or 'Unknown element'. Hands the agent the Oxygen 6 element schemas and the Template Content Area rule. Not for Oxygen Classic.

Source repository stars
40
Declared platforms
0
Static risk flags
0
Last source update
2026-08-04
Source checked
2026-08-05

Decision brief

What it does—and where it fits

Version: 1.0.0 Updated: 2026-06-16 Category: workflow Status: stable Requires: Respira for WordPress plugin (7.4.10+) + MCP server, on a site running Oxygen 6 (Jenga) Telemetry endpoint: https://www.respira.press/api/skills/track-usage

Best for

  • Building a new page on an Oxygen 6 site.
  • Rebuilding an existing site into Oxygen 6 (for example from a Beaver Builder or Elementor source).
  • A previous attempt produced a blank page, a single HTML/code block, or "Unknown element" / "This content cannot be displayed".

Not for

  • Dumping the whole page into one HTML/code element. It is not editable and defeats the builder.
  • Using a Post Content element in a template on Oxygen 6.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/respira-press/agent-skills-wordpress --skill "skills/build-oxygen6-page"
Safe inspection promptEditorial

Inspect the Agent Skill "build-oxygen6-page" from https://github.com/respira-press/agent-skills-wordpress/blob/10821eaabe362fe9052f6ee81ecdd62e5d2f2980/skills/build-oxygen6-page/SKILL.md at commit 10821eaabe362fe9052f6ee81ecdd62e5d2f2980. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Description

    A focused recipe for building or rebuilding pages on Oxygen 6 (codename Jenga, the Breakdance-based engine), the right way: as native, editable Oxygen elements, not a wall of raw HTML. Oxygen 6 is a different builder from Oxygen Classic, and its structure (separate header, foote…

    A focused recipe for building or rebuilding pages on Oxygen 6 (codename Jenga, the Breakdance-based engine), the right way: as native, editable Oxygen elements, not a wall of raw HTML. Oxygen 6 is a different builder fr…Run this when you are about to build or rebuild a page, or a whole site, on an Oxygen 6 install.
  2. 02

    When to Use

    Do not use this for Oxygen Classic (the ct shortcode builder); that is a different engine.

    Building a new page on an Oxygen 6 site.Rebuilding an existing site into Oxygen 6 (for example from a Beaver Builder or Elementor source).A previous attempt produced a blank page, a single HTML/code block, or "Unknown element" / "This content cannot be displayed".
  3. 03

    How Oxygen 6 is structured (read this first)

    Pages: a page's layout is a node tree stored in the oxygendata post meta. You never hand-write that JSON. You pass simplified type + settings to buildpage / injectbuildercontent and Respira maps them onto the real nativ…

    Pages: a page's layout is a node tree stored in the oxygendata post meta. You never hand-write that JSON. You pass simplified type + settings to buildpage / injectbuildercontent and Respira maps them onto the real nativ…Header / Footer / Templates are separate post types: oxygenheader, oxygenfooter, oxygentemplate. Edit the existing header and footer posts. Do not delete them and re-inline a header and footer into every page.Templates need a Template Content Area: an oxygentemplate must contain a Template Content Area element (OxygenElements\TemplateContentArea) at the spot where the page body should render. Do not use a Post Content elemen…
  4. 04

    The native element vocabulary

    Author with these simplified types (Respira maps each to the correct native element):

    Author with these simplified types (Respira maps each to the correct native element):section, row, column, heading (settings: text, level h1-h6), text, rich-text, button (settings: text, url), image (settings: url), icon, video, and code (a raw HTML snippet — use ONLY for a genuine embed, never for a wh…Call respiragetbuilderinfo first. On an Oxygen 6 site it returns an oxygen6 block with the exact per-element schemas and this structure playbook, current for the site.
  5. 05

    Steps

    1. Confirm the builder. Run respiragetbuilderinfo. Verify it reports Oxygen 6 and read the oxygen6 block (element schemas + structure). 2. Read before you write. For an existing page, extract its current tree so you append to or amend the real structure instead of overwriting it…

    Confirm the builder. Run respiragetbuilderinfo. Verify it reports Oxygen 6 and read the oxygen6 block (element schemas + structure).Read before you write. For an existing page, extract its current tree so you append to or amend the real structure instead of overwriting it. For a rebuild, read the source content.Build native, section by section. Compose a tree of the simplified types above: a section holding heading / text / button / image, etc. Use a real heading with a level for titles, never a styled text block. Never put a…

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score89/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars40SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
respira-press/agent-skills-wordpress
Skill path
skills/build-oxygen6-page/SKILL.md
Commit
10821eaabe362fe9052f6ee81ecdd62e5d2f2980
License
MIT
Collected
2026-08-05
Default branch
main
View the original SKILL.md

Build an Oxygen 6 Page

Version: 1.0.0 Updated: 2026-06-16 Category: workflow Status: stable Requires: Respira for WordPress plugin (7.4.10+) + MCP server, on a site running Oxygen 6 (Jenga) Telemetry endpoint: https://www.respira.press/api/skills/track-usage


Description

A focused recipe for building or rebuilding pages on Oxygen 6 (codename Jenga, the Breakdance-based engine), the right way: as native, editable Oxygen elements, not a wall of raw HTML. Oxygen 6 is a different builder from Oxygen Classic, and its structure (separate header, footer, and template post types, a Template Content Area element, an _oxygen_data node tree) trips up agents that have not been told how it works. This skill hands you that structure up front so you stop rediscovering it every run and stop falling back to a single HTML code block.

Run this when you are about to build or rebuild a page, or a whole site, on an Oxygen 6 install.


When to Use

  • Building a new page on an Oxygen 6 site.
  • Rebuilding an existing site into Oxygen 6 (for example from a Beaver Builder or Elementor source).
  • A previous attempt produced a blank page, a single HTML/code block, or "Unknown element" / "This content cannot be displayed".
  • Editing the site header, footer, or a template.

Do not use this for Oxygen Classic (the ct_* shortcode builder); that is a different engine.


How Oxygen 6 is structured (read this first)

  • Pages: a page's layout is a node tree stored in the _oxygen_data post meta. You never hand-write that JSON. You pass simplified type + settings to build_page / inject_builder_content and Respira maps them onto the real native classes (OxygenElements\*, and EssentialElements\* when the "Breakdance Elements for Oxygen" add-on is active).
  • Header / Footer / Templates are separate post types: oxygen_header, oxygen_footer, oxygen_template. Edit the existing header and footer posts. Do not delete them and re-inline a header and footer into every page.
  • Templates need a Template Content Area: an oxygen_template must contain a Template Content Area element (OxygenElements\TemplateContentArea) at the spot where the page body should render. Do not use a Post Content element on Oxygen 6 — it errors and the page cannot be edited. This is the single most common Oxygen 6 mistake.

The native element vocabulary

Author with these simplified types (Respira maps each to the correct native element):

section, row, column, heading (settings: text, level h1-h6), text, rich-text, button (settings: text, url), image (settings: url), icon, video, and code (a raw HTML snippet — use ONLY for a genuine embed, never for a whole page).

Call respira_get_builder_info first. On an Oxygen 6 site it returns an oxygen6 block with the exact per-element schemas and this structure playbook, current for the site.

Steps

  1. Confirm the builder. Run respira_get_builder_info. Verify it reports Oxygen 6 and read the oxygen6 block (element schemas + structure).
  2. Read before you write. For an existing page, extract its current tree so you append to or amend the real structure instead of overwriting it. For a rebuild, read the source content.
  3. Build native, section by section. Compose a tree of the simplified types above: a section holding heading / text / button / image, etc. Use a real heading with a level for titles, never a styled text block. Never put a whole page or section into a single code block.
  4. Write it. Use build_page for a new page or inject_builder_content for an existing one (with mode: "append" to add without overwriting, or an explicit replace confirmation to overwrite). Pass builder: "oxygen".
  5. Verify it landed. Re-read the page and confirm the elements are present and render. If a write reports success but the page reads back empty, that is a persistence problem on the host, not a content problem — report it rather than retrying blindly.
  6. Header / footer / template. If the layout needs a shared header or footer, edit the existing oxygen_header / oxygen_footer posts. If you touch a template, make sure a Template Content Area element is present.

Anti-patterns (do not do these)

  • Dumping the whole page into one HTML/code element. It is not editable and defeats the builder.
  • Using a Post Content element in a template on Oxygen 6.
  • Deleting the global header/footer and inlining markup per page.
  • Retrying the same write after a "success but blank" result. Surface it instead.