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/preview-qa.md

View on GitHub
# Checks, preview and QA

**When to read:** you need an HTML download, diagnostics of a specific rendering problem, or the preview came
without PNG links. The preview of every iteration needs only `SKILL.md`.
**Return:** to §3 "Editing" of the visual workflow in `SKILL.md`, or to the user with the QA result.

- **HTML is not downloaded automatically.** Download HTML only for HTML QA or
  diagnostics where the HTML has to be read. PNG QA does not need HTML: MCP provides the PNG.
  First fix the absolute `<projectRoot>`; do not rely on the runner's cwd. For a
  campaign, name it by the campaign's `internalId` from `campaign_get`: `<internalId>.html`:

  ```bash
  # macOS/Linux
  curl --fail --location --silent --show-error "<htmlUrl>" \
    --output "<projectRoot>/<internalId>.html"

  # Windows PowerShell
  & curl.exe --fail --location --silent --show-error "<htmlUrl>" `
    --output "<projectRoot>/<internalId>.html"
  ```

  A campaign GUID needs no name sanitizing and prevents conflicts between different
  campaigns. A new QA/debug download of the same campaign replaces the previous local
  file: this is expected; the file represents the last downloaded backend render, not
  necessarily the last JSX edit. Do not use the campaign name alone and do not invent
  your own name without the campaign's `internalId`. If the download failed,
  keep `htmlUrl`, report the `curl` error and do not substitute the HTML.
  Count a download as successful only with exit code `0` and a non-empty output file.
  A download error does not cancel a successful backend preview and does not by itself block
  save. HTML QA is unavailable until the download is repeated successfully; PNG QA via MCP
  does not depend on the HTML download.
  For a standalone preview without a target campaign, use
  `<projectRoot>/standalone-preview.html`; it represents the last standalone
  render and must not be used as an artifact of a specific campaign.
- **A request to check the email or its rendering is already consent to diagnostics:** do not ask separately
  whether you may download the HTML or open the PNG.
- **HTML QA** reads the downloaded file
  selectively and checks the expected texts, images, layout and obvious
  escaping/structure problems against the user's request. Do not read the whole HTML
  into the model's context without need. Where the canvas differs from the sent email — `#` links, sample
  values, placeholders — is in the wiki page `email.tags.template`, "In the preview": none of it is a defect.
  In the canvas HTML every link inside `<Text>` is `#`, ordinary ones too. Addresses and the unsubscribe link are checked against the JSX, not the canvas HTML; a link inside a
  `<SyncBlock>` — `email.topics.unsubscribe_link`.

  PNG QA uses the desktop/mobile links from the preview response and visually checks
  content, clipping, the responsive branch and image loading. This is best-effort QA, not
  a full Outlook/Gmail compatibility test.
- **PNG links are in the same preview response** — no second tool, no second call. No local screenshot, except the fallback below. Only mobile or only desktop asked — show that link; for
  responsive diagnostics — both. To the user they are "the desktop snapshot" and "the mobile snapshot".
- **Fallback if there are no PNG links.** If preview returned an error or came without
  PNG links, and the user still needs a visual check, in Cowork you may use
  Claude in Chrome as an emergency fallback to view/snapshot the HTML preview. Tell
  the user explicitly that this is a fallback, not the standard PNGs from the tool's response. The browser here only
  reads: using it to go into the Mindbox interface and click anything on the user's behalf is forbidden.
- **Diagnosing follow-up complaints.** If the user reports a problem with the
  content/rendering of a generated campaign, get the current JSX, call a fresh
  HTML preview, download the HTML only if HTML fragments need checking; for a
  visual/responsive problem, check the desktop/mobile PNG links from the preview
  response. Use an existing local HTML only if it is provably fresh
  for the same JSX.

QA found a defect and Generator changed the JSX — the local HTML is stale too. The user continues QA — repeat the
preview and the download; otherwise the new JSX gets its usual preview.
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