Token导航 LogoToken导航

Agent Skill · 研究检索

follow-up-emails(跟进电子邮件)

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

follow-up-emails 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 60,488。

总安装 367周安装 15GitHub Stars 30下载 119核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/salesably/salesably-marketplace --skill follow-up-emails

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

follow-up-emails 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。适用于研究类任务,如市场调研、竞品分析或信息搜集,帮助 Agent 高效获取目标线索。

通过关键词输入和来源仓库配置,Agent 可自动检索并整理相关数据,支持进一步人工核验。安装前需确认权限范围和维护状态,注意是否涉及联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/follow-up-emails

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/salesably/salesably-marketplace --skill follow…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

follow-up-emails 怎么安装?

在终端执行 npx skills add https://github.com/salesably/salesably-marketplace --skill follow-up-emails。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

follow-up-emails 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

follow-up-emails 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

follow-up-emails 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

follow-up-emails 用的人多吗?

公开数据是累计安装 367 次,近一周安装 15 次,下载 119 次,GitHub 30 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

follow-up-emails 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
follow-up-emails

跟进电子邮件 · 本页

36730只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Follow-Up Emails

This skill creates professional, well-structured follow-up emails that capture key discussion points, confirm action items, and maintain deal momentum after sales conversations.

Objective

Transform sales call insights into clear, compelling follow-up emails that reinforce value, confirm next steps, and keep deals moving forward.

Email Structure

1. Personalized Opening

Brief greeting that acknowledges the conversation.

Good Examples:

  • "Thanks for making time to chat today."
  • "Great connecting with you this afternoon."
  • "Appreciated the candid conversation earlier."

Avoid:

  • Generic "Hope this email finds you well"
  • Overly effusive thanks
  • Restating obvious facts ("As we discussed...")

2. Next Steps Section

The most important part-clear action items.

Format:

## Next Steps

**Your action items:**
- [Action 1] - by [date]
- [Action 2] - by [date]

**My action items:**
- [Action 1] - by [date]
- [Action 2] - by [date]

Guidelines:

  • Lead with their action items (creates accountability)
  • Be specific about what and when
  • Keep it to 2-4 items total
  • Make deadlines clear but reasonable

3. Discussion Summary

Organized recap of what was covered.

Sections to Include:

Challenges Discussed:

  • Key pain points they mentioned
  • Impact of those challenges
  • Urgency or timeline drivers

Goals Identified:

  • Desired outcomes they expressed
  • Success criteria mentioned
  • Priority areas

Solutions Discussed:

  • How your solution addresses their needs
  • Features or capabilities most relevant
  • Differentiation from alternatives

4. Professional Closing

Brief sign-off with clear call to action.

Good Closings:

  • "Looking forward to our follow-up on [date]."
  • "Let me know if anything changes or if you have questions."
  • "Happy to chat before then if anything comes up."

Customization Options

Tone Settings

Formal:

  • Full sentences, proper grammar
  • Professional language
  • Structured format
  • Appropriate for executives or first interactions

Casual:

  • Conversational language
  • Contractions allowed
  • Lighter touch
  • Good for established relationships

Persuasive:

  • Emphasizes value and urgency
  • Stronger calls to action
  • More selling language
  • Use when deal needs momentum

Length Settings

Brief (150-200 words):

  • Next steps only
  • One-line summary of discussion
  • Best for busy executives or quick check-ins

Standard (200-350 words):

  • Full structure with all sections
  • Balanced detail
  • Best for most follow-ups

Detailed (350-500 words):

  • Comprehensive summary
  • Additional context and value
  • Best for complex deals or multiple stakeholders

Emphasis Options

Focus the email on specific areas:

  • Challenges: Emphasize pain points discussed
  • Solutions: Highlight how you address their needs
  • Next Steps: Focus on action and momentum
  • Value: Reinforce ROI and business impact

Email Templates by Scenario

Post-Discovery Call

Subject: Follow-up: [Company] Discovery Call

Hi [Name],

Thanks for the great conversation today. I learned a lot about
[key challenge] and how it's impacting [business outcome].

## Next Steps
- [Their action] - by [date]
- [Your action] - by [date]

## Key Takeaways
- [Challenge 1 and its impact]
- [Challenge 2 and its impact]
- [Goal they mentioned]

Based on what you shared, I think [your solution] could help by
[specific benefit]. I'll have [deliverable] ready for our next call.

Talk soon,
[Your name]

Post-Demo Follow-Up

Subject: [Company] Demo Follow-up + Resources

Hi [Name],

Great walking through [product] with you and [other attendees] today.

## What We Covered
- [Feature 1] and how it addresses [their need]
- [Feature 2] and the impact on [their goal]
- [Feature 3] for [specific use case]

## Next Steps
- [Their action] - by [date]
- [Your action] - by [date]

## Resources
- [Link to recording/deck/materials]
- [Link to relevant case study]

Let me know if questions come up as you think things through.

Best,
[Your name]

Proposal Follow-Up

Subject: [Company] Proposal + Next Steps

Hi [Name],

As promised, attached is the proposal we discussed. Here's a quick summary:

## Investment
- [Pricing summary]
- [Payment terms if relevant]

## Timeline
- [Implementation timeline]
- [Key milestones]

## Next Steps
- [Their action] - Review and share feedback by [date]
- [Your action] - [Any follow-up you're doing]

Happy to walk through any questions-just let me know.

Best,
[Your name]

Quality Guidelines

Make It Scannable

  • Use headers and bullet points
  • Bold key information
  • Keep paragraphs short
  • Front-load important content

Be Accurate

  • Capture what was actually discussed
  • Use their language and terminology
  • Double-check names and details
  • Don't embellish or oversell

Create Accountability

  • Be specific about who does what
  • Include concrete dates
  • Make next steps clear
  • Set expectations appropriately

Add Value

  • Include relevant resources
  • Anticipate questions
  • Provide helpful context
  • Make their job easier

Output Format

When creating a follow-up email, produce:

  1. Subject Line: Clear, specific subject
  2. Full Email: Properly formatted with all sections
  3. Personalization Notes: What was customized and why
  4. Suggested Attachments: What to include with the email
  5. Send Timing: When to send for best response

Cross-References

  • Use call-analysis output as input for email content
  • Apply powerful-framework insights for targeted messaging
  • Feed into multithread-outreach for stakeholder variants
  • Reference prospect-research for personalization

平台分布

Codex

34.73%
按下载量换算41

Claude

32.91%
按下载量换算39

Cursor

17.38%
按下载量换算21

Gemini CLI

10.21%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills