email-composer
Use when the user needs professional email drafting, tone adjustment, template creation, or communication strategy for business correspondence. Trigger conditions: draft professional email, adjust email tone, create email template, write cold outreach, compose follow-up, draft escalation email, write apology email, craft meeting request, compose status update, plan email communication strategy.
- Installs
- 78
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pixel-process-ug/superkit-agents --skill email-composer- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads email-composer automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Email Composer
Overview
Draft clear, effective professional emails with appropriate tone, structure, and purpose. This skill covers business correspondence, cold outreach, follow-ups, escalations, apologies, negotiations, internal communications, and stakeholder updates. Includes tone calibration, cultural sensitivity, and templates for common business scenarios.
Apply this skill whenever professional email communication needs to be drafted, refined, or strategized.
Multi-Phase Process
Phase 1: Context Assessment
- Identify the recipient(s) and their relationship to the sender
- Determine the email's primary purpose (inform, request, persuade, respond)
- Assess the appropriate formality level (see tone matrix)
- Consider cultural and organizational norms
- Identify any sensitive topics requiring careful framing
STOP — Do NOT begin drafting without knowing the recipient, purpose, and tone level.
Phase 2: Structure Planning
- Craft a clear, specific subject line
- Plan the opening (context-setting or relationship acknowledgment)
- Organize the body (one idea per paragraph, most important first)
- Define the call to action or next steps
- Choose an appropriate sign-off
STOP — Do NOT draft the full email without a subject line and clear CTA defined.
Phase 3: Drafting
- Write using the selected tone and formality level
- Keep paragraphs short (2-4 sentences maximum)
- Use bullet points for multiple items or action items
- Bold or highlight key dates, deadlines, or decisions
- Include all necessary context without over-explaining
STOP — Do NOT send without completing the review phase.
Phase 4: Review
- Read aloud for natural flow and tone
- Check that the subject line matches the content
- Verify all names, dates, and attachments are correct
- Ensure the CTA is clear and actionable
- Consider how the email reads if forwarded out of context
Email Type Decision Table
| Situation | Structure | Tone | Key Element |
|---|---|---|---|
| Status update to stakeholders | Inverted Pyramid | Professional | Bold status indicator, bullet points |
| Request for approval/decision | BLUF | Professional | Recommendation first, supporting data |
| Delivering bad news | Sandwich | Formal | Empathy, explanation, constructive close |
| Meeting request | Direct | Professional-Friendly | Agenda items, time options |
| Cold outreach | Personalized Hook | Professional | Specific observation about recipient |
| Follow-up (no response) | Gentle Reminder | Professional | Easy options, graceful out |
| Escalation | Structured Report | Formal | Impact, attempts made, specific ask |
| Apology | Acknowledgment + Action | Formal | Honest explanation, preventive measures |
| Internal team update | Quick Update | Friendly Professional | Brevity, action items highlighted |
| Negotiation | Collaborative | Professional | Shared interests, multiple options |
Tone Calibration Matrix
| Tone Level | When to Use | Characteristics | Example Opening |
|---|---|---|---|
| Formal | C-suite, legal, first contact with executives | No contractions, full titles, structured | "Dear Ms. Chen, I am writing to formally request..." |
| Professional | Standard business, cross-team, clients | Contractions ok, warm but focused | "Hi Sarah, I wanted to follow up on our conversation..." |
| Friendly Professional | Familiar colleagues, regular collaborators | Casual openings, personality shows | "Hey team, quick update on the launch timeline..." |
| Casual | Close teammates, informal updates | Conversational, emoji acceptable | "Just a heads up — the deploy is going out at 3pm" |
Tone Adjustment Signals
| Signal | Shift Toward |
|---|---|
| Bad news, rejection, complaint | More formal, more empathetic |
| Good news, congratulations | Warmer, more enthusiastic |
| Urgency, deadline | More direct, shorter sentences |
| Sensitive/political topic | More formal, more careful word choice |
| Follow-up after no response | Slightly more formal, provide easy out |
Email Structure Patterns
The Inverted Pyramid (Default)
Subject: [Action Required] Q3 Budget Approval — Due Friday
Hi Maria,
[BOTTOM LINE FIRST]
I need your approval on the Q3 budget by Friday, March 19.
[CONTEXT]
The finance team reviewed our proposal and approved the
$240K allocation with one change: marketing spend shifted
from Q3 to Q4.
[DETAILS]
Key changes from the original proposal:
- Marketing: $80K → $60K (Q3), $20K moved to Q4
- Engineering: unchanged at $120K
- Operations: $40K (new line item for tooling)
[ACTION]
Could you review the attached spreadsheet and reply with
your approval? Happy to jump on a quick call if you have
questions.
Thanks,
Alex
The BLUF (Bottom Line Up Front)
Subject: Decision Needed: Vendor Selection for Auth Service
Hi team,
RECOMMENDATION: Go with Auth0 (Option B).
Here's why:
1. 40% lower total cost over 3 years
2. Better compliance certifications (SOC2, HIPAA)
3. Faster integration timeline (2 weeks vs. 6 weeks)
Full comparison attached. Please reply by Thursday with
your vote or concerns.
The Sandwich (Difficult Messages)
[Positive/Neutral Opening]
Thank you for the thorough proposal on the new dashboard.
The data visualization approach is exactly what we needed.
[Difficult Content]
After reviewing with the team, we've identified some concerns
with the timeline and resource allocation that we need to
address before moving forward...
[Constructive/Forward-Looking Close]
I'd love to schedule 30 minutes this week to work through
these together. I'm confident we can find an approach that
works for everyone.
Templates for Common Scenarios
Meeting Request
Subject: Meeting Request: [Topic] — [Suggested Date/Time]
Hi [Name],
I'd like to schedule [duration] to discuss [topic].
Specifically, I'd like to cover:
- [Agenda item 1]
- [Agenda item 2]
Would [date/time option 1] or [date/time option 2] work
for you? Happy to adjust to your availability.
Best,
[Name]
Project Status Update
Subject: [Project Name] Status Update — Week of [Date]
Hi [stakeholders],
**Status: On Track** (or At Risk / Blocked)
**Completed this week:**
- [Accomplishment 1]
- [Accomplishment 2]
**In progress:**
- [Task 1] — expected completion [date]
- [Task 2] — expected completion [date]
**Blockers/Risks:**
- [Blocker] — [mitigation plan or help needed]
**Next week's priorities:**
- [Priority 1]
- [Priority 2]
Let me know if you have questions or want to discuss any
of these items.
[Name]
Escalation Email
Subject: [Escalation] [Issue] — Impact on [Project/Deadline]
Hi [Manager/Stakeholder],
I'm escalating [issue] because [reason — timeline impact,
blocked dependencies, unresolved after N attempts].
**Background:**
[2-3 sentences of context]
**Impact if unresolved:**
- [Consequence 1 with timeline]
- [Consequence 2]
**What I've tried:**
- [Attempt 1 — outcome]
- [Attempt 2 — outcome]
**What I need:**
[Specific ask — decision, resource, intervention]
**Recommended next step:**
[Your suggestion]
I'm available to discuss this at your earliest convenience.
[Name]
Apology / Mistake Acknowledgment
Subject: Regarding [Issue] — Our Apology and Next Steps
Hi [Name],
I want to apologize for [specific issue]. This fell short
of the standard you should expect from us.
**What happened:**
[Brief, honest explanation — no excuses]
**What we're doing about it:**
- [Immediate fix]
- [Preventive measure for the future]
**What this means for you:**
[Any impact, compensation, or timeline adjustment]
I take full responsibility for this and am committed to
making it right. Please don't hesitate to reach out if
you have any concerns.
Sincerely,
[Name]
Cold Outreach
Subject: [Personalized hook — reference their work/company]
Hi [Name],
I noticed [specific observation about their company/role/content].
[One sentence connecting their situation to your offering.]
[Company/Product] helps [target audience] [achieve outcome].
For example, [brief case study or metric].
Would you be open to a 15-minute call to explore whether
this could help [their company]? No pressure either way.
Best,
[Name]
[Title, Company]
Follow-Up After No Response
Subject: Re: [Original Subject]
Hi [Name],
I wanted to follow up on my email from [date] about [topic].
I understand you're busy — would it help if I:
- [Simplified option A]
- [Alternative option B]
- [Easy opt-out: "Let me know if this isn't a priority
right now and I'll circle back later"]
[Name]
Subject Line Best Practices
Formula
[Action Tag] + [Specific Topic] + [Context/Deadline]
Examples:
"[Action Required] Q3 Budget Approval — Due March 19"
"[FYI] New Deploy Process Starting Monday"
"[Decision Needed] Vendor Selection by EOW"
"[Update] Sprint 12 Retro Notes"
"[Blocked] API Integration — Need Access Keys"
Subject Line Rules
| Rule | Good | Bad |
|---|---|---|
| Be specific | "Q3 Marketing Budget: $80K Reallocation" | "Budget Update" |
| Include action if needed | "[Review Required] PR #342" | "Please look at this" |
| Keep under 50 chars | "Launch timeline shifted to April 3" | "Update regarding the potential shift in our product launch timeline" |
| No ALL CAPS | "[Urgent] Server outage in prod" | "URGENT SERVER DOWN!!!" |
| Match the content | "Meeting recap: 3 action items" | "Great chat today!" |
Cultural Considerations
| Context | Adjustment |
|---|---|
| East Asian business culture | More formal, acknowledge hierarchy, indirect negative feedback |
| German business culture | Direct and precise, titles important (Herr/Frau), structured |
| US startup culture | Casual, first names, brief, action-oriented |
| UK business culture | Polite hedging ("I wonder if...", "Perhaps we might...") |
| Cross-timezone | State timezone explicitly, suggest multiple options |
| Non-native English speakers | Simpler vocabulary, shorter sentences, avoid idioms |
Anti-Patterns / Common Mistakes
| Anti-Pattern | Why It Fails | What To Do Instead |
|---|---|---|
| Burying the ask at the bottom | Reader may never reach it | Lead with the request (BLUF) |
| Reply-all unnecessarily | Clutters inboxes, annoys recipients | Reply only to those who need to act |
| Passive-aggressive tone | Damages relationships and trust | Be direct and professional |
| Long emails requiring mobile scrolling | Recipients skip or defer | Keep to 5-8 sentences for mobile |
| Vague subject lines ("Quick question") | Gets deprioritized or lost | Include topic and action needed |
| Too many asks for too many people | Diffusion of responsibility | One primary ask per email |
| No deadline ("when you get a chance") | Means never | Specify date and time |
| CC-ing manager without telling recipient | Perceived as hostile escalation | Mention it in the email or tell them first |
| Humor or sarcasm in text | Misinterpreted without vocal tone | Save humor for in-person |
| Sending emotional emails immediately | Regret and reputation damage | Wait 30 minutes before sending |
Anti-Rationalization Guards
- Do NOT skip the context assessment because "it's just a quick email" -- every email represents you.
- Do NOT draft without a defined CTA -- even "FYI" emails should state what you expect.
- Do NOT send without the read-aloud review, especially for sensitive emails.
- Do NOT use a casual tone with someone you haven't corresponded with before.
- Do NOT send an escalation email without documenting what you have already tried.
Integration Points
| Skill | How It Connects |
|---|---|
content-creator | Brand voice and copywriting frameworks apply to marketing emails |
content-research-writer | Research summaries inform executive briefing emails |
docx-processing | Generated documents attach to emails |
pdf-processing | Generated PDF reports attach to emails |
xlsx-processing | Spreadsheet attachments accompany data-driven emails |
llm-as-judge | Evaluate email tone and clarity against rubric |
Skill Type
FLEXIBLE — Adapt tone, structure, and formality to the relationship, organizational culture, and communication purpose. The BLUF structure and clear subject line practices are strongly recommended for all professional correspondence.
FAQ
What does the email-composer skill do?
Use when the user needs professional email drafting, tone adjustment, template creation, or communication strategy for business correspondence. Trigger conditions: draft professional email, adjust email tone, create email template, write cold outreach, compose follow-up, draft escalation email, write apology email, craft meeting request, compose status update, plan email communication strategy.
How do I install email-composer?
Run npx skills add https://github.com/pixel-process-ug/superkit-agents --skill email-composer in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/email-composer/ (personal) or .claude/skills/email-composer/ (project).
Which AI agents can use email-composer?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is email-composer safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains email-composer?
It is published by pixel-process-ug in pixel-process-ug/superkit-agents. It has 78 recorded installs.
More from pixel-process-ug/superkit-agents
ui-ux-pro-max
pixel-process-ug/superkit-agents
Use when the user needs full UI/UX design intelligence — styles, palettes, fonts, UX guidelines, chart selection, and accessible, performant implementation across any supported stack. Triggers: user says "design", "UI", "UX", "color palette", "typography", "accessibility", "responsive design", "chart type", "style guide", building any user-facing interface.
frontend-ui-design
pixel-process-ug/superkit-agents
Use when designing UI components, creating component architectures, implementing responsive layouts, setting up design systems, or selecting state management solutions for frontend applications
reverse-engineering-specs
pixel-process-ug/superkit-agents
Use when onboarding to an existing codebase that lacks specifications — exhaustively traces code paths and produces implementation-free behavioral specifications for safe refactoring, feature addition, or legacy modernization
canvas-design
pixel-process-ug/superkit-agents
Use when the user needs HTML Canvas, SVG graphics, data visualization, generative art, or interactive visual elements with D3.js or similar libraries. Triggers: user says "canvas", "SVG", "chart", "data visualization", "D3", "generative art", "animation", "interactive graphics", drawing on screen.
autonomous-loop
pixel-process-ug/superkit-agents
Use when running Ralph-style iterative autonomous development. Triggers on /ralph or /loop commands, when autonomous iterative development is needed, when a project has specs and an implementation plan ready for iterative execution, or when deterministic context loading with subagent delegation and dual-condition exit gates is required. Orchestrates PLANNING, BUILDING, and STATUS cycles.
mobile-design
pixel-process-ug/superkit-agents
Use when the user needs mobile app design and development patterns for React Native, Flutter, or SwiftUI — including platform HIG compliance, gestures, and offline-first architecture. Triggers: user says "mobile", "iOS", "Android", "React Native", "Flutter", "SwiftUI", "app design", "mobile navigation", "touch targets", "offline-first".
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。