mindbox-cloud/agent-skills / plugins/mindbox/skills/email-ops
email-ops
VerifiedOperational actions for Mindbox emails — preview, reading and saving the visual template, saved templates (an email by one, changing, creating, copying), reading/editing campaign metadata and recipients (a segment or a filter), finding gallery assets via MCP, uploading images from the user's machine through the MCP App panel, PNG preview. Use together with the email skill when images, a preview, a check or a write to Mindbox are needed.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 34.0 KB |
| references/feedback-examples.md | markdown | 5.5 KB |
| references/preview-qa.md | markdown | 4.2 KB |
| references/recipients.md | markdown | 1.9 KB |
| references/saved-template.md | markdown | 3.2 KB |
references/recipients.md
View on GitHub# Campaign recipients: segment or filter
**When to read:** the user asks to set or change a campaign's recipients, to send it
"to a segment", "to a filter" or "to those who …".
**Return:** to the user with the write result; the live launch stays in the UI.
The "exclude inactive/new" toggles are UI only.
## Workflow
1. `campaign_get`. If the editability line says the campaign is not edited from here or is working, or its
`state` is scheduled or already sending, do not change the recipients either: such a campaign is
managed in the editor (the prohibition is in the "`campaign_edit`, `campaign_edit_content`,
`campaign_create`" section of `SKILL.md`). Remember the current recipients from the `Recipients`
block.
2. Choose the method by the request:
- **An existing segment by name** → `segments_list`. Several candidates or nothing —
show what was found by name and let the user choose; do not ask the person for an id.
- **The audience is described by conditions, or a segment plus conditions** → the filter-building skill (`filter-build`)
with `root: User`, `filterablePropertySet: Default` and `includeFilterJson: true`. The result
is usable only when the platform confirmed it (`FILTER_OK`). If the filter-building skill is not in your skill listing, do not compose
the filter yourself: say that recipients by conditions are unavailable and offer a segment.
3. Confirmation before the write is always separate, even with an explicit request. Name
the campaign, the method and the audience in words — the segment name or the filter conditions — and
say that the previous recipients, if any, will be replaced.
4. `campaign_edit`, then check the `Recipients` block of the response and say that launching the campaign is done in the UI.
A version conflict — per the version-conflict item of the "Campaign version chain" in `SKILL.md`, without an
automatic retry.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |