Resend

What it does

The entry file includes sending and receiving examples, then points domain, contact, broadcast, webhook and automation tasks to specific references. It stresses idempotency for retries and raw-payload webhook verification. It also notes that an inbound event does not necessarily contain the complete message body.

Best for

Applications integrating Resend’s SDK or API rather than operating the service manually through a dashboard.

Tradeoffs and requirements

API access can transmit email and modify account resources. Provider limits, billing and permission scope need independent review. Webhook authenticity does not make an email’s content trustworthy, and successful acceptance is different from delivery to a recipient’s inbox.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code; this catalog never runs it.

npx skills add https://github.com/resend/resend-skills/tree/b2ae7b1798b70134faf679f35fc05b4331462988/skills/resend --skill resend

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Credential Reference — review the source context.
• Network Access — review the source context.
• Shell Or Package Install — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

85/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

42/100

42

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Choose one message flow and implement it against a controlled test setup. Store credentials outside source code, verify webhook signatures and preserve idempotency across network retries.

How to judge the result

Test duplicate events, invalid signatures, partial batch failures and missing inbound bodies. Inspect real provider results and suppression handling, and verify that logging contains enough diagnostics without storing unnecessary recipient content or authentication secrets.