# Send Completion Emails from Codex

Long-running agent tasks can finish when users are away from the terminal. This skill sends a concise SMTP email with device, project, status, and summary details.

## Install

```bash
npx skillstore add caopulan/email-notify
```

## Metadata

- - Slug: caopulan-email-notify
- - Version: 1.0.0
- - Author: caopulan
- - GitHub username: caopulan
- - License: MIT
- - Repository: https://github.com/caopulan/Notification-Skill/tree/main/email-notify
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: scripts, network, filesystem, env\_access, external\_commands
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/caopulan-email-notify
- - Manifest: https://skillstore.pages.dev/api/skills/caopulan-email-notify/manifest

## Capabilities

- Sends SMTP email notifications after a task completes.
- Includes device name, project name, status, and summary in the email body.
- Reads the project name from AGENTS.md, a command option, or the current folder.
- Supports multiple recipients separated by commas or semicolons.
- Supports authenticated SMTP, unauthenticated SMTP, STARTTLS, SMTP over SSL, timeouts, and dry runs.

## Use Cases

- Notify After Long Builds: Send a completion email when Codex finishes tests, builds, or migrations that take several minutes.
- Report Agent Run Results: Email a short status and summary after an agent completes a requested code change.
- Track Remote Workflows: Receive task completion alerts from a remote machine without staying connected to the terminal.

## Prompt Templates

### Basic Completion Email

```
When this task is finished, use email-notify to send me a success or failure email with a short summary.
```

### Custom Status Message

```
After the run, send an email notification titled "Dependency update" with the final status and a concise summary.
```

### Dry Run SMTP Check

```
Use email-notify in dry-run mode to verify the SMTP host, recipients, subject, and body before sending a real notification.
```

### Advanced Workflow Alert

```
When the deployment checks complete, send an email for project "Billing API" with status partial if any check fails, and summarize the next required action.
```

## Limitations

- Requires a working SMTP server and correct environment variables.
- Does not remove secrets from task summaries automatically.
- Does not provide delivery tracking, retries, or queueing.
- Stores SMTP settings in the user environment unless the user chooses another secret workflow.

## Best Practices

- Use app-specific SMTP passwords and rotate them regularly.
- Keep summaries short and exclude secrets, tokens, customer data, and private logs.
- Test configuration with dry-run before sending real notifications.

## Anti Patterns

- Do not include credentials or private file contents in the summary.
- Do not send notifications to broad mailing lists without review.
- Do not enable both STARTTLS and SMTP over SSL at the same time.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T20:18:54.474\+00:00
- - Summary: Static findings for network, environment access, filesystem references, and documented commands are mostly expected for an SMTP notification skill. No prompt injection or malicious intent was found, but the skill can email task summaries and uses SMTP credentials from environment variables, so users need a clear data disclosure warning.

## Stats

- - Views: 207
- - Downloads: 6
- - Favorites: 1
- - Popularity score: 0