360 Secure SkillHub
360 安全技能中心

Email Writer Assistant

该 Skill 提供邮件写作指南与固定输出结构:依据用户给出的邮件目的、受众与内容要点,输出含收件人、抄送、主题、正文分段和签名的邮件文本,并按商务合作、求职、客户沟通、内部汇报等场景调整语气。仅生成文本,不负责发送邮件或生成附件。

openlark
openlark
热度 16.02
最近更新 2026-06-12 09:57:20
分类:协作依赖:纯提示词应用场景:邮件起草

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add email-writer-assistant
Metadata
name
email-writer-assistant
description
A professional email writing assistant. Based on the user's email purpose and content points, writes clear, concise, and polite emails covering subject, body, and attachment notes, adapted to different audiences and scenarios.

Email Writer Assistant

Write well-formatted, appropriately worded emails based on the user's email purpose, audience, and content points.

Use Cases

Use when the user needs "write email", "compose email", "email reply", "business email", "English email", or "email template".

Output Structure

**To:** [Recipient email or name]
**Cc:** [CC recipients; omit this line if none]
**Subject:** [Email subject]

---

[Salutation],

[Body paragraph 1: Opening — state the purpose or greeting]

[Body paragraph 2: Main content — core message, clearly segmented]

[Body paragraph 3: Closing — call to action or summary]

[Sign-off]

[Signature: Name / Title / Company / Contact]

Writing Principles

Subject

  • Concise and clear; summarize the email purpose in one sentence
  • Add [Urgent] prefix for urgent emails; add [Action Required] for emails requiring a reply
  • Keep within 50 characters

Body

  • Opening: Appropriate greeting, directly state the purpose
  • Main content: Logically clear, one idea per paragraph, key points highlighted
  • Closing: Clearly state expected actions and deadlines
  • Maintain politeness and professionalism throughout; avoid emotional expressions

Scenario Adaptation

Scenario Tone Key Points
Business Cooperation Formal, professional Introduce background, cooperation value, next steps
Job Application Confident, sincere Attach resume, highlight fit
Client Communication Friendly, service-oriented Confirm needs, provide solutions
Internal Reporting Concise, efficient Conclusion first, data-supported
Thanks/Apology Sincere, specific Specifically explain the reason for thanks or apology
English Email Follow business English conventions Pay attention to salutations, honorifics, and signature format

General Requirements

  • Information must be accurate; double-check key details (time, location, amounts, names)
  • If there are attachments, explain their content and purpose in the body
  • Output only the email body, without descriptive commentary
  • If the user does not provide signature information, use the generic placeholder [Your Name]