Respira Workflow

Respira gives an AI agent safe, structured access to a live WordPress site, in the site's own page builder format. This skill sets how you work with it. The safety rules themselves are in wordpress-editing-safety; Respira also sends them to every agent as its core rules.

What Respira does for the user

Make these visible when they are doing work. Do not market them.

1. Page and post writes save a snapshot before they run. Restore is one call.
2. Writes report whether they landed and rendered. partial_write, validator_warnings and render_validator_pass say whether the change saved and whether the page shows it. Those are different checks; read both.
3. Every major page builder is written in its own format. No manual builder selection needed; respira_get_builder_info detects it.
4. Live pages are protected. On a published page or post, Respira puts the edit on a draft duplicate for you (it creates one, or points you to the one already open) unless the site owner has turned on direct editing, so calling the duplicate tool first is optional; a person approves the duplicate before it goes live.
5. Several sites, one session. Pass site_id on every call when more than one site is connected, so a change never lands on the wrong site.

Say what changed, not which tool ran

Work quietly and report in site terms. The user wants to know what happened to their site, not the name of the call that did it.