Skip to content
Skills Library
Marketing & content · Tool integration

respira-workflow

/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 site, or the user wants to edit a site.

Licence
MIT
Last repository change
18.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

  1. What Respira does for the user
  2. Say what changed, not which tool ran
  3. Be patient, and show it
  4. Approvals belong to the person
  5. Be honest about limits
  6. Be founder direct
  7. More skills
Original SKILL.md headings · 56 lines, 629 words
SKILL.md preview
---
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.1
  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 unless the site owner turned on direct editing (an unpublished item is edited in place); ask before publishing it with respira_approve_duplicate, and once the person has said yes to publishing in this conversation, publish later changes they ask for when done and tell them they are 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.

Versions

The database has no other skills named respira-workflow.

Database snapshot: 13.11.2026 · package version 5aeb4bcc5f85 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100wordpress-editing-safety
    Safety rules for editing a WordPress site through Respira. Use whenever the user mentions WordPress, Respira, editing a page or a site, a page builder, a snapshot, a duplicate, an approval, or rolling back. Covers read before write, duplicates on live pages, verifying every…
  • 100respira-setup-assistant
    Use when the user says 'set up respira', 'respira not connecting', 'check my respira connection', or 'fix respira'. Walks through first-time setup and diagnoses connection failures: timeouts, 401s, 403s, and plugin or server version mismatches.
  • 100wordpress
    Publish and manage posts on a self-hosted WordPress site via the WordPress REST API. Use when the user mentions WordPress, wp-admin, publishing / updating a blog post, managing categories or tags, or uploading media to their own WordPress site.
  • 81wordpress
    Use when the user asks to inspect or work on a connected WordPress site, including content, layouts, SEO, or commerce.
  • 90wordpress-publication-flow
    Use when publishing WordPress content through an agent. Review-first, approval-gated.
  • 100wordpress-content
    Create and manage WordPress posts, pages, media, categories, tags, and menus via WP-CLI or the REST API. Use whenever the user wants to publish a blog post on WordPress, update a page, upload media, manage categories or tags, update navigation menus, schedule posts, or do bulk…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.