What problem does it solve? Adding transactional email to a static or Firebase-hosted site requires wiring up a third-party email API, storing the API key securely, granting the right IAM permissions, and scaffolding a Cloud Function — a multi-step process that is easy to get wrong. This Skill walks through the entire setup so the Resend API key never touches the repo and the function deploys correctly the first time. ## Core Features & Use Cases - Secret Management: Stores the Resend API key in Firebase Secret Manager and grants the compute service account the secretAccessor role, keeping credentials out of source control. - Two Trigger Variants: Scaffolds either a Firestore-triggered function (fires when a document is created, with optional welcome email via Resend template) or an HTTP callable function accepting to, subject, html, and text. - Next.js Track: For Next.js sites, uses a route handler with the key as a RUNTIME-only Secret Manager reference in apphosting.yaml instead of a functions directory. - Use Case: A marketing site has a signup form writing to a Firestore collection. Run this Skill to deploy a function that emails the admin on every new submission and optionally sends the submitter a welcome email. ## Quick Start Set up Resend email sending for my site with a Firestore trigger on the signups collection that notifies alerts@example.com.
