Simple SMTP Mailer
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill is aligned with sending email, but it gives the agent broad ability to send from a local SMTP account using unsafe shell-style command templates and a hard-coded credential path.
Only install this if you are comfortable giving the agent the ability to send email through your configured SMTP account. Fix the hard-coded config path, keep the msmtp credential file locked down, and require a final confirmation of the exact recipient and message before sending.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could send email from the configured account too readily, including to unintended recipients or with unintended content.
The assistant guide authorizes direct command execution to send email, but does not require explicit user confirmation of the recipient, subject, sender, and body before sending from the user's SMTP account.
Use the exec tool to run msmtp commands
Require explicit user confirmation with the exact recipient, subject, sender, and body before any msmtp send, and document that the skill should not send messages proactively.
A malicious or accidental email field could potentially cause the agent to run unintended shell commands on the user's machine.
The documented execution pattern places user-controlled subject, body, and recipient values into a shell command template. If substituted naively, shell metacharacters or command substitutions in those fields could execute unintended local commands.
echo -e "Subject: <SUBJECT>\n\n<BODY>" | msmtp --file=/Users/yugaoxiang/.msmtp/config <RECIPIENT>
Avoid shell interpolation for email content and recipients. Use safe argument passing, quote recipients safely, and feed message content through a controlled file or stdin mechanism without evaluating it in a shell.
The agent may fail or, on a matching system, send mail using an unexpected local account configuration.
The assistant guide uses a hard-coded personal home-directory config path instead of the current user's ~/.msmtp/config, which could attempt to use the wrong local SMTP credential file if present.
msmtp --file=/Users/yugaoxiang/.msmtp/config <RECIPIENT>
Replace the hard-coded path with ~/.msmtp/config or $HOME/.msmtp/config, declare the credential/config requirement clearly, and ensure the user chooses which SMTP account is used.