email-notify
Send SMTP email notifications after Codex completes a task. Use when one Codex or Claude run is finished, or when you need to notify on task completion with device name, project name, status, and summary via email.
Best use case
email-notify is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Send SMTP email notifications after Codex completes a task. Use when one Codex or Claude run is finished, or when you need to notify on task completion with device name, project name, status, and summary via email.
Teams using email-notify should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/email-notify/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How email-notify Compares
| Feature / Agent | email-notify | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Send SMTP email notifications after Codex completes a task. Use when one Codex or Claude run is finished, or when you need to notify on task completion with device name, project name, status, and summary via email.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Email Notify ## Overview Send an email notification after each Codex task. Use the helper script to resolve the project name and send via SMTP. ## User Preparation ### 1) Configure environment variables Add the following lines to `~/.bashrc` (Linux) or `~/.zshrc` (macOS): ``` export CODEX_MACHINE_NAME="Machine-name" # e.g., Macbook export CODEX_EMAIL_SMTP_HOST="smtp.example.com" export CODEX_EMAIL_SMTP_PORT="587" export CODEX_EMAIL_USERNAME="user@example.com" export CODEX_EMAIL_PASSWORD="..." export CODEX_EMAIL_FROM="user@example.com" export CODEX_EMAIL_TO="recipient1@example.com,recipient2@example.com" export CODEX_EMAIL_USE_TLS="false" # true/false, default false export CODEX_EMAIL_USE_SSL="true" # true/false, default true ``` If your SMTP server does not require auth, leave `CODEX_EMAIL_USERNAME` and `CODEX_EMAIL_PASSWORD` unset. Set `CODEX_EMAIL_USE_SSL` to `true` for SMTPS (typically port 465) and `CODEX_EMAIL_USE_TLS` to `true` for STARTTLS. Do not set both `CODEX_EMAIL_USE_TLS` and `CODEX_EMAIL_USE_SSL` to `true`. ### 2) Add instruction in project AGENTS.md For example, add this instruction to AGENTS.md: > Use skill email-notify to notify users when each agent run is finished or when any notifications would be sent to users. ## Workflow ### 1) Provide a project name source (optional) - To override the folder name, define a project name in `AGENTS.md` using one of: - YAML frontmatter: `project_name: My Project` (or `name:`) - A plain line: `Project Name: My Project` - If no name is found, the script uses the project folder name. ### 2) Send the notification at task completion - Generate a short task title (3-8 words). - Pick an execution status: `success`, `failed`, `partial`, `blocked`, etc. - Write a brief result summary; avoid secrets. Run: ```bash python3 ~/.codex/skills/email-notify/scripts/send_email_notification.py \ --task-title "..." \ --status "success" \ --summary "..." \ --project-name "..." ``` ## Resources - `scripts/send_email_notification.py`: Send the email notification and resolve the project name.
Related Skills
email-template-generator
Email Template Generator - Auto-activating skill for Business Automation. Triggers on: email template generator, email template generator Part of the Business Automation skill category.
email-parser
Email Parser - Auto-activating skill for Business Automation. Triggers on: email parser, email parser Part of the Business Automation skill category.
email-drafting
Draft email replies for Gonto's Gmail accounts (m@gon.to, gonto@hypergrowthpartners.com). Handles intro acceptances, scheduling intent, thanks/ack, and positive short replies. Use when user asks to draft or reply to an email, or when Gmail webhook triggers arrive for auto-draft classification. Draft-only mode — never sends automatically.
recipe-share-doc-and-notify
Share a Google Docs document with edit access and email collaborators the link.
recipe-save-email-to-doc
Save a Gmail message body into a Google Doc for archival or reference.
recipe-save-email-attachments
Find Gmail messages with attachments and save them to a Google Drive folder.
recipe-label-and-archive-emails
Apply Gmail labels to matching messages and archive them to keep your inbox clean.
recipe-forward-labeled-emails
Find Gmail messages with a specific label and forward them to another address.
recipe-email-drive-link
Share a Google Drive file and email the link with a message to recipients.
recipe-draft-email-from-doc
Read content from a Google Doc and use it as the body of a Gmail message.
gws-workflow-email-to-task
Google Workflow: Convert a Gmail message into a Google Tasks entry.
Himalaya Email CLI
Himalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends.