- Home
- Skills
- Frontend & Web Apps
- Oxygen Builder: AI-Built Sections That Stay Editable
More screenshots
Works with the AI Agents you already use
Oxygen Builder: AI-Built Sections That Stay Editable
Tired of AI agents breaking Oxygen pages? Get new sections built on your server that your team can still edit.
$12
Oxygen Builder: AI-Built Sections That Stay Editable
Example session with this skill installed
Our WordPress site is built with Oxygen Builder (classic, 4.9). I exported the Services page (post ID 214) into ./site/ along with some notes. Add a "Why patients choose us" section with three cards (the copy is in ./site/new-section-copy.md) right after the hero, styled like the existing service cards. Write the script I will run on the server over SSH with WP-CLI to install it, plus the exact commands to run. The office manager still edits this page in the Oxygen editor every week, so it has to stay fully editable there. Put everything you produce in ./out/.
- Read your context and instructions
- Compiled the oxygen builder
- Generated the app files
I've written the install script and the section spec, but nothing has been run against WordPress. I had no server access, so the server-side steps are untested.
The spec passes the offline linter with 0 errors and 0 warnings, and a local preview of the generated shortcodes came out as expected. Your page export also lints clean.
What it builds. The section goes right after the Hero, before "Our services". It has a "Why patients choose us" heading and a three-column grid of cards, using your copy from new-section-copy.md. These are native Oxygen elements: a section, headline, grid, three card divs, and a headline and text block in each card. The styles sit on the elements themselves, so the office manager can click and edit everything in the Oxygen editor. The only Code Block rule is a mobile @media that stacks the cards on phones.
Styling. The cards copy the service cards: white background, 12px corners, the same shadow, and the same colors and type sizes. The section background is white so it stays distinct from the mist-colored services section below it.
What the script does. install-why-us.sh runs without writing anything unless you pass write:
- It runs a read-only check of page 214 and stops if the section is already there.
- With
writeit backs up page 214 to~/oxy-backups. It then inserts the section after the Hero, signed by Oxygen on your server, and regenerates the CSS for page 214 only. - It only inserts new elements, so the office manager's existing edits aren't touched.
Commands to run (the full list, with expected output at each step, is in out/README.md):
- Copy
out/to the server (for examplescp -r out/ you@server:~/oxy-install), thencd ~/oxy-install. - Fetch
/services/withcurland save it asbefore.html. Searching it for "Why patients choose us" should find 0 matches. bash install-why-us.shis the dry run. It should report 13 new elements with valid signatures.bash install-why-us.sh writedoes the backup, the insert and the CSS regeneration.- Purge your host's page cache.
- Fetch
/services/again. The heading should now appear once, along with the new element ids ending in-214. - Open
/?ct_builder=true&page_id=214. Click the section, the grid and each card. Check that the styles show in the panels and the three columns stay put.
To undo it, run wp eval-file ~/oxy-install/oxy/oxy-backup.php 214 <backup folder> restore, then purge the cache. The write step prints the backup folder name.
Before you run it. The script assumes the WordPress root is ~/public_html; set WP_ROOT if it's elsewhere. The helper scripts were written against the Oxygen 4.9 source, so check the recon output before you run write.
Everything is in ./out/:
install-why-us.shwhy-us-section.spec.jsonREADME.mdoxy/
before.html
ZIP · project files
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem. Ask an AI agent to add a section to an Oxygen Builder page and you get a script plus homework: click "Sign all shortcodes" in wp-admin (which re-signs every page of that type), press the site-wide CSS rebuild, then check the page by eye. Ask it for a new page from a mockup and it can save the design under a meta key Oxygen 4.x never reads, so the page stays blank and nothing reports an error. This skill makes the agent finish the job: the new section goes live signed, styled like your page, and editable in the Oxygen editor, with no wp-admin cleanup.
What it does. You ask for something like "Add a 'Why patients choose us' section with three cards after the hero, styled like the service cards. The office manager edits this page in Oxygen every week." The agent writes the section from your page's own styles, plus a script and the exact commands to install it over SSH with WP-CLI. You run the dry run (it reports the new elements and that every signature is valid), then write, then purge your cache. The heading appears on the live page, and when you click a card in the Oxygen editor its font size, weight, color and heading tag are right there in the panel.
- Native Oxygen elements with the styles on each element, so whoever edits the page next can click anything and change it in the editor.
- Signed on your server for that one page, so you skip the "Sign all shortcodes" pass that touches every page of that type.
- CSS rebuilt for that page only, and it confirms the site-wide
universal.cssdid not change, so the rest of the site is left alone. - Copies style keys and global colors from elements already on the page, so the new section looks like it belongs.
- Checks the served page before and after, so you know the section is live instead of guessing from the editor.
- Backup first, dry run by default, one-command restore, so changing your mind costs one line.
Why this beats prompting it yourself.
Ask a capable agent the same thing without this skill and it tends to:
- Leave the new elements unsigned and tell you to "Sign all shortcodes" in wp-admin.
- Send you to the site-wide CSS rebuild button.
- On a new page, write the design under keys Oxygen 4.x never reads, so the page stays blank.
With the skill, the agent:
- Signs the new elements on your server, for that page only.
- Rebuilds that page's CSS and confirms the site-wide file did not change.
- Writes the rows Oxygen 4.x reads and checks the live page before and after.
Known limitations. Oxygen Classic 4.x only; Oxygen 6 stores pages differently and is not supported. It adds new elements (after an element, at the end, or as a whole new page) and does not move or restyle elements already there. Phone layouts go in a small code block as @media rules, not Oxygen's per-breakpoint panels. The install step needs SSH and WP-CLI; without them the agent writes the files and commands and you run them. Built for Oxygen 4.9: on other 4.x versions run the read-only check and the dry run first, on a staging copy when you have one.
What's inside. SKILL.md (the rules and method), four WP-CLI scripts (oxy-apply.php, oxy-recon.php, oxy-backup.php, oxy-regen-css.php), an offline linter (oxy_lint.py), references on how Oxygen Classic stores a page and which style keys keep elements editable, and an example three-card section spec.
$12. Pays for itself the first time a new section goes live without a "Sign all shortcodes" pass or a site-wide CSS rebuild on a live site.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
- Oxygen Classic 4.x only. Oxygen 6 uses a different format and is not supported.
- Inserts at the top level of a page (after an element, at the end, or a whole new page). It does not move or restyle elements already on the page.
- Built for Oxygen Classic 4.9. On other 4.x versions run
oxy-recon.phpand the dry run first, and use a staging copy when you have one. - Global colors like
color(3)only work if your site defines them; the agent copies them from elements already on the page. - Mobile breakpoints go in a small code block as
@mediarules, not Oxygen's per-breakpoint panels. - Without shell access the agent writes the files and the commands, and you run them.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
File Scopes
no network calls in the scripts, no credentials, no environment reads, nothing installed. `oxy-apply.php` writes nothing unless the last argument is `write`. `oxy-recon.php` and `oxy_lint.py` are read-only.