Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Send emails via Resend API from any verified domain. Use when sending emails, notifications, or automated messages. Supports HTML and plain text. Default voi...
Send emails via Resend API from any verified domain. Use when sending emails, notifications, or automated messages. Supports HTML and plain text. Default voi...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Send emails from any Resend-verified domain using the Resend API.
# Send simple email bash skills/resend-email/scripts/send.sh \ --to "recipient@example.com" \ --subject "Subject Line" \ --body "Email body text" # With custom from address bash skills/resend-email/scripts/send.sh \ --to "recipient@example.com" \ --from "you@yourdomain.com" \ --subject "Subject" \ --body "Body"
curl -X POST 'https://api.resend.com/emails' \ -H "Authorization: Bearer $(cat ~/.config/resend/credentials.json | jq -r .api_key)" \ -H "Content-Type: application/json" \ -d '{ "from": "noreply@yourdomain.com", "to": ["recipient@example.com"], "subject": "Subject", "text": "Plain text body" }'
Credentials: ~/.config/resend/credentials.json Domain: any Resend-verified domain (configured in your Resend account) Default from: set in credentials.json (e.g., noreply@yourdomain.com)
Use this when you want Resend inbound emails to trigger Clawdbot automatically.
{ hooks: { enabled: true, token: "<shared-secret>", path: "/hooks", transformsDir: "~/.clawdbot/hooks", mappings: [ { id: "resend", match: { path: "resend" }, // relative to /hooks (no leading slash) action: "agent", deliver: true, channel: "telegram", transform: { module: "resend-inbound.js", export: "transform" } } ] } } Important: match.path is relative to /hooks (e.g., /hooks/resend β resend).
If your gateway is local-only, expose it via Funnel: /Applications/Tailscale.app/Contents/MacOS/Tailscale funnel --bg 18789 MagicDNS + HTTPS certs must be enabled in your tailnet for TLS to work.
In Resend β Webhooks: URL: https://<your-tailnet-host>.ts.net/hooks/resend?token=<shared-secret> Event: email.received Resend cannot set custom headers, so use ?token=.
Resend webhooks do not include body text. Use the receiving API: GET https://api.resend.com/emails/receiving/:id (See resend-inbound.js for an example transform that fetches the body.)
See references/voice-bureaucrat.md for the default email tone. Key traits: Warm, patient, endlessly polite Passive voice ("it is recommended thatβ¦") Official jargon ("compliance framework", "pursuant to section 14(b)") Everything framed as "best practices" Bullet points start with "Please note thatβ¦" Ends with "We appreciate your cooperation" Tone: DMV supervisor who smiles while denying your form Γ LinkedIn thought-leader who genuinely believes bureaucracy is beautiful. When drafting emails, apply this voice unless instructed otherwise.
curl -X POST 'https://api.resend.com/emails' \ -H "Authorization: Bearer $RESEND_KEY" \ -H "Content-Type: application/json" \ -d '{ "from": "noreply@yourdomain.com", "to": ["recipient@example.com"], "subject": "Subject", "html": "<h1>Hello</h1><p>HTML content</p>" }'
send.sh preserves line breaks in --body (no literal \n output). Use --html for rich formatting; default is plain text.
Transactional notification: # Order confirmation, welcome email, etc. bash skills/resend-email/scripts/send.sh \ --to "customer@example.com" \ --subject "Your Request Has Been Processed" \ --body "$(cat <<'EOF' Dear Valued Individual, Please note that your recent submission has been received and processed in accordance with standard operating procedures. It should be understood that all requests are handled in the order received, pursuant to our established compliance framework. We appreciate your cooperation in maintaining an orderly process. Warm regards, Clawd Agent Services Division EOF )" Reply to inquiry: Apply bureaucrat voice. Be helpful while maintaining the veneer of official procedure.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.