Skip to content

mindbox-cloud/agent-skills / plugins/mindbox/skills/email-ops

email-ops

Verified

Operational 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.

FileKindSize
SKILL.mdskill md34.0 KB
references/feedback-examples.mdmarkdown5.5 KB
references/preview-qa.mdmarkdown4.2 KB
references/recipients.mdmarkdown1.9 KB
references/saved-template.mdmarkdown3.2 KB

references/saved-template.md

View on GitHub
# Saved templates

**When to read:** the user asks for an email "by template X", "from my templates", to see their saved templates,
or to change, rename, create or copy a saved template.
**Return:** to the canonical workflow in `SKILL.md` — §3 for edits; for an email by a template also §1–§2 and §4–§5.

**Choosing the template** — `client_visual_template_list`. A template named in words with no exact match by
name, or several — show the candidates and let the user choose. No look-alike.

## An email by a saved template

`visual_template_get` gives a saved template's blocks as JSX; its look comes only from the saved template's
settings, taken into the preview and the save.

1. **Target.** §1–§2 of the canonical workflow; a new campaign — "New campaign from scratch" first.
2. **Reading.** `visual_template_get` of the saved template.
3. **Shared styles**, when the generator needs them — `visual_template_theme_get` on the saved template: after
   the save the email has the template's styles, not the campaign's.
4. **Confirmation** — §4, with the shared-styles line "the email's width, background, CSS and shared styles are
   taken from template <name>", plus "and changed by this document" if it has `<Theme>`.
5. **Save** — §5 with the saved template's settings, in this one save only. The next edits are saved
   without them: the campaign already holds the settings, and passing them again overwrites what the user has
   changed in the editor since.

## Changing, creating, copying a saved template

1. **Changing the content** — `visual_template_get` of the saved template; edits and the preview —
   §3 and the preview rules, the saved template standing wherever they name the campaign's template; the write —
   `client_visual_template_edit`.
2. **A copy** — "save this email as a template", "a template based on X": `client_visual_template_create` as a copy
   of the campaign's template or of X. The editor copies what is saved, settings
   included; its JSX is not read. A campaign — `campaign_get` first; several A/B variants, or two versions listed
   (active and draft) — ask which; any campaign state reads. Changes to the content — one confirmation before the
   copy, naming the copy and the change, then item 1 on the copy. The email in this conversation has changes not
   saved to the campaign — not a copy: item 3 with that JSX and the campaign's template's settings.
3. **From JSX** — `client_visual_template_create` with a new content from the generator's JSX and the settings of
   the template whose look the user names, or of the campaign's template of item 2. Without them the template gets
   the platform defaults.
4. **The name** of a new template or a copy is the user's: ask for it if the request does not give one.
5. **Confirmation** before writing JSX — `client_visual_template_edit` of the JSX and
   `client_visual_template_create` from JSX: the template's name, the change and
   the shared-styles line — for a change, the line of §4; for a new template, "the template's width, background,
   CSS and shared styles are taken from <template>" or "… are the platform defaults", plus "and changed by this
   document" if it has `<Theme>`. A rename and a copy are done on the request.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall