菜单
Drafts personalized follow-up emails and messages based on Evergreen CRM contact history, past interactions, and pending actions. Use when you need to write a follow-up email, thank-you note, check-in message, or any outreach to an existing contact.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/wdm0006/evergreen-skills --skill drafting-evergreen-follow-ups命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | drafting-evergreen-follow-ups |
| description | Drafts personalized follow-up emails and messages based on Evergreen CRM contact history, past interactions, and pending actions. Use when you need to write a follow-up email, thank-you note, check-in message, or any outreach to an existing contact. |
Works with Evergreen, a local-first personal CRM for macOS. Get it on the Mac App Store.
get_contact for full profileget_contact_interactions for conversation historylist_actions for any commitmentsget_contact_network for shared connections contextlog_interactionmark_action_completed| Type | Tone | Key Elements |
|---|---|---|
| Post-meeting recap | Professional, warm | Key takeaways, action items, next steps |
| Thank-you note | Grateful, specific | What you're thankful for, why it mattered |
| Check-in | Casual, genuine | Reference last conversation, ask about their work |
| Introduction follow-up | Enthusiastic, brief | Reference who introduced you, what excited you |
| Congratulations | Warm, sincere | Specific achievement, genuine reaction |
| Re-engagement | Low-pressure, curious | Shared memory, open-ended question |
Context from Evergreen:
Contact: Sarah Chen (CTO, Meridian Health)
Last interaction: Meeting on Mar 20 — "Discussed API integration possibilities"
Pending action: "Send API documentation" (due Apr 2)
Notes: "Interested in our healthcare data pipeline"
Drafted message:
Subject: API docs + a few thoughts from our chat
Hi Sarah,
Great catching up at the dinner last month. I've been thinking more
about the integration approach we discussed for Meridian's patient
data pipeline.
As promised, here are our API docs: [link]
I flagged the batch processing section specifically — based on what
you described about your throughput needs, that's probably the most
relevant starting point.
Happy to jump on a quick call if any questions come up as your team
reviews. What does your week look like?
Best,
[Name]
Post-send:
1. log_interaction({ contactId: sarah_id, type: "email", description: "Sent API docs follow-up, offered call to discuss" })
2. mark_action_completed({ actionId: api_docs_action_id }) // "Send API documentation"
| Principle | Meaning |
|---|---|
| Specific | Reference real details from your history, not generic pleasantries |
| Brief | Respect their time — get to the point in 3-5 sentences |
| Action-oriented | Include a clear next step or question |
| Authentic | Match the user's natural voice and relationship level |
| Contextual | Show you remember what matters to them |
Follow-Up Draft:
- [ ] Contact history reviewed for relevant context
- [ ] Message references specific shared details
- [ ] Clear call-to-action or next step included
- [ ] Tone matches the relationship level
- [ ] Interaction logged after sending
- [ ] Related actions marked complete