Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

email-composer电子邮件编辑器

Agent Skill

email-composer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,833

周安装

180

GitHub Stars

3

下载量

1,972
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:email-composer(电子邮件编辑器)
来源仓库:https://github.com/jmsktm/claude-settings
仓库路径:skills/email-composer
安装命令:
npx skills add https://github.com/jmsktm/claude-settings --skill 'Email Composer'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jmsktm/claude-settings --skill 'Email Composer'

简介

用于查找、检索和筛选邮件撰写相关模板或写作指导。

  • 适合根据沟通场景(如商务、通知、请求)定位表达方式。
  • 使用时需提供收件人背景、核心诉求和语气要求。email-composer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 结果引用建议结合原始 README 核验具体用法和限制。
  • 安装前建议确认权限范围及是否会触发联网或文件读写操作。

SKILL.md

Email Composer

The Email Composer skill helps you craft professional, effective emails for any business context. Whether you need to reach out to a client, respond to a team inquiry, follow up on a meeting, or send a cold outreach message, this skill ensures your emails are clear, appropriately toned, and action-oriented.

This skill analyzes the context you provide and generates emails that match the appropriate level of formality, include necessary components (subject line, greeting, body, call-to-action, closing), and maintain professional standards. It can adapt tone from casual internal communications to formal external correspondence.

The skill also considers email best practices like brevity, clarity, scannable structure, and clear next steps to maximize response rates and effectiveness.

Core Workflows

Workflow 1: Draft New Email

  1. Gather Context: Understand the purpose, recipient, and key points
  2. Determine Tone: Assess formality level (casual, professional, formal)
  3. Structure Email: Create subject line, opening, body paragraphs, CTA, closing
  4. Review & Refine: Check for clarity, conciseness, and appropriate tone
  5. Deliver: Present complete email ready to send

Workflow 2: Reply to Email Thread

  1. Review Thread: Analyze previous messages for context
  2. Identify Key Points: Extract questions or items requiring response
  3. Craft Response: Address all points systematically
  4. Maintain Thread: Preserve relevant context while staying concise
  5. Close Loop: Ensure all items are addressed with clear next steps

Workflow 3: Email Template Creation

  1. Identify Use Case: Understand the recurring scenario
  2. Define Variables: Mark customizable sections
  3. Create Template: Build reusable structure
  4. Add Guidelines: Include usage notes and customization tips
  5. Test & Validate: Review with example content

Quick Reference

ActionCommand/Trigger
Draft new email"Draft email to [recipient] about [topic]"
Reply to thread"Write reply to [sender] addressing [points]"
Cold outreach"Compose cold email to [prospect] for [purpose]"
Follow-up email"Write follow-up on [topic] from [date/meeting]"
Thank you email"Draft thank you email for [reason]"
Internal update"Write team email about [update/announcement]"
Create template"Create email template for [use case]"
Adjust tone"Make this more [formal/casual/friendly]"

Email Types Supported

  • Cold Outreach: First contact with prospects or partners
  • Follow-ups: After meetings, proposals, or previous emails
  • Internal Updates: Team announcements and status reports
  • Client Communication: Professional updates and responses
  • Thank You Notes: Appreciation and acknowledgment
  • Meeting Requests: Scheduling and coordination
  • Introductions: Connecting people or introducing services
  • Apologies: Professional handling of mistakes or delays
  • Requests: Asking for information, time, or resources
  • Confirmations: Acknowledging receipt or confirming details

Best Practices

  • Subject Lines: Keep under 50 characters, make them specific and actionable
  • Opening: Personalize when possible, reference previous interactions
  • Body Structure: Use short paragraphs (2-3 sentences max), bullet points for lists
  • One Main Point: Each email should have one primary purpose
  • Clear CTA: End with specific next step or call-to-action
  • Appropriate Length: Aim for under 200 words for most business emails
  • Professional Tone: Match recipient's communication style while staying professional
  • Proofread: Check for typos, grammar, and clarity before sending
  • Timing: Consider time zones and optimal send times
  • Mobile-Friendly: Format should be easily readable on mobile devices

Tone Guidelines

ContextToneExample Opening
Cold OutreachProfessional, Value-focused"I noticed your work on [X] and wanted to reach out..."
Internal TeamCasual, Clear"Quick update on the project..."
Client CommunicationProfessional, Helpful"Thank you for your message regarding..."
Executive CommunicationFormal, Concise"Per our discussion on [topic]..."
Follow-upFriendly, Persistent"I wanted to circle back on..."
ApologyHumble, Solution-oriented"I apologize for the confusion regarding..."

Common Pitfalls to Avoid

  • Too Long: Emails over 300 words rarely get fully read
  • Buried Lede: Put the main point in the first paragraph
  • No Clear Ask: Always end with what you need from recipient
  • Generic Greetings: Personalize when possible
  • Over-Apologizing: One sincere apology is enough
  • Reply-All Abuse: Only use when truly necessary
  • Vague Subject: Be specific about email content
  • Missing Context: Don't assume recipient remembers previous conversations

Usage Examples

Example 1: Cold Outreach

Subject: Quick question about [Company]'s content strategy

Hi [Name],

I came across your recent article on [topic] and was impressed by your approach to [specific point].

I'm reaching out because we've developed a tool that helps companies like [Company] streamline their content workflow. I'd love to show you how [specific benefit relevant to their work].

Would you be open to a quick 15-minute call next week to explore this?

Best regards,
[Your name]

Example 2: Internal Update

Subject: Design sprint update - Week of Jan 6

Team,

Quick update on our progress:

✅ Completed: User research interviews (12/12)
🏃 In progress: Wireframe iterations for checkout flow
📅 Next: Prototype testing scheduled for Thursday

Blocker: Still waiting on API specs from backend team.

Let me know if you have questions.

[Your name]

Example 3: Follow-up Email

Subject: Following up - Partnership discussion

Hi [Name],

I wanted to follow up on our conversation from last Tuesday about the potential partnership between our companies.

As discussed, I've attached the proposal outlining our integration timeline and resource requirements. The key highlights:

• Go-live target: March 15, 2026
• Estimated setup time: 2-3 weeks
• Monthly cost: $X,XXX

Are you available for a brief call this week to discuss next steps?

Thanks,
[Your name]

Integration Points

  • CRM Systems: Draft emails based on contact records and interaction history
  • Calendar: Include meeting links and availability
  • Task Management: Reference tickets, projects, or action items
  • Templates Library: Build and maintain reusable templates
  • Analytics: Track open rates and response rates to improve effectiveness

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.98%
按下载量换算690

Claude

29.29%
按下载量换算578

Cursor

19.09%
按下载量换算376

Gemini CLI

9.96%
按下载量换算196

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills