events helps an agent make events produce pipeline and content. It asks which role you play (hosting, sponsoring or exhibiting, speaking, attending), what the primary outcome is, who must be in the room, and what budget and team exist.
Its core idea is that the event is 20 percent of the work and the before and after are 80 percent: target lists and pre-booked meetings, then fast, tiered follow-up routed to the CRM. Measurement separates vanity numbers from qualified meetings and cost per opportunity.
What You Get
- A role-based plan for hosting, sponsoring, speaking or attending
- A selection approach that favors a few high-yield events over many
- A pre-event routine: target list, meeting outreach and announcements
- A tiered follow-up plan for hot, warm and scan-only contacts
- A measurement table that separates vanity, real and decisive metrics
Common Use Cases
- Deciding whether a conference booth is worth the money
- Planning a recurring webinar as a lead source
- Hosting a small dinner next to a big conference
- Turning event recordings into clips, recaps and proof points
What Makes It Unique
It starts with portfolio selection: events are judged one at a time, size is treated as noise and cost, and in-person is reserved for high-trust, high-ACV motions. It gives the attending role a zero-budget playbook with a side-event dinner, and it treats each event as a content engine with recordings and transcripts that AI assistants can cite.
Under The Hood
The SKILL.md and four references are loaded as context. It ships no scripts and runs no commands, and it reaches no outside service. It reads the product marketing context file in your project when present. The plan, outreach angles and follow-up notes are written by the agent in chat or to files you name.