email_composer

Generates professional business emails using structured templates and a three-phase drafting workflow.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill email-composer-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email_composer
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/email_composer
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill email-composer-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, professional business emails is time-consuming and error-prone—vague subject lines, buried requests, and missing calls to action lead to miscommunication and ignored messages. ## Core Features & Use Cases - Ready-to-Use Templates: Pre-built structures for meeting requests, follow-ups, and status updates with proper subject lines and formatting. - Three-Phase Workflow: A Draft → Refine → Finalize process covering objective setting, BLUF (Bottom Line Up Front) structure, tone checks, and proofreading. - Best Practices Checklist: Do/Don't guidance and verification checkpoints ensuring each email has a clear subject, visible main message, and explicit next step. - Use Case: You need to send a weekly project status update to stakeholders. Use the Status Update template, apply the BLUF principle to lead with key results, and run the finalization checklist to confirm a clear call to action before sending. ## Quick Start Write a professional follow-up email to a client about last week's proposal using the email composer guidelines.

Frequently Asked Questions about email_composer

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

FAQPage Schema
How do I write a professional business email?

Start with a clear subject line under five words, open with context, state your main message up front using the BLUF principle, and close with a specific call to action. Use bullet points instead of long paragraphs and proofread before sending.

How do I write a follow-up email that gets a response?

Reference the original conversation and date in the subject line, briefly restate the context, then ask one specific question or propose a clear next step. Keep it short and polite but direct so the recipient knows exactly what to do.

What should a project status update email include?

A status update email should include completed items, work in progress, blockers, and next steps, each as a short bulleted section. Use a subject line with the project name and date so recipients can track updates over time.

What are common business email mistakes to avoid?

Common mistakes include vague subject lines like "Quick question", combining multiple unrelated requests in one email, burying the main point at the end, and forgetting attachments. The checklist phase catches these before sending.

When should I not use a formal email template?

Templates are less suitable for sensitive conversations like delivering bad news, negotiating conflicts, or highly personal messages where rigid structure can feel impersonal. In those cases, adapt the tone guidance but write more freely.