@aksp/opencrew 1.6.1 → 1.6.3

package/templates/skills/resend/SKILL.md

@@ -19,6 +19,7 @@ mcp:
   command: npx
   args: ["-y", "resend-mcp"]
   transport: stdio
+side_effects: irreversible
 env:
   - RESEND_API_KEY
 categories: [email, automation, communication]
@@ -34,17 +35,53 @@ so the crew only needs to compose the content and call the MCP tools.
 
 ## Instructions
 
+### Confirmation (before any send, schedule or delete)
+
+Sending is **irreversible**: an e-mail cannot be taken back once it leaves. The rule below is
+about the **action**, whatever the tool is called on the server: before ANY call that sends,
+schedules or deletes, follow this order. The messages to the user are in PT-BR, as written here.
+
+1. Prepare **from**, **to**, **subject**, **body** (HTML or plain text) and attachments. Call no
+   sending tool yet.
+2. **Preview (prévia)** — show the user exactly this, filled in:
+   ```
+   Vou enviar este e-mail:
+   De: {remetente}
+   Para: {N} destinatário(s): {até 10 endereços}… e mais {N-10}
+   Assunto: {assunto}
+   Início do texto: {3 primeiras linhas}
+   Anexos: {nomes}, ou nenhum
+   Quando: agora, ou agendado para {data e hora}
+   Para enviar, responda com a palavra enviar. Qualquer outra resposta cancela.
+   ```
+   (`{N}` is the total of recipients — to, CC and BCC; in a batch, of all the e-mails together.
+   List at most 10 addresses; "… e mais {N-10}" only when there are more. `Quando`: write `agora`
+   or `agendado para …`. `Anexos`: the file names, or `nenhum`.)
+3. Wait for the word **enviar**. Any other answer — including silence, "ok" or "sim" — cancels:
+   say "Nenhum e-mail foi enviado." and stop.
+4. Only after the word: make **one single call** — `send_email` for one e-mail,
+   `batch_send_emails` for a batch.
+5. On success: check the response for the `id` (one per item in a batch) and save it to the step
+   output file immediately.
+6. On failure, timeout or missing answer: do NOT repeat the call again, in this step or in a retry.
+   Tell the user: "⚠️ Não recebi a confirmação do Resend. O e-mail pode já ter sido enviado.
+   Confira no painel antes de tentar de novo. Não vou repetir sozinho."
+7. One confirmation is worth one send. If this step runs again in the same run (a retry, or back
+   from a rejected review), show the preview again, after this line: "Este passo já tentou enviar
+   nesta execução. Confira se saiu antes de confirmar de novo." — and wait for the word.
+8. A call that **deletes** (removing a contact or a domain) follows the same order with its own
+   word: "Vou apagar isto: {o que será apagado}. Para apagar, responda com a palavra apagar.
+   Qualquer outra resposta cancela." Any other answer: "Nada foi apagado."
+
 ### Sending a single email
 
-1. Prepare **from**, **to**, **subject**, and **body** (HTML or plain text).
-2. Call the Resend MCP `send_email` tool.
-3. Check the response for a successful `id` — that confirms the email was queued.
+Fields: **from**, **to**, **subject** and **body**; a successful `id` in the response confirms the
+e-mail was queued.
 
 ### Sending a batch
 
-1. Build an array of email objects (same fields as single send).
-2. Call the Resend MCP `batch_send_emails` tool.
-3. Each item in the response will have its own `id` or error.
+Build an array of email objects (same fields as single send). Each item in the response has its
+own `id` or error — report both; never send the failed ones again on your own.
 
 ### Attachments
 
@@ -52,25 +89,27 @@ Pass attachments as an array with `filename`, `path` (local file), `url`, or `co
 
 ### Scheduling
 
-Include a `scheduled_at` field (ISO 8601 datetime) to schedule future delivery.
+Include a `scheduled_at` field (ISO 8601 datetime) to schedule future delivery. A scheduled e-mail
+asks for the same preview and the same word, with the date and time on the `Quando` line.
 
 ## Best practices
 
 - Validate **from** against a verified domain before sending — Resend rejects unverified senders.
 - Keep subject lines under 80 characters for better deliverability.
 - For batch sends, group by shared content to reduce payload size.
-- Always check the response for errors and surface them to the user rather than silently failing.
+- Always check the response for errors and surface them to the user rather than silently failing
+  — and never by sending again.
 - When composing HTML emails, keep the markup simple — most email clients ignore complex CSS.
 
 ## Available operations
 
-- **Send Email** — Single email with HTML/text body, attachments, CC/BCC, reply-to
-- **Batch Send** — Multiple emails in one call
-- **Schedule Email** — Queue an email for future delivery
+- **Send Email** — Single email with HTML/text body, attachments, CC/BCC, reply-to (only after the word)
+- **Batch Send** — Multiple emails in one call (only after the word)
+- **Schedule Email** — Queue an email for future delivery (only after the word)
 - **List/Get Emails** — Check delivery status of sent emails
 - **Cancel Email** — Cancel a scheduled email before it sends
-- **Manage Contacts** — Create, list, update, and remove contacts from audiences
-- **Manage Domains** — Add and verify sender domains
+- **Manage Contacts** — Create, list, update, and remove contacts from audiences (removing asks for the word `apagar`)
+- **Manage Domains** — Add and verify sender domains (removing asks for the word `apagar`)
 
 ## Setup