skills/event-follow-up/SKILL.md
Batch-processes contacts from a conference, dinner, or networking event into Evergreen CRM — creates records, tags them by event, and drafts personalized follow-up messages. Use after any event where you met multiple new people.
npx skillsauth add wdm0006/evergreen-skills evergreen-event-follow-upInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Works with Evergreen, a local-first personal CRM for macOS. Get it on the Mac App Store.
search_contactscontacts.createtags.add_to_contactinteractions.lognotes.appendactions.createUse consistent event tags for easy filtering later:
Format: event-[name]-[year]
Examples:
event-ai-dinner-2026
event-pycon-2026
event-founders-retreat-q1
event-team-offsite-apr26
Input: Notes from Atlanta AI Dinner
Met at Atlanta AI Dinner, April 3, 2026:
1. Sarah Chen — CTO at Meridian Health. Talked about healthcare data
pipelines. Very interested in our API. [email protected]
2. Marcus Webb — Founder of DataFlow. Building real-time analytics.
Previously at Google. [email protected]
3. Priya Sharma — ML Engineer at NewCo. Working on NLP for
customer support. [email protected]. Introduced by David Kim.
Batch processing:
For each contact:
1. search_contacts("[name]") → check for duplicates
2. contacts.create({ ... })
3. tags.add_to_contact(id, ["event-ai-dinner-2026", "atlanta", "ai"])
4. interactions.log(id, {
type: "meeting",
summary: "Met at Atlanta AI Dinner — [conversation topic]"
})
5. notes.append(id, "[conversation details]")
6. actions.create({
contact_id: id,
title: "Send follow-up email to [name]",
due_date: "2026-04-05",
priority: "medium"
})
Sample follow-up for Sarah:
Subject: Great meeting you at the AI Dinner
Hi Sarah,
Really enjoyed our conversation about healthcare data pipelines last
night. The challenges you described with real-time patient data are
exactly the kind of problems I find fascinating.
I'd love to continue the conversation — especially around how our
API might fit into Meridian's architecture. Free for a quick call
next week?
Best,
[Name]
| Priority | When to Send | Who | |----------|-------------|-----| | Same night / next morning | People you had deep conversations with | | Within 48 hours | Everyone else you want to stay in touch with | | Within a week | Lower priority but still worth connecting | | Skip | Brief hellos with no real connection point |
Event Follow-Up:
- [ ] All contacts created with complete details
- [ ] Event tag applied consistently
- [ ] Initial interaction logged with conversation context
- [ ] Notes capture what you discussed (not just who they are)
- [ ] Follow-up messages personalized per conversation
- [ ] Follow-up actions created with appropriate deadlines
business
Generates a weekly relationship management digest from Evergreen CRM — interactions logged, follow-ups completed vs missed, network growth, and a spotlight contact. Use for weekly reviews, accountability, or planning the week ahead.
testing
Drafts double-opt-in introduction emails connecting two Evergreen CRM contacts. Use when someone asks for an introduction, when you spot a mutually beneficial connection, or when facilitating networking between contacts.
testing
Audits Evergreen CRM for stale or incomplete contact data — outdated titles, missing fields, potential duplicates, and contacts that may have changed jobs. Use for periodic database hygiene, before a big outreach push, or when data quality feels off.
business
Scores and surfaces relationship health across your Evergreen CRM contacts — identifies thriving relationships, ones at risk, and dormant connections needing attention. Use when you want a high-level view of your network health or need to prioritize relationship investment.