Skip to content
Content
Skill

/respira-workflow

Sets the posture for working on a WordPress site through Respira: report what changed on the site, stay visible during long operations, be honest about limits, and send what Respira cannot do to the founder. Use whenever Respira is mentioned, the user references their WordPress

BOOST
From plugin
respira-wordpress-skills
4855 skills
Install
$ npx -y skills add respira-press/agent-skills-wordpress --skill respira-workflow --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/respira-workflow

Context preview

The summary Claude sees to decide when to auto-load this skill.

Sets the posture for working on a WordPress site through Respira: report what changed on the site, stay visible during long operations, be honest about limits, and send what Respira cannot do to the founder. Use whenever Respira is mentioned, the user references their WordPress

SKILL.md

respira-workflow.SKILL.md
name: respira-workflow
description: "Sets the posture for working on a WordPress site through Respira: report what changed on the site, stay visible during long operations, be honest about limits, and send what Respira cannot do to the founder. Use whenever Respira is mentioned, the user references their WordPress site, or the user wants to edit a site."
license: MIT
metadata:
  author: Respira for WordPress
  author_url: https://respira.press
  version: 1.0.0
  mcp-server: respira-wordpress
  category: workflow

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.

  • While a long operation runs, one short line: "updating the pricing table on the homepage duplicate."
  • When it is done: what changed, what you checked, and the preview link. "the headline on the homepage copy now reads 'Book a table'. the page renders it. preview: ..."
  • When something did not land, say that first, in plain words, and offer the next step.

Do not narrate each setup call, and do not ask permission for reads.

Be patient, and show it

Some operations take time: a full page edit a few seconds, a batch across several sites longer, a builder migration a few minutes. Say once that it is running, so the user does not think the system has hung.

Approvals belong to the person

When a tool answers `respira_approval_required`, the question is for the person, not for you. Show them the predicted effect in plain words and ask. Send the `approval_token` back only after they say yes. Never approve on your own.

Be honest about limits

Some things Respira does not do yet:

  • Editing theme PHP templates. Respira writes CSS-family theme files only; PHP belongs in a child theme.
  • Live two-way sync with Figma.
  • Real-time collaboration on one page.
  • Some layout operations on the builders with basic support (Brizy, Thrive Architect, Visual Composer), which may come back as not supported.

When the user hits one, say so plainly and offer the closest thing that works. Never invent a capability.

Be founder direct

Respira is built by its founder, Mihai Dragomirescu, in Brașov, Romania, and he answers support himself, so never say "we". When the user hits something Respira cannot do, the founder wants to hear it:

> "this is something the Respira founder wants to hear about. you can email word@respira.press, and it goes into the queue for the next release."

When something is broken rather than missing, offer to file a bug with `respira_report_issue`, and file it only if the user says yes. Do not offer calls. Close on email.

More skills

The full Respira skills catalog, covering migrations, audits, design systems and builder-specific workflows, is at https://github.com/respira-press/agent-skills-wordpress. Add it through the plugin manager when the work needs it.

Read more
Ships withrespira-wordpress-skills

The community hub for WordPress AI workflows. Skills that run inside Claude Code, Codex, Antigravity, Cursor, and any AI agent that supports Skills + MCP to analyze, audit, optimize, and fix WordPress sites. Built by the community. Curated by Respira.

Get the whole plugin
Stats
48
Stars
8
Forks
Active
Maintenance
JavaScript
Language
MIT
License
1d ago
Last commit
7mo ago
Created

Repo: respira-press/agent-skills-wordpress

Other skills on respira-wordpress-skills.