How do I install the Sc Resend skill?

Run npx skillmds@latest add rahmanef63/sc-resend in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sc Resend safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sc Resend?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sc Resend free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sc Resend?

rahmanef63 (@rahmanef63) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sc Resend by rahmanef63 — Agent Skill

Name: Sc Resend
Author: rahmanef63

Sc Resend

(STUB / NOT IMPLEMENTED YET) Transactional email via Resend — verify sender domain DNS (DKIM/SPF/DMARC), create API keys, send template-based emails. Pairs with sc-cf or lib/hostinger.js for the DNS record creation step.

rahmanef63 1bf1cec 2 files · 3.1 KB Updated Sep 17, 2026

File contents

/sc-resend — Resend (STUB)

Status: boilerplate only.

Scope when implemented

Domain verification: register a sending domain with Resend, fetch the DKIM/SPF/DMARC records it requires, then create them via sc-cf or lib/hostinger.js automatically — no manual DNS copy-paste.
API key rotation per project, scoped to the verified domain.
Audience creation for broadcast lists (optional).
Smoke send to a verified recipient to confirm DNS propagation.

Sender identity policy

Sender identity is project configuration, not repository-global policy. Use one explicitly verified Resend domain/account selected by the user and keep the visible project name separate from the sender address:

From: <Project Name> <transactional@example.com>
Reply-To: <optional monitored mailbox>

Do not infer a sender address from the application hostname. A project hosted at app.example.com may legitimately send from a different verified domain. Keep the project-local contract explicit:

EMAIL_FROM_ADDRESS=transactional@example.com
EMAIL_PROJECT_NAME=<Project Name>
EMAIL_PROJECT_TAG=<project-slug>
EMAIL_REPLY_TO=

Framework adapters may map these values into native variables, but the selected project configuration remains the source of truth. Never bake another project's domain, sender, or display name into this skill.

Env vars

Var	Purpose
`RESEND_API_KEY`	`re_...` server key
`RESEND_FROM_DOMAIN`	The verified sending domain

Suggested file layout

sc-resend/
├── SKILL.md
└── scripts/
    ├── verify-domain.js   # register + auto-create DNS records via sc-cf / hostinger
    ├── api-key.js         # create/rotate scoped API key
    ├── audiences.js       # CRUD audience (optional)
    └── smoke-send.js      # send a test email to confirm

Implementation notes

API base: https://api.resend.com
Auth: Authorization: Bearer <RESEND_API_KEY>
Domain verify response gives 3 records [{ name, type, value }] — feed those into the DNS module via configureDns().
DMARC: Resend recommends v=DMARC1; p=none; initially, tighten to p=quarantine once SPF/DKIM are confirmed in DNS for 24h.

---name: sc-resenddescription: (STUB / NOT IMPLEMENTED YET) Transactional email via Resend — verify sender domain DNS (DKIM/SPF/DMARC), create API keys, send template-based emails. Pairs with sc-cf or lib/hostinger.js for the DNS record creation step.---# /sc-resend — Resend (STUB)> **Status:** boilerplate only.## Scope when implemented- **Domain verification**: register a sending domain with Resend, fetch the DKIM/SPF/DMARC records it requires, then create them via `sc-cf` or `lib/hostinger.js` automatically — no manual DNS copy-paste.- **API key** rotation per project, scoped to the verified domain.- **Audience** creation for broadcast lists (optional).- **Smoke send** to a verified recipient to confirm DNS propagation.## Sender identity policySender identity is project configuration, not repository-global policy. Use one explicitlyverified Resend domain/account selected by the user and keep the visible project nameseparate from the sender address:```textFrom: <Project Name> <transactional@example.com>Reply-To: <optional monitored mailbox>```Do not infer a sender address from the application hostname. A project hosted at`app.example.com` may legitimately send from a different verified domain. Keep theproject-local contract explicit:```textEMAIL_FROM_ADDRESS=transactional@example.comEMAIL_PROJECT_NAME=<Project Name>EMAIL_PROJECT_TAG=<project-slug>EMAIL_REPLY_TO=```Framework adapters may map these values into native variables, but the selected projectconfiguration remains the source of truth. Never bake another project's domain, sender,or display name into this skill.## Env vars| Var | Purpose ||---|---|| `RESEND_API_KEY` | `re_...` server key || `RESEND_FROM_DOMAIN` | The verified sending domain |## Suggested file layout```sc-resend/├── SKILL.md└── scripts/ ├── verify-domain.js # register + auto-create DNS records via sc-cf / hostinger ├── api-key.js # create/rotate scoped API key ├── audiences.js # CRUD audience (optional) └── smoke-send.js # send a test email to confirm```## Implementation notes- API base: `https://api.resend.com`- Auth: `Authorization: Bearer <RESEND_API_KEY>`- Domain verify response gives 3 records `[{ name, type, value }]` — feed those into the DNS module via `configureDns()`.- DMARC: Resend recommends `v=DMARC1; p=none;` initially, tighten to `p=quarantine` once SPF/DKIM are confirmed in DNS for 24h.

Frequently asked questions