email-notify

The email-notify skill is a robust automation utility designed to bridge the gap between autonomous agent task execution and real-time user awareness. By integrating this skill into your agent workflows, you receive timely updates regarding the progress and results of your automated runs directly in your email inbox. This is particularly valuable for long-running scripts, batch processing tasks, or background agents where manual monitoring is impractical. The skill provides a professional reporting format, including the source machine identifier, project context, specific task outcomes, and concise summaries, ensuring that you stay informed about your infrastructure or development operations even when you are away from the terminal. It is built to be lightweight, utilizing standard SMTP protocols for maximum compatibility with both commercial providers like Gmail and private mail servers.

• Automated notifications triggered via CLI commands after agent task cycles.

• Support for multi-device environments using environment variables for custom machine naming.

• Flexible project identification via AGENTS.md YAML frontmatter or automatic directory detection.

• Configurable SMTP settings including authentication, port selection, and encrypted transport layer options like SSL/TLS.

• Highly customizable output fields: task title, execution status (success, failed, blocked, etc.), and result summaries.

• Ensure all required environment variables are set in your shell profile (e.g., ~/.bashrc or ~/.zshrc) including SMTP host, port, user credentials, and recipient email addresses.

• Use the --task-title, --status, and --summary flags during execution to provide meaningful content to your notifications.

• Leverage project resolution logic by including a project_name field in your agent configuration files for consistent reporting.

• Note that this skill is part of a larger notification suite and can be used in tandem with other tools like Bark for multi-channel alerting.

• Always keep your email credentials secure; avoid hardcoding passwords directly in scripts or shared configuration files.