email

GitHub

用于撰写商务邮件的 Skill,涵盖正式与非正式语气、结构化格式、回复与跟进场景及多语言支持。通过确认收件人、目的和语调等细节,提供包含主题行和正文的标准邮件模板,确保内容清晰、可操作且符合商务礼仪。

backend/app/data/skills/email/SKILL.md openyak/openyak

Trigger Scenarios

起草商务邮件 撰写邮件回复 发送跟进邮件 调整邮件语气或风格

Install

npx skills add openyak/openyak --skill email -g -y
More Options

Non-standard path

npx skills add https://github.com/openyak/openyak/tree/main/backend/app/data/skills/email -g -y

Use without installing

npx skills use openyak/openyak@email

指定 Agent (Claude Code)

npx skills add openyak/openyak --skill email -a claude-code -g -y

安装 repo 全部 skill

npx skills add openyak/openyak --all -g -y

预览 repo 内 skill

npx skills add openyak/openyak --list

SKILL.md

Frontmatter
{
    "name": "email",
    "description": "Business email writing — formal\/informal tone, structured format, replies, follow-ups, multilingual support."
}

Business Email Writing

When the user asks you to draft an email, follow this workflow:

1. Clarify key details

Before writing, confirm:

  • Recipient: Who is it for? (manager, colleague, client, external partner)
  • Purpose: Inform, request, follow up, thank, apologize, invite?
  • Tone: Formal, semi-formal, or casual?
  • Language: Match the user's language or ask if bilingual is needed.

If unspecified, infer from context or ask briefly.

2. Email structure

Standard format

  1. Subject line: Clear and specific — the reader should know the topic at a glance
  2. Greeting: Match formality level
  3. Opening: 1-2 sentences stating the purpose or context
  4. Body: Core content, use paragraphs or bullet points for readability
  5. Action items: Clearly state what you need from the recipient and by when
  6. Closing: Polite sign-off
  7. Signature: Add if the user requests it

Reply emails

  • Acknowledge receipt or thank the sender
  • Address each point raised
  • Propose next steps

Follow-up emails

  • Politely reference the previous message
  • Briefly restate the context (avoid making the recipient dig through old emails)
  • State the expected response timeline

3. Tone guide

Scenario Tone Example opening
To senior/client Formal "Dear Mr./Ms. X, I hope this message finds you well."
To colleague Semi-formal "Hi X, regarding our discussion yesterday..."
To familiar partner Friendly professional "Hey X, quick follow-up on what we talked about..."

4. Best practices

  • One email, one topic: Keep each email focused on a single core message
  • Actionable: Tell the recipient exactly what you need them to do
  • No ambiguity: Use specific dates (not "next week"), full names
  • Sensitive content: Remind the user to check for confidential information
  • CC/BCC: Suggest appropriate recipients if relevant

5. Output format

Output in two parts:

  1. Subject line (labeled separately)
  2. Email body

If the user wants multiple versions (e.g., formal and casual), label each clearly.

Version History

  • bd88bff Current 2026-07-25 08:57

Same Skill Collection

backend/app/data/skills/algorithmic-art/SKILL.md
backend/app/data/skills/bootstrap/SKILL.md
backend/app/data/skills/canvas-design/SKILL.md
backend/app/data/skills/charting/SKILL.md
backend/app/data/skills/data-analysis/SKILL.md
backend/app/data/skills/doc-coauthoring/SKILL.md
backend/app/data/skills/document-summary/SKILL.md
backend/app/data/skills/docx/SKILL.md
backend/app/data/skills/frontend-design/SKILL.md
backend/app/data/skills/github-deep-research/SKILL.md
backend/app/data/skills/mcp-builder/SKILL.md
backend/app/data/skills/meeting-notes/SKILL.md
backend/app/data/skills/pdf/SKILL.md
backend/app/data/skills/pptx/SKILL.md
backend/app/data/skills/presentation/SKILL.md
backend/app/data/skills/project-planning/SKILL.md
backend/app/data/skills/report/SKILL.md
backend/app/data/skills/research/SKILL.md
backend/app/data/skills/skill-creator/SKILL.md
backend/app/data/skills/theme-factory/SKILL.md
backend/app/data/skills/translation/SKILL.md
backend/app/data/skills/web-artifacts-builder/SKILL.md
backend/app/data/skills/webapp-testing/SKILL.md
backend/app/data/skills/xlsx/SKILL.md

Metadata

Files
0
Version
067fd4a
Hash
fe79cd11
Indexed
2026-07-25 08:57

inicio - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-25 03:28
浙ICP备14020137号-1 $mapa de visitantes$