mailgun sender

Send emails via Mailgun API. Use when the user needs to send emails programmatically, such as newsletters, notifications, alerts, or automated reports. Requi...

Security Scan

The skill is coherent with its stated purpose (sending Mailgun emails); required secrets are Mailgun-specific and the included script calls only Mailgun's API and curl, though there are minor documentation/metadata inconsistencies to note.

Purpose & Capability

Name, description, and implementation align: the script sends email via Mailgun's HTTP API and requires MAILGUN_API_KEY and MAILGUN_DOMAIN plus optional MAILGUN_FROM/MAILGUN_DEFAULT_TO. No unrelated services, binaries, or capabilities are requested.

Instruction Scope

Runtime instructions are narrowly scoped to sending email. The script uses curl to call https://api.mailgun.net only. One minor mismatch: SKILL.md's Prerequisites instruct configuring env vars in shell RC files, while the script will alternatively source ~/.config/mailgun/credentials — the README doesn't initially document that file path except in an error message.

Install Mechanism

No install spec (instruction-only) and no downloads or package installs. The script is included in the skill bundle and relies on curl, which is a typical, low-risk dependency.

Credentials

Requested environment variables are proportional and Mailgun-specific. However, registry metadata lists 'Required env vars: none' while SKILL.md and the script require MAILGUN_API_KEY and MAILGUN_DOMAIN (and recommend MAILGUN_FROM / MAILGUN_DEFAULT_TO). This metadata omission is an inconsistency worth correcting. The script also reads ~/.config/mailgun/credentials if env vars are absent — this is reasonable but should be documented clearly.

Persistence & Privilege

Skill does not request persistent system privileges, does not set always:true, and does not modify other skills or system-wide settings. Agent autonomous invocation is allowed (default) which is normal for skills.

Assessment

This skill appears to do what it says (send Mailgun emails), but check these before installing: - Confirm the skill source/trust (source is 'unknown' but homepage points to a repo). Only provide your MAILGUN_API_KEY to trusted skills. - Fix the metadata/documentation mismatch: registry metadata claims no required envs but SKILL.md and the script do require MAILGUN_API_KEY and MAILGUN_DOMAIN. - Note the script will also try ~/.config/mailgun/credentials if env vars are missing—if you use that file, store it with restrictive permissions (chmod 600) and don't commit it to version control. - Review the included send_email.sh yourself; it only posts to api.mailgun.net via curl and prints the response. If you plan to use this skill automatically, monitor your Mailgun usage to avoid accidental mass sends. - If you have stricter security needs, consider creating a Mailgun API key with limited send scope and rotating keys periodically.

Mailgun Email Sender

Send emails programmatically using Mailgun's HTTP API.

Prerequisites

Configure the following environment variables in ~/.zshrc or ~/.bash_profile:

export MAILGUN_API_KEY="key-xxxxx"      # Your Mailgun private API key
export MAILGUN_DOMAIN="mg.yourdomain.com"  # Your Mailgun domain
export MAILGUN_FROM="Sender <[e-mail]>"  # Default sender
export MAILGUN_DEFAULT_TO="[e-mail]"  # Default recipient (optional)

Then reload your shell configuration:

source ~/.zshrc

Usage

Send a simple email

mailgun/scripts/send_email.sh "Subject" "Email body text"

Send to a specific recipient

mailgun/scripts/send_email.sh "Newsletter" "Content here" "[e-mail]"

Send with custom sender

mailgun/scripts/send_email.sh "Alert" "System down" "[e-mail]" "[e-mail]"

Features

• Simple command-line interface
• Uses environment variables for configuration
• Supports custom sender and recipient
• Returns success/error status codes
• Works with HTML content (pass HTML in body parameter)

Common Use Cases

• Daily/weekly newsletters
• System alerts and notifications
• Automated reports
• Confirmation emails
• Scheduled reminders

Troubleshooting

Error: MAILGUN_API_KEY and MAILGUN_DOMAIN must be set → Configure environment variables as shown in Prerequisites

Error: 401 Unauthorized → Check that your API key is correct and active

Error: 404 Not Found → Verify your MAILGUN_DOMAIN is correct

References

• Mailgun Documentation: https://documentation.mailgun.com/
• API Reference: See references/api.md