send-email

**Quick judgement:** A focused and practical SMTP email-sending skill that integrates smoothly with OpenClaw via environment-injected credentials. It is mature enough for typical notification and reporting tasks, but carries the usual risks of a powerful outbound communication channel. **What it does well:** - Sends emails via standard SMTP with support for SSL/TLS and major providers (163, Gmail, QQ, etc.). - Simple CLI interface (`python3 ... send_email.py "recipient" "Subject" "Body" ["/path/to/file"]`) that fits well into automated workflows. - Handles attachments through an additional command-line argument. - Uses OpenClaw env injection for credentials, avoiding direct file reads of secret config. **Risks / considerations:** - Outbound email is a strong data exfiltration vector: if an agent is compromised or misused, it can leak sensitive data to arbitrary recipients. - Depends entirely on correct SMTP configuration in `~/.openclaw/openclaw.json`; misconfiguration leads to auth/connection failures. - Error handling and edge-case behavior (rate limits, large attachments, non-ASCII content) are not visible from the description and may limit robustness. **Recommended scenarios:** - Automated alerts, status updates, or completion notifications from long-running tasks. - Scheduled or on-demand report delivery (e.g., PDFs, CSVs) to known internal recipients. - Internal tooling where an orchestrated OpenClaw agent needs a straightforward way to send emails, and where email recipients and usage patterns are tightly controlled. - Not recommended for high-volume marketing mail, complex templating, or scenarios requiring strict data-loss-prevention controls unless additional safeguards are in place.