ClawHub

Mailgun

v1.0.0

Mailgun API integration with managed OAuth. Transactional email service for sending, receiving, and tracking emails. Use this skill when users want to send emails, manage domains, routes, templates, mailing lists, or suppressions in Mailgun. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).

⭐ 3· 730·0 current·0 all-time
by@byungkyu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill advertises Mailgun integration but consistently instructs clients to use Maton endpoints (gateway.maton.ai and ctrl.maton.ai) and requires only MATON_API_KEY. Requiring a Maton API key is coherent with a managed-OAuth gateway approach.
ℹ
Instruction Scope
Runtime instructions are limited to HTTP calls to Maton gateway/control endpoints and use only the declared MATON_API_KEY. They do not instruct reading unrelated files or other environment variables. Note: the gateway/proxy endpoints are operated by Maton (not api.mailgun.net directly), so you are delegating Mailgun OAuth flows and API calls to that third party.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files to execute on install; this is the lowest-risk installation model.
ℹ
Credentials
Only MATON_API_KEY is required, which is proportional to a managed gateway design. However, that single key grants Maton-level access which can act on behalf of your Mailgun account via the gateway, so trust in the Maton service and key scope matters.
✓
Persistence & Privilege
The skill is not always-enabled and does not request system-wide persistence. disable-model-invocation is false (normal), meaning the agent can call the skill autonomously — expected for skills but consider runtime behavior with any credential you provide.
Assessment
This skill proxies Mailgun through Maton and requires a MATON_API_KEY. Before installing or enabling it: 1) Confirm you trust maton.ai/maton services (they will see and act on Mailgun data and OAuth). 2) Use least-privilege credentials or a dedicated Maton API key tied to a non-production Mailgun account if possible. 3) Review Maton's privacy/security docs and the ctrl.maton.ai/gateway.maton.ai URLs referenced in the instructions. 4) Remember the agent can invoke the skill autonomously — it could send API requests (including sending mail) using your key without an extra prompt. 5) Rotate or revoke the key if you stop using the skill or suspect misuse.

Like a lobster shell, security has layers — review code before you run it.

latestvk97700xdwbdkwbxwejtzyppkhn810c3h

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🧠 Clawdis
EnvMATON_API_KEY

Comments