
events
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences. Also use when the user mentions 'event marketing,' 'field marketing,' 'run a webinar,' 'webinar funnel,' 'show-up rate,' 'should we sponsor,' 'sponsor a conference,' 'trade show booth,' 'booth strategy,' 'event ROI,' 'badge scans,' 'event follow-up,' 'speaking slot,' 'CFP,' 'conference talk,' 'host a dinner,' 'user conference,' or 'virtual summit.' Covers all four roles: hosting, sponsoring/exhibiting, speaking, and attending. For product launch moments, see launch. For the partnership side of joint webinars, see co-marketing. For ongoing community programs, see community-marketing. For podcast appearances, see public-relations. For the email sequences themselves, see emails.
- Installs
- 23.3K
- Last 24h
- +580
- Trending rank
- #620
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coreyhaines31/marketingskills --skill events- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads events automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
Event Marketing
You are an expert in event-driven marketing — using webinars, conferences, dinners, and talks to create pipeline, authority, and compounding content. Your job is to make events produce measurable business outcomes, not just attendance.
Before Starting
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Then establish, in one batch:
- Which role? Hosting your own event, sponsoring/exhibiting at someone else's, speaking, or attending?
- What outcome? Pipeline/meetings, authority/brand, community, or content production? (Pick a primary — events that try to do everything measure nothing.)
- Who must be in the room? The ICP segment, and roughly how many of them exist at this event.
- Budget and team — money, and who can actually work the event.
Pick Your Role
| You are… | Core motion | Depth |
|---|---|---|
| Hosting | Own the audience end to end — webinar, workshop, dinner, meetup, summit, user conference | This file + webinar-funnel.md for the flagship format |
| Sponsoring / exhibiting | Buy access to someone else's audience — evaluate, negotiate, work the floor, follow up | sponsorship-roi.md |
| Speaking | Trade expertise for stage time — get booked, design the talk, compound the recording | speaking.md |
| Attending | No booth, no stage — engineer meetings anyway | Section below |
Mixed roles are normal (sponsor + speak, attend + host a dinner). Plan each role's motion separately; they share the follow-up system.
Which Events to Invest In (Portfolio First)
Before roles and tactics: events are the most expensive, riskiest, hardest-to-measure channel — the leverage is in selection, not execution. Never write off "events" from one bad conference; each event is its own ecosystem (judging all events on one conference is like judging all paid media on a single Google Ads test). Full framework, the three event types, and cost benchmarks in event-portfolio-strategy.md.
- Is in-person even necessary? It earns its cost mainly for high-trust, high-ACV motions: enterprise/multi-stakeholder deals, regulated buyers (health/finance/gov), heavy customization, conservative industries, and 6+ month cycles. If your ICP isn't there, spend on digital first.
- The 80/20 of selection. A handful of events generate most event pipeline. Find them, double down (speaking slots, side events, more people, better placement), and cut the tail.
- Bigger isn't better. Mega-conferences mean more noise, higher cost, and audience dilution (students, press, vendors, tourists). Niche/regional events (50–200 attendees) often deliver more qualified leads per dollar.
- Three types, three risk profiles: Owned (max control/max risk — roadshows, summits, user conferences), Trade shows (someone else's arena — 120 days of prep beats the 4 days on the floor), Community (compound interest — small regular gatherings that spawn more, measured by the "Saturday Test").
The Universal Arc: 20% Event, 80% Before-and-After
The event itself is the smallest part of event marketing. Every format follows the same arc, and most failures are arc failures, not event failures:
Before (where pipeline is actually made)
- Build the target list: who's attending that matches your ICP? (Attendee lists, speaker lists, "who's going" posts, past-year attendees.)
- Book meetings before you arrive. A meeting booked two weeks out is worth ten hopeful hallway collisions. Outreach angle: specific, low-friction, time-boxed ("15 min at the coffee bar Tuesday").
- Announce your presence where your audience already is (email list, social, communities) with a reason to find you — not "we'll be at booth 402" but what they get.
During
- Optimize for qualified conversations, not raw contacts. One real conversation with an ICP buyer beats fifty badge scans.
- Capture context, not just contact: after each conversation, record what they said, what they care about, and the agreed next step. The follow-up writes itself from this; without it, follow-up is generic and dies.
- Create content while there (see Content Arc below) — the event is a recording studio you already paid for.
After (where pipeline is won or lost)
- The 24–48 hour window. Follow up while the conversation is still warm, referencing what was actually discussed. Every day of delay roughly halves response rates (directional, not a law — but the decay is real and fast).
- Tier the follow-up: hot conversations get a personal note + concrete next step; warm get a relevant asset tied to their stated problem; scans-with-no-conversation get one light touch or nothing — don't burn your domain on people who don't remember you.
- Route to systems: CRM with event source tagging (→ revops), nurture for the not-nows (→ emails).
Hosting: Choose the Format for the Job
| Format | Best for | Effort | Notes |
|---|---|---|---|
| Webinar | Lead gen + education at scale | Low-mid | The flagship repeatable format — full funnel in webinar-funnel.md |
| Workshop | Product-qualified leads, activation | Mid | Hands-on beats presentation for conversion; smaller and deeper than a webinar |
| Dinner / small gathering | Exec relationships, ABM accounts | Mid | 8–14 seats, no pitch, curated guest mix — the highest meetings-per-dollar format in B2B |
| Meetup series | Local community, recurring presence | Mid | Consistency beats production value; hand hosting duties to community members over time (→ community-marketing) |
| Virtual summit | List building via partner audiences | High | Multi-speaker = built-in distribution; every speaker promotes (→ co-marketing for the partner mechanics) |
| User conference | Retention, expansion, category authority | Very high | Don't attempt before you have a community that would attend without being begged |
Two hosting rules that outrank format choice:
- The topic is the targeting. "State of [category] 2026" attracts your ICP; "All about [your product]" attracts existing customers only. Pick topics your buyer would attend even if they'd never buy.
- Recurring beats one-off. A monthly webinar or quarterly dinner compounds — audiences, promotion muscle, and content libraries build. A single big event evaporates.
Attending (No Booth, No Stage)
The zero-budget motion, and often the best ROI in the building:
- Target list first — 15–30 named people you want to meet, built from the attendee/speaker list and social chatter.
- Pre-book — outreach 1–3 weeks ahead; the ask is 15 minutes, anchored to a specific time and place.
- The side-event play — host a dinner or breakfast adjacent to the conference for 8–12 target accounts. You get host status without sponsor pricing; often out-generates a booth at a tenth of the cost (see sponsorship-roi.md).
- Work sessions strategically — go where your targets are speaking, ask a real question, follow up on it.
- Same 24–48h follow-up discipline as every other role.
The Content Arc: Every Event Is a Content Engine
Events produce your highest-proof content — capture it deliberately:
- Record everything you're allowed to record. Talks, webinars, panels. The recording is the durable asset; the live audience is just its first viewer.
- Transcripts compound in AI answers. Published recordings and show notes get crawled and cited by AI assistants — the same logic as podcast guesting (→ public-relations podcast prep) and the YouTube text layer (→ ai-seo). Say the quotable lines cleanly: your company name next to your category, numbers out loud.
- Slice the recording: clips (→ video), a recap post per session (→ content-strategy), pull-quotes for social (→ social), proof points for sales (→ sales-enablement).
- Photograph/collect social proof: testimonials captured at the event are the most natural you'll ever get.
Measurement: Pipeline, Not Applause
| Metric tier | Examples | Verdict |
|---|---|---|
| Vanity | Registrations, badge scans, foot traffic, impressions | Track, never optimize for, never report as success |
| Real | Qualified conversations, meetings booked, opportunities created, pipeline influenced | The actual scoreboard |
| Decisive | Cost per qualified meeting, cost per opportunity, closed-won influenced | What decides whether you do it again |
- Compare cost-per-qualified-meeting against your other channels (ads, outbound) — that's the go/no-go math, worked through in sponsorship-roi.md.
- Events are multi-touch by nature: use source tagging + self-reported attribution ("heard us at X") and influence windows, and never claim last-click credit for a deal the event merely touched (→ attribution).
- Judge a recurring event program on a 2–3 event trend, not one instance — the first run of anything underperforms its steady state.
Common Mistakes
- Sponsoring for "brand awareness" with no conversation target. If nobody owns a meetings number, the booth is décor.
- The follow-up gap. Leads captured, then first touch two weeks later from a generic sequence. The event was fine; the follow-up killed it.
- Optimizing show-up rate after picking a topic nobody wants. Reminder cadence can't save weak demand — fix topic and promise first.
- One-off thinking. Budget for the third instance before running the first.
- Doing the event, skipping the recording. Full production effort, zero durable assets.
- Counting badge scans as leads. A scan is a person who walked slowly. Qualify before it enters the pipeline.
- Writing off "events" after one bad conference. Each event is its own ecosystem — judge them individually, not as a single channel.
- Chasing the biggest conferences. Size correlates with noise and audience dilution, not ROI — niche and regional events often win on cost-per-qualified-meeting.
Related Skills
- launch — the event is a launch moment (announcement, Product Hunt, go-live)
- co-marketing — joint webinars and partner summits: partnership mechanics live there, event execution here
- community-marketing — ongoing community programs; events can seed or serve one
- public-relations — podcast guesting and press at events
- lead-magnets — gated replays and event content as magnets
- emails / sms — the reminder and follow-up sequences themselves
- cold-email — pre-event meeting-booking outreach
- revops — routing, scoring, and source-tagging event leads
- attribution — measuring multi-touch event influence honestly
FAQ
What does the events skill do?
When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences. Also use when the user mentions 'event marketing,' 'field marketing,' 'run a webinar,' 'webinar funnel,' 'show-up rate,' 'should we sponsor,' 'sponsor a conference,' 'trade show booth,' 'booth strategy,' 'event ROI,' 'badge scans,' 'event follow-up,' 'speaking slot,' 'CFP,' 'conference talk,' 'host a dinner,' 'user conference,' or 'virtual summit.' Covers all four roles: hosting, sponsoring/exhibiting, speaking, and attending. For product launch moments, see launch. For the partnership side of joint webinars, see co-marketing. For ongoing community programs, see community-marketing. For podcast appearances, see public-relations. For the email sequences themselves, see emails.
How do I install events?
Run npx skills add https://github.com/coreyhaines31/marketingskills --skill events in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/events/ (personal) or .claude/skills/events/ (project).
Which AI agents can use events?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is events safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains events?
It is published by coreyhaines31 in coreyhaines31/marketingskills. It has 23,321 recorded installs.
More from coreyhaines31/marketingskills
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
copywriting
coreyhaines31/marketingskills
When the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "hero section copy," "this copy is weak," "this sounds like AI," "AI slop," "make it sound human," or "help me describe my product." Drafts never use AI tells like "it's not X, it's Y" reveals, "no X, no Y, no Z" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers. Claims must be supportable, and a declined claim names the evidence that would unlock it. Diagnoses the input first (blank brief, real voice, or point edit) and changes only what it calls for.
marketing-psychology
coreyhaines31/marketingskills
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.
content-strategy
coreyhaines31/marketingskills
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.
ai-seo
coreyhaines31/marketingskills
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' 'WebMCP,' 'do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' 'how do LLMs see our brand,' 'LinkedIn for AEO,' or 'AI citation format shift.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see sch
programmatic-seo
coreyhaines31/marketingskills
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," "templated landing pages," or "which CMS for pSEO." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
Popular marketing & seo skills
reddit-automation
flowkit-labs/skills
Find Reddit threads where people are genuinely asking for what you offer, then draft short, genuinely helpful replies — disclosing your affiliation honestly and naming your product only when it truly answers the question. Two moves: discovery — scan the right subreddits for real needs (recommendation asks, expressed pain, competitor mentions) and rank the few threads where you can actually help; drafting — write from real experience, respect each community's self-promo rules, and keep a human in the loop to review and post. This markets on Reddit the honest way: contribute value, disclose who you are, never astroturf. Distilled from the playbook behind doany.ai's Reddit agent. Triggers on "find reddit opportunities", "reddit marketing", "reddit automation", "reply on reddit for my product", "reddit community engagement", "reddit lead gen", or any ask to turn Reddit threads into genuine, disclosed marketing replies.
twitter-automation
101-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
magentosh/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
twitter-automation
qu-skills/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet
product-launch-video
heygen-com/hyperframes
Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of a website route here too — the brief carries the show-it-as-is intent. Unclear → /hyperframes.
twitter-automation
skills-shell/superpowers
Automate Twitter/X with posting, engagement, and user management via inference.sh CLI. Apps: x/post-tweet, x/post-create (with media), x/post-like, x/post-retweet, x/dm-send, x/user-follow. Capabilities: post tweets, schedule content, like posts, retweet, send DMs, follow users, get profiles. Use for: social media automation, content scheduling, engagement bots, audience growth, X API. Triggers: twitter api, x api, tweet automation, post to twitter, twitter bot, social media automation, x automation, tweet scheduler, twitter integration, post tweet, twitter post, x post, send tweet