composing-emails

Compose standardized HTML email content with validated recipient addresses.

97|5|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/friday-platform/friday-studio --skill composing-emails
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: composing-emails
Source: https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/composing-emails
Command: npx skills add https://github.com/friday-platform/friday-studio --skill composing-emails

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of HTML emails that render incorrectly across different email clients, ensuring your messages are professional, consistent, and display exactly as intended for every recipient.

Core Features & Use Cases

  • Standardized Block Structure: Enforces a simple, widely supported block model (only paragraph, heading, and link blocks) to avoid rendering errors from unsupported HTML elements like lists, tables, or markdown syntax.
  • Tone & Formatting Rules: Provides clear guidelines for professional, clear email copy, including best practices for subject lines, emphasis, and data formatting.
  • Safe Recipient Handling: Includes guardrails to ensure recipient addresses are pulled from validated signal payloads, preventing misdirected or fabricated email addresses.
  • Use Case: For example, use this Skill to draft a customer order confirmation email that displays correctly in Gmail, Outlook, and mobile email clients, while ensuring it is sent only to the verified customer address from your order system.

Quick Start

Use the composing-emails skill to draft a professional shipping notification email for a customer who purchased a $79.99 wireless charger, sent to their verified email address from the order payload.

Frequently Asked Questions about composing-emails

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

FAQPage Schema
How do I write HTML emails that render correctly across all email clients?

To ensure HTML emails render correctly across all clients, use a standardized block structure limited to paragraph, heading, and link blocks, avoiding unsupported elements like tables and lists that cause display failures.

Why does my transactional email formatting break in Gmail and Outlook?

Transactional email formatting breaks in clients like Gmail and Outlook due to unsupported HTML elements and markdown syntax; restricting content to simple paragraph, heading, and link blocks prevents these rendering errors.

What is the best way to validate recipient addresses for customer notification emails?

The best way to validate recipient addresses for customer notification emails is to pull them directly from validated signal payloads, ensuring addresses are verified system outputs rather than fabricated or misdirected inputs.

Can I use markdown syntax when composing professional marketing outreach emails?

You cannot use markdown syntax when composing marketing outreach emails; markdown causes rendering failures across different email clients, so you must use strictly formatted HTML paragraph, heading, and link blocks instead.

What HTML elements should I avoid to prevent cross-client email rendering failures?

To prevent cross-client email rendering failures, avoid using unsupported HTML elements like lists, tables, and markdown syntax, relying exclusively on a simple block model of paragraphs, headings, and links.