add-email-template

Create transactional email templates with C# models and Fluid Liquid files.

230|29|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/fpindej/netrock --skill add-email-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-email-template
Source: https://github.com/fpindej/netrock/tree/main/.claude/skills/add-email-template
Command: npx skills add https://github.com/fpindej/netrock --skill add-email-template

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of adding new transactional email templates to an application, ensuring consistency and reducing boilerplate code.

Core Features & Use Cases

  • Template Creation: Generates the necessary C# model, Liquid template files (HTML, subject, plain text), and registration code for new email templates.
  • Convention Enforcement: Adheres to established naming conventions and best practices for email templating.
  • Use Case: Quickly add a new "password reset" email template by defining its model and content, integrating seamlessly with the existing email sending service.

Quick Start

Add a new email template named 'password-reset' with a 'token' variable.

Frequently Asked Questions about add-email-template

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

FAQPage Schema
How do I add a transactional email template using Liquid in C#?

To add a transactional email template using Liquid in C#, generate a C# model record, HTML body fragment, subject line, and plain text version, then register the model type with your templated email sender. This ensures consistent, boilerplate-free template creation.

What is the Fluid templating engine used for in backend email templates?

The Fluid templating engine renders Liquid syntax for backend email templates, allowing you to define dynamic HTML bodies, subject lines, and plain text versions using C# model records for transactional emails.

Can I use this approach to generate both HTML and plain text email versions?

Yes, you can generate both HTML and plain text email versions. The process creates Liquid template files for HTML body fragments, subject lines, and plain text, alongside the corresponding C# model for seamless integration.

What's the best way to structure a C# model for a transactional email template?

The best way to structure a C# model for a transactional email template is to create a dedicated C# record representing the template's variables, such as a token for password resets, and register it with your existing email sending service.

Do I need an existing email sending service to integrate Liquid templates?

Yes, you need an existing email sending service. The process integrates by registering C# model types and utilizing a templated email sender to dispatch the generated Liquid email templates.

Why does my transactional email template need registration code?

Your transactional email template needs registration code to integrate with the existing email sending service. Registering C# model types allows the templated email sender to correctly map Liquid template variables to your backend data.