templates

Manage Resend email templates via API with CRUD and alias operations.

Updated Sep 22, 2025
One-click install
npx skills add https://github.com/Davidenk0v/juan-carlos-fontaneria --skill templates-davidenk0v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: templates
Source: https://github.com/Davidenk0v/juan-carlos-fontaneria/tree/main/.agents/skills/resend/templates
Command: npx skills add https://github.com/Davidenk0v/juan-carlos-fontaneria --skill templates-davidenk0v

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires resend, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation, updating, publishing, and deletion of email templates within the Resend platform, enabling programmatic control over reusable email structures.

Core Features & Use Cases

  • Template Lifecycle Management: Create, publish, update, and delete email templates via the Resend API.
  • Alias Management: Use stable, human-readable aliases for referencing templates instead of auto-generated IDs.
  • Variable Handling: Define and manage template variables with support for fallback values.
  • Use Case: Automatically create a new "welcome" email template with a personalized greeting variable when a new user signs up for your service.

Quick Start

Use the templates skill to create a new draft template named 'welcome-email' with the HTML content '<h1>Welcome!</h1>'.

Frequently Asked Questions about templates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Resend email templates programmatically through API calls?

You can manage Resend email templates programmatically by using API interactions to perform CRUD operations, publish templates, and handle template variable substitution for automated email workflows.

What's the best way to automate Resend email template creation when a new user signs up?

Automating Resend email template creation involves defining a reusable template with personalized variables, then triggering its creation and publishing via API calls to ensure consistent welcome email delivery.

Can I use stable aliases instead of auto-generated IDs to reference Resend email templates?

Yes, you can use stable, human-readable aliases to reference Resend email templates instead of auto-generated IDs, simplifying template management and ensuring consistent programmatic access across your workflows.

How do I define and handle variables with fallback values in Resend email templates?

Defining variables with fallback values in Resend email templates involves specifying substitution parameters during template creation, ensuring consistent email rendering even when dynamic data is missing.

What are the limitations of using API interactions for Resend email template lifecycle management?

Limitations of API-based Resend email template lifecycle management include dependency on the Resend API availability and the need to handle template publishing and variable substitution logic within your own application code.

Do I need a Resend dependency to programmatically publish and delete email templates?

Yes, you need the Resend dependency to programmatically interact with the Resend API, enabling you to create, publish, update, and delete email templates within your development environment.