Resend
CommunicationCommonly used with
Skills using Resend (10)
add-resend
Add Resend (email) channel integration via Chat SDK.
email-campaigns
Design, build, and send beautiful HTML email campaigns via Resend. Handles asset hosting (images + GIFs on your own CDN), the pre-built email HTML component library (frost-glass cards, hero image, video blocks with blurred backgrounds, CTA buttons, footer), GIF optimization from MP4 source video, and sending via the Resend API. Use when asked to "create an email", "draft a marketing email", "send a campaign", "make an email sequence", or "build an email with Resend". Proactively suggest when the user mentions sending marketing emails, launching a feature via email, or designing a newsletter.
secrets
Securely request API keys, access tokens, passwords, webhook secrets, or other credentials and write them to a dotenv file without exposing their values to the agent. Use whenever a task needs a credential that the user must supply.
login_auto
基于 Supabase Auth + Resend SMTP 实现通用登录系统，零新依赖。覆盖邮箱密码登录、OAuth(google/github)、邮箱验证码注册、邮箱验证码改密。验证码邮件经 Supabase 自定义 SMTP 接入 Resend 投递。当用户说"login_auto"、"登录实现"、"Supabase登录"、"通用登录"时触发。
send-update-email
Send a readable, version-grouped update email via Resend for a single repo's accumulated commits since the last send — shows the rendered content and waits for confirmation before actually sending.
cold-outreach
Research a prospect, evaluate fit, draft a personalized cold email, preview it to yourself, send it via Resend, and track it in a bounded ledger. Use when the user asks to "research a company/prospect", "check out this lead", "draft a cold email", "send cold outreach", "outreach to this business", "deep dive on this prospect", "add to my prospect list", or "follow up". Config-driven: you set your sender identity, product, and ideal customer in references/config.md — the skill stays generic across industries.
email-broadcasts
Draft, test, and send marketing / product-update email broadcasts to an audience via Resend. Use when the user asks to "send a broadcast", "email blast", "newsletter", "product update email", "announce something to users", "marketing email", "review request", "how many contacts", "email history", or "what have we sent". Config-driven brand + sender; mandatory test send and explicit confirmation before any real send; CAN-SPAM compliant; bounded history.
vibe-design-md
Generates a DESIGN.md file for any website URL or fetches a pre-built one from the awesome-design-md collection (55+ sites). DESIGN.md captures the complete design system of a real product — exact hex/oklch values, font families, spacing scales, shadow formulas, component states, do's and don'ts — in a format vibe-design reads to produce pixel-accurate matching UI. Three modes: (A) fetch a pre-built DESIGN.md from the catalog by site name (instant, exact tokens); (B) generate one from any URL by reading the site's rendered CSS and visual language (~2 min); (C) INGEST a design the user already made — a mockup/screenshot image (PNG/JPG), a prototype HTML/CSS file, or a written description — and extract it into DESIGN.md, so a look designed elsewhere (e.g. in the Claude desktop app) satisfies the pipeline's design gate without redoing it. Output always saved to project root as DESIGN.md. Triggers on "design-md:", "generate a design system for", "extract design tokens from", "make it look like [brand]", "get the
resend-cli
Operate Resend from a coding-agent terminal with the official resend-cli and bundled REST helpers. Use when the agent needs to send, schedule, inspect, forward, or cancel emails; manage inbound email, domains, API keys, contacts, contact properties, segments, topics, broadcasts, templates, webhooks, automations, events, suppression entries, or API logs; diagnose Resend authentication or delivery; invoke resend-cli; or translate a Resend MCP workflow to shell commands. Do not use for application runtime integration through a Resend SDK, continuous monitoring, non-Resend email providers, or Resend MCP server configuration.
secrets
Securely request API keys, access tokens, passwords, webhook secrets, or other credentials from the user and write them to a dotenv file without exposing their values to the agent.
Integration detected automatically from skill content. Some results may be false positives.