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.

MITAuto-check passedMarketing & SEO

Install Events

skills CLI
$ npx skills add coreyhaines31/marketingskills --skill events -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coreyhaines31/marketingskills events --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/events .claude/skills/events && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
events
GitHub stars
54k
Token cost
~3k tokens
SKILL.md length
1,486 words
Files
6 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 4 steps: Which role? Hosting your own event,… → What outcome? Pipeline/meetings,… → Who must be in the room? The ICP… → …
  • Get pipeline from events — webinars
  • SKILL.md covers Before Starting, Pick Your Role, Which Events to Invest In… and The Universal Arc: 20% Event,…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Events is an agent skill from coreyhaines31/marketingskills. 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…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/evals.json`, `references/event-portfolio-strategy.md` and `references/speaking.md`).

It sits in Marketing & SEO, covering Email marketing and Product launch strategy. The repository describes itself as: Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. The licence is MIT.

When your agent uses it

  • Get pipeline from events — webinars
  • Virtual summits
  • User conferences
  • The user mentions event marketing

Example prompts

  • “event marketing,”
  • “field marketing,”
  • “run a webinar,”
  • “/events”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Which role? Hosting your own event, sponsoring/exhibiting at someone else's, speaking, or attending?
  2. What outcome? Pipeline/meetings, authority/brand, community, or content production? (Pick a primary — events that try to do everything…
  3. Who must be in the room? The ICP segment, and roughly how many of them exist at this event.
  4. Budget and team — money, and who can actually work the event.

What it can do on your machine

Read from SKILL.md and the folder at commit 1efedbc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Events loads about 3k tokens when it runs, and up to ~9.9k if it reads all its reference files. Until then it costs about 219 tokens; SKILL.md has 1,486 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~219
When it runs · the whole SKILL.md, loaded when a task matches
~3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coreyhaines31/marketingskills at commit 1efedbc, republished under its MIT licence (© coreyhaines31). 1,486 words, ~3,006 tokens.

Download SKILL.mdSave it as .claude/skills/events/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
events
description
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.
metadata.version
1.0.0

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:

  1. Which role? Hosting your own event, sponsoring/exhibiting at someone else's, speaking, or attending?
  2. What outcome? Pipeline/meetings, authority/brand, community, or content production? (Pick a primary — events that try to do everything measure nothing.)
  3. Who must be in the room? The ICP segment, and roughly how many of them exist at this event.
  4. Budget and team — money, and who can actually work the event.

Pick Your Role

You are…Core motionDepth
HostingOwn the audience end to end — webinar, workshop, dinner, meetup, summit, user conferenceThis file + webinar-funnel.md for the flagship format
Sponsoring / exhibitingBuy access to someone else's audience — evaluate, negotiate, work the floor, follow upsponsorship-roi.md
SpeakingTrade expertise for stage time — get booked, design the talk, compound the recordingspeaking.md
AttendingNo booth, no stage — engineer meetings anywaySection 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

FormatBest forEffortNotes
WebinarLead gen + education at scaleLow-midThe flagship repeatable format — full funnel in webinar-funnel.md
WorkshopProduct-qualified leads, activationMidHands-on beats presentation for conversion; smaller and deeper than a webinar
Dinner / small gatheringExec relationships, ABM accountsMid8–14 seats, no pitch, curated guest mix — the highest meetings-per-dollar format in B2B
Meetup seriesLocal community, recurring presenceMidConsistency beats production value; hand hosting duties to community members over time (→ community-marketing)
Virtual summitList building via partner audiencesHighMulti-speaker = built-in distribution; every speaker promotes (→ co-marketing for the partner mechanics)
User conferenceRetention, expansion, category authorityVery highDon'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.
Show full SKILL.md (581 more words)Show less

Attending (No Booth, No Stage)

The zero-budget motion, and often the best ROI in the building:

  1. Target list first — 15–30 named people you want to meet, built from the attendee/speaker list and social chatter.
  2. Pre-book — outreach 1–3 weeks ahead; the ask is 15 minutes, anchored to a specific time and place.
  3. 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).
  4. Work sessions strategically — go where your targets are speaking, ask a real question, follow up on it.
  5. 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 tierExamplesVerdict
VanityRegistrations, badge scans, foot traffic, impressionsTrack, never optimize for, never report as success
RealQualified conversations, meetings booked, opportunities created, pipeline influencedThe actual scoreboard
DecisiveCost per qualified meeting, cost per opportunity, closed-won influencedWhat 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.
  • 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

© coreyhaines31, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in skills/events of coreyhaines31/marketingskills.

  • SKILL.md
  • evals/evals.json
  • references/event-portfolio-strategy.md
  • references/speaking.md
  • references/sponsorship-roi.md
  • references/webinar-funnel.md

Open the folder on GitHubat commit 1efedbc

Compare with similar skills

Events next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Events compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Events this skillcoreyhaines31/marketingskills54k—~3kAutomated safety check: PassMIT
Marketing Campaignaffaan-m/ECC277k1 repos~1.3kAutomated safety check: PassMIT
Webinar Marketingalirezarezvani/claude-skills28k—~3.3kAutomated safety check: PassMIT
Email Marketingsanqiufong/slides-from-anything1321 repos~861Automated safety check: PassApache-2.0
Memstack Marketing Webinar Scriptcwinvestments/memstack423—~3kAutomated safety check: PassProprietary
Campaign And Launch Planningsocial-media-skills/skills134—~1.7kAutomated safety check: PassMIT

Similar skills

  • Marketing Campaign

    affaan-m/ECC

    End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.

    277k GitHub starsUsed in 1 repo~1.3k tokens
    Marketing & SEOAuto-check passed
  • Webinar Marketing

    alirezarezvani/claude-skills

    When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand.

    28k GitHub stars~3.3k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Email Marketing

    sanqiufong/slides-from-anything

    A brand product-launch email — masthead with wordmark, hero image block, headline lockup with skewed-italic accent, body copy, primary CTA, and a specifications grid.

    132 GitHub starsUsed in 1 repo~861 tokens
    Marketing & SEOAuto-check passed
  • Memstack Marketing Webinar Script

    cwinvestments/memstack

    A skill your agent uses when the user says 'webinar script', 'webinar', 'live presentation', 'teach-to-sell', or needs a timestamped presentation script with slide notes, presenter cues, and replay…

    423 GitHub stars~3k tokensUpdated 14 days ago
    Marketing & SEOAuto-check passed
  • Campaign And Launch Planning

    social-media-skills/skills

    Plan and orchestrate a product launch or social media campaign end to end — the multi-week arc, channel by channel.

    134 GitHub stars~1.7k tokensUpdated 9 days ago
    Marketing & SEOAuto-check passed
  • Email Campaign

    mohitagw15856/pm-claude-skills

    Write and sequence multi-email nurture or launch campaigns. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~1k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

More from coreyhaines31/marketingskills

All 21 skills in this repo
  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Auto-check passed
  • Ab Testing

    coreyhaines31/marketingskills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

    54k GitHub starsUsed in 3 repos~3.1k tokens
    Auto-check passed
  • Referrals

    coreyhaines31/marketingskills

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    54k GitHub starsUsed in 2 repos~2.6k tokens
    Auto-check passed
  • Aso

    coreyhaines31/marketingskills

    When the user wants to audit or optimize an App Store or Google Play listing.

    54k GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed
  • Emails

    coreyhaines31/marketingskills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    54k GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed
  • Paywalls

    coreyhaines31/marketingskills

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

    54k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Categories

Questions about Events

What does Events 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. Events is an agent skill from coreyhaines31/marketingskills. 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.

When should I use Events?

Events fits situations like: get pipeline from events — webinars; virtual summits; user conferences; the user mentions event marketing.

How do I install Events in Claude Code?

Run `npx skills add coreyhaines31/marketingskills --skill events -a claude-code`. Or copy the skill folder (skills/events in coreyhaines31/marketingskills) into .claude/skills/events in your project. Claude Code loads it when a task matches its description.

How do I install Events in Codex?

Run `npx skills add coreyhaines31/marketingskills --skill events -a codex`. Or copy the skill folder (skills/events in coreyhaines31/marketingskills) into .agents/skills/events in your project. Codex loads it when a task matches its description.

Can I use Events in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coreyhaines31/marketingskills --skill events -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/events, .gemini/skills/events, .github/skills/events and .opencode/skills/events in your project.

What does Events need to run?

SKILL.md names no scripts, command-line tools or credentials: Events is instructions for the agent only.

Does Events access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Events safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Events use?

Events is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Events use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.9k tokens, read only when the agent opens those files.

What are the alternatives to Events?

Skills that share tags, products or a category with Events: Marketing Campaign (affaan-m/ECC, 277k stars), Webinar Marketing (alirezarezvani/claude-skills, 28k stars), Email Marketing (sanqiufong/slides-from-anything, 132 stars) and Memstack Marketing Webinar Script (cwinvestments/memstack, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Events?

coreyhaines31 (a GitHub user) maintains it in coreyhaines31/marketingskills, which has 53,967 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: coreyhaines31/marketingskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.