agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/event-follow-up/SKILL.md

event-follow-up

Skill13 starsChanged 23 days agoMITView on GitHub

Use this skill when you need to turn a conference, trade show, webinar or roundtable into pipeline: \"follow up with event leads\", \"post-webinar email\", \"trade show follow-up sequence\", \"pre-event outreach to book meetings\". Plans pre-event outreach to book meetings, sorts leads after the event by conversation quality, and writes follow-ups that reference the actual conversation or session, with timing and channel for each lead group.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this around any event.

    line 16
  2. Distinctive:

    Every message references something real from the event.

    line 58
  3. Distinctive:

    MUST follow up hot leads within 24 hours.

    line 64
  4. Distinctive:

    MUST respect the consent people gave at the event (badge scans and webinar terms differ by event and region).

    line 65
  5. Distinctive:

    NEVER claim a conversation that did not happen.

    line 66

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this around any event. Most event leads go cold because follow-up is slow and generic; a fast follow-up that references the real conversation stands out from every other booth.

Inputs

  • The event, your presence (booth, talk, sponsor, attendee) and dates.
  • Lead list with notes: who you spoke with and about what; webinar registrants and attendees.
  • What you presented or demoed.

The play

1. Before the event: book meetings

Two to three weeks before, reach target accounts attending: a short email or LinkedIn message with a reason to meet (a specific session, a private demo, a small dinner). Meetings booked before the event beat badge scans after it.

2. Sort leads within 24 hours

GroupWhoFollow-up
HotReal conversation about a live need; asked for a next stepPersonal email same or next day, meeting proposal
WarmGood conversation, no clear need yetPersonal email within 2 days, useful resource
SessionAttended your talk or webinarRecording, slides, one insight, soft ask
ColdBadge scan, giveaway, no conversationLight nurture, not sales outreach
Registered, did not attendWebinar no-showsRecording plus a 3-bullet summary

3. Reference the conversation

The first line names what you talked about or what they heard: "Good to talk at the booth about your night-shift scheduling problem." Generic "Great to meet you at the event!" emails are indistinguishable from the fifty others in their inbox.

4. Time and channel

Hot leads: email plus LinkedIn connection the same day. Warm: within 48 hours. Session and webinar: within 24 hours while it is fresh. Then a short sequence (3 touches over 2 weeks) for each group.

5. Measure

Meetings booked per event, pipeline per event, cost per meeting. Badge counts are not results.

Example (hot lead)

Subject: night-shift scheduling

Hi Ana, good talking at the booth yesterday about covering night shifts across your three new sites. As promised, here is how Northwind handles cross-site cover; the part on swap approvals is on page 2.

Would Thursday at 10 work for 20 minutes to look at your setup?

What good looks like

  • Hot leads get a personal message within 24 hours.
  • Every message references something real from the event.
  • Badge-scan-only leads are not sent sales sequences as if they asked for them.
  • The common mistake is one mass "thanks for visiting our booth" email to every scan, a week later.

Rules

  • MUST follow up hot leads within 24 hours.
  • MUST respect the consent people gave at the event (badge scans and webinar terms differ by event and region).
  • NEVER claim a conversation that did not happen.

Example prompts

  • "We had 140 badge scans and 22 real conversations at the summit. Sort them and write the follow-ups."
  • "Write pre-event outreach to book meetings with our target accounts attending next month."
  • "Write a post-webinar sequence for attendees and no-shows."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free