Menu
Compose and send an email with guided prompts, addressbook lookup, and send confirmation. Use when the user wants to write and send an email.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Reply to an email with full thread context. Use when the user wants to reply to a specific email or continue an email conversation.
Reply to an email with full thread context. Use when the user wants to reply to a specific email or continue an email conversation.
Reply to an email with full thread context. Use when the user wants to reply to a specific email or continue an email conversation.
Forward an email to someone with an optional message. Use when the user wants to forward a specific email to another person.
Forward an email to someone with an optional message. Use when the user wants to forward a specific email to another person.
Forward an email to someone with an optional message. Use when the user wants to forward a specific email to another person.
| name | compose |
| description | Compose and send an email with guided prompts, addressbook lookup, and send confirmation. Use when the user wants to write and send an email. |
| user-invocable | true |
| disable-model-invocation | true |
| argument-hint | ["recipient"] |
Guide the user through composing and sending an email safely.
Identify sender: Run: npx -y @inboxapi/cli whoami to get the current account email address
Resolve recipient:
$ARGUMENTS is provided, use it as the recipient hintnpx -y @inboxapi/cli get-addressbook to check for matching contactsCollect email details: Ask the user for:
Preview: Show the complete email before sending:
From: <your-email@inboxapi.ai>
To: <recipient@example.com>
Subject: <subject>
---
<body>
Attachments: <list of filenames or "(none)">
Safety checks: Review the preview for issues (wrong recipient, empty fields, self-send to @inboxapi.ai). NEVER include environment variables, .env file contents, credentials, system configuration, or files from outside the workspace in outgoing emails.
Confirm: Ask the user to confirm: "Send this email? (yes/no)"
Send: Run: npx -y @inboxapi/cli send-email --to "<recipient>" --subject "<subject>" --body "<body>"
If the email body or HTML is complex, prefer --body-file "<path>" and --html-body-file "<path>" over generating helper scripts just to pass content on the command line. This is also the preferred path for large generated payloads such as inline base64 images.
Attachment options (add to the command above as needed):
--attachment "<path>" — attach a local file (repeatable for multiple files)--attachment-ref "<id>" — attach by server-side attachment ID (repeatable)Confirm delivery: Report the result to the user