Agent skill
mailgun
Send emails via Mailgun API. Use when the user needs to send emails programmatically, such as newsletters, notifications, alerts, or automated reports. Requires MAILGUN_API_KEY and MAILGUN_DOMAIN environment variables to be configured.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/mailgun
SKILL.md
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 <[email protected]>" # Default sender
export MAILGUN_DEFAULT_TO="[email protected]" # 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" "[email protected]"
Send with custom sender
mailgun/scripts/send_email.sh "Alert" "System down" "[email protected]" "[email protected]"
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?