add-resend
Add Resend (email) channel integration via Chat SDK.
pinned to #a30547fupdated 3 months ago
Ask your AI client: “install skills/add-resend”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/add-resendmetahub onboarded this repo on the author's behalf.
If you own github.com/nanocoai/nanoclaw on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
30,187
Last commit
3 months ago
Latest release
published
- #ai-agents
- #ai-assistant
- #claude-code
- #claude-skills
- #openclaw
About this skill
Pulled from SKILL.md at publish time.
Connect NanoClaw to email via Resend for async email conversations.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.a30547f· 3 months ago
Documentation
4 passed1 warningDescription qualitywarn
8 words · 52 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
15,207 chars · 13 sections · 7 code blocks
Tags / topics declared
5 total — ai-agents, ai-assistant, claude-code, claude-skills, openclaw
README has usage / example sections
found: Quick Start · Usage
Homepage / docs URL declared
https://nanoclaw.dev
Release history
1- releasecurrenta30547fwarn3 months ago
Contents
Connect NanoClaw to email via Resend for async email conversations.
Install
NanoClaw doesn't ship channels in trunk. This skill copies the Resend adapter in from the channels branch.
Pre-flight (idempotent)
Skip to Credentials if all of these are already in place:
src/channels/resend.tsexistssrc/channels/resend-registration.test.tsexistssrc/channels/index.tscontainsimport './resend.js';@resend/chat-sdk-adapteris listed inpackage.jsondependencies
Otherwise continue. Every step below is safe to re-run.
1. Fetch the channels branch
git fetch origin channels
2. Copy the adapter and its registration test
git show origin/channels:src/channels/resend.ts > src/channels/resend.ts
git show origin/channels:src/channels/resend-registration.test.ts > src/channels/resend-registration.test.ts
3. Append the self-registration import
Append to src/channels/index.ts (skip if the line is already present):
import './resend.js';
4. Install the adapter package (pinned)
pnpm install @resend/[email protected]
5. Build and validate
pnpm run build
pnpm exec vitest run src/channels/resend-registration.test.ts
Both must be clean before proceeding. resend-registration.test.ts is the one integration test: it imports the real channel barrel and asserts the registry contains resend. It goes red if the import './resend.js'; line is deleted or drifts, if the barrel fails to evaluate, or if @resend/chat-sdk-adapter isn't installed (the import throws) — so it also implicitly verifies the dependency from step 4. The adapter also calls core's createChatSdkBridge(...); that typed core-API consumption is guarded by pnpm run build.
Credentials
- Go to resend.com and create an account.
- Add and verify your sending domain.
- Go to API Keys and create a new key.
- Set up a webhook:
- Go to Webhooks > Add webhook.
- URL:
https://your-domain/webhook/resend. - Events: select email.received.
- Copy the signing secret.
Configure environment
Add to .env:
RESEND_API_KEY=re_...
[email protected]
RESEND_FROM_NAME=NanoClaw
RESEND_WEBHOOK_SECRET=your-webhook-secret
Sync to container: mkdir -p data/env && cp .env data/env/env
Next Steps
If you're in the middle of /setup, return to the setup flow now.
Otherwise, run /manage-channels to wire this channel to an agent group.
Channel Info
- type:
resend - terminology: Resend handles email. Each email thread (identified by subject/In-Reply-To headers) is a separate conversation. The "from address" is the bot's identity.
- how-to-find-id: The platform ID is the from email address (e.g.
[email protected]). Each sender's email thread becomes its own conversation. - supports-threads: yes (via email threading headers -- replies to the same thread stay together)
- typical-use: Async communication -- email conversations with longer response expectations
- default-isolation: Same agent group if you want your agent to handle email alongside other channels. Separate agent group if email contains sensitive correspondence that shouldn't be accessible from other channels.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/add-resend