activity-report-compos…
Use when the user asks for a client report, a monthly or activity report, a case study draft,…
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
$ npx -y skills add respira-press/agent-skills-wordpress --skill respira-workflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/respira-workflowContext 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
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 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.
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.
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.
Do not narrate each setup call, and do not ask permission for reads.
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.
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.
Some things Respira does not do yet:
When the user hits one, say so plainly and offer the closest thing that works. Never invent a capability.
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.
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.
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.
Repo: respira-press/agent-skills-wordpress
Use when the user asks for a client report, a monthly or activity report, a case study draft,…
Use on any page build, redesign, or 'make it look better' request on a site that has (or…
Use when the user says 'extract my brand voice', 'what is my writing style', or 'analyze my…
Use when building an Elementor page by hand with respira_build_page: from a brief, a…
Use when building or rebuilding a page, header, footer, or template on an Oxygen 6 (Jenga)…
Use when the user says 'export my site', 'backup my pages before editing', 'download my…