Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mailgun-setup
Set up and send emails via a user-provided Mailgun account (BYO email provider)
Passed 13 of 18 test cases with the skill, and 5 of 18 without it.
and 9 more in the full report
11 fixed5 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
If the detected active domain is 'company.org' and no custom sender address was requested, what default email address should be assigned for outbound mail?
| Checked | Without skill | With skill |
|---|---|---|
| Uses [email protected] as the default sender address | Missed | Passed |
The instructions your model reads when the skill loads.
Send emails through the user's own Mailgun account. The user provides their Mailgun API key and domain, and you send via their infrastructure.
Before starting, check whether Mailgun is already configured:
bun skills/mailgun-setup/scripts/check-config.ts
The script outputs JSON: { "configured": boolean, "hasApiKey": boolean, "hasWebhookKey": boolean, "details": string }.
configured is true — Mailgun is already set up. Offer to verify the connection or reconfigure.configured is false — continue to Step 1.Run the store script to securely collect the API key:
bun skills/mailgun-setup/scripts/store-api-key.ts
The script opens a secure credential prompt, stores the key, and exits. If it exits 0, the key is stored. Exit code 130 means the user cancelled the prompt — nothing was stored; that's a valid choice, not an error, so ask whether they'd like to try again rather than treating it as a failure. Any other non-zero exit is a real failure. Never ask for the key in chat.
Note: Mailgun uses HTTP Basic Auth with username api and the API key as the password. The credential proxy cannot construct Basic Auth headers automatically. Instead, use curl -u "api:$KEY" in bash commands — retrieve the key from the vault at runtime. See the sending examples below.
After storing the API key, automatically detect the user's domain — don't ask them for it. Retrieve the API key from the vault and call the Mailgun Domains API:
curl -s --user "api:$MAILGUN_API_KEY" \
https://api.mailgun.net/v4/domains?state=active
test cases passed, vs 5 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.