Plan, run, sponsor, speak at, or get pipeline from events

Event Marketing

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Event Marketing cover

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.

---
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:

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill events -g -a claude-code
Claude Code (degit)npx degit coreyhaines31/marketingskills/skills/events#5b2c0007766c6a1cf1d53fd8fc73e979e0821022 ~/.claude/skills/events
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md11.9 KB
Read SKILL.md here
coreyhaines31/5b2c0001 file shown
SKILL.md
Show the full text132 lines

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 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:

  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 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.
  • 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
1---
2name: events
3description: "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."
4metadata:
5 version: 1.0.0
6---
7 
8# Event Marketing
9 
10You 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.
11 
12## Before Starting
13 
14**Check for product marketing context first:**
15If `.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.
16 
17Then establish, in one batch:
18 
191. **Which role?** Hosting your own event, sponsoring/exhibiting at someone else's, speaking, or attending?
202. **What outcome?** Pipeline/meetings, authority/brand, community, or content production? (Pick a primary — events that try to do everything measure nothing.)
213. **Who must be in the room?** The ICP segment, and roughly how many of them exist at this event.
224. **Budget and team** — money, and who can actually work the event.
23 
24## Pick Your Role
25 
26| You are… | Core motion | Depth |
27|---|---|---|
28| **Hosting** | Own the audience end to end — webinar, workshop, dinner, meetup, summit, user conference | This file + [webinar-funnel.md](references/webinar-funnel.md) for the flagship format |
29| **Sponsoring / exhibiting** | Buy access to someone else's audience — evaluate, negotiate, work the floor, follow up | [sponsorship-roi.md](references/sponsorship-roi.md) |
30| **Speaking** | Trade expertise for stage time — get booked, design the talk, compound the recording | [speaking.md](references/speaking.md) |
31| **Attending** | No booth, no stage — engineer meetings anyway | Section below |
32 
33Mixed roles are normal (sponsor + speak, attend + host a dinner). Plan each role's motion separately; they share the follow-up system.
34 
35## Which Events to Invest In (Portfolio First)
36 
37Before 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](references/event-portfolio-strategy.md).
38 
39- **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.
40- **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.
41- **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.
42- **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").
43 
44## The Universal Arc: 20% Event, 80% Before-and-After
45 
46The event itself is the smallest part of event marketing. Every format follows the same arc, and most failures are arc failures, not event failures:
47 
48**Before (where pipeline is actually made)**
49- Build the target list: who's attending that matches your ICP? (Attendee lists, speaker lists, "who's going" posts, past-year attendees.)
50- **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").
51- 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.
52 
53**During**
54- Optimize for *qualified conversations*, not raw contacts. One real conversation with an ICP buyer beats fifty badge scans.
55- 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.
56- Create content while there (see Content Arc below) — the event is a recording studio you already paid for.
57 
58**After (where pipeline is won or lost)**
59- **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).
60- 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.
61- Route to systems: CRM with event source tagging (→ **revops**), nurture for the not-nows (→ **emails**).
62 
63## Hosting: Choose the Format for the Job
64 
65| Format | Best for | Effort | Notes |
66|---|---|---|---|
67| **Webinar** | Lead gen + education at scale | Low-mid | The flagship repeatable format — full funnel in [webinar-funnel.md](references/webinar-funnel.md) |
68| **Workshop** | Product-qualified leads, activation | Mid | Hands-on beats presentation for conversion; smaller and deeper than a webinar |
69| **Dinner / small gathering** | Exec relationships, ABM accounts | Mid | 8–14 seats, no pitch, curated guest mix — the highest meetings-per-dollar format in B2B |
70| **Meetup series** | Local community, recurring presence | Mid | Consistency beats production value; hand hosting duties to community members over time (→ **community-marketing**) |
71| **Virtual summit** | List building via partner audiences | High | Multi-speaker = built-in distribution; every speaker promotes (→ **co-marketing** for the partner mechanics) |
72| **User conference** | Retention, expansion, category authority | Very high | Don't attempt before you have a community that would attend without being begged |
73 
74Two hosting rules that outrank format choice:
75 
76- **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.
77- **Recurring beats one-off.** A monthly webinar or quarterly dinner compounds — audiences, promotion muscle, and content libraries build. A single big event evaporates.
78 
79## Attending (No Booth, No Stage)
80 
81The zero-budget motion, and often the best ROI in the building:
82 
831. **Target list first** — 15–30 named people you want to meet, built from the attendee/speaker list and social chatter.
842. **Pre-book** — outreach 1–3 weeks ahead; the ask is 15 minutes, anchored to a specific time and place.
853. **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](references/sponsorship-roi.md)).
864. **Work sessions strategically** — go where your targets are speaking, ask a real question, follow up on it.
875. Same 24–48h follow-up discipline as every other role.
88 
89## The Content Arc: Every Event Is a Content Engine
90 
91Events produce your highest-proof content — capture it deliberately:
92 
93- **Record everything you're allowed to record.** Talks, webinars, panels. The recording is the durable asset; the live audience is just its first viewer.
94- **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.
95- Slice the recording: clips (→ **video**), a recap post per session (→ **content-strategy**), pull-quotes for social (→ **social**), proof points for sales (→ **sales-enablement**).
96- Photograph/collect social proof: testimonials captured at the event are the most natural you'll ever get.
97 
98## Measurement: Pipeline, Not Applause
99 
100| Metric tier | Examples | Verdict |
101|---|---|---|
102| **Vanity** | Registrations, badge scans, foot traffic, impressions | Track, never optimize for, never report as success |
103| **Real** | Qualified conversations, meetings booked, opportunities created, pipeline influenced | The actual scoreboard |
104| **Decisive** | Cost per qualified meeting, cost per opportunity, closed-won influenced | What decides whether you do it again |
105 
106- Compare cost-per-qualified-meeting against your other channels (ads, outbound) — that's the go/no-go math, worked through in [sponsorship-roi.md](references/sponsorship-roi.md).
107- 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**).
108- Judge a recurring event program on a 2–3 event trend, not one instance — the first run of anything underperforms its steady state.
109 
110## Common Mistakes
111 
112- **Sponsoring for "brand awareness" with no conversation target.** If nobody owns a meetings number, the booth is décor.
113- **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.
114- **Optimizing show-up rate after picking a topic nobody wants.** Reminder cadence can't save weak demand — fix topic and promise first.
115- **One-off thinking.** Budget for the third instance before running the first.
116- **Doing the event, skipping the recording.** Full production effort, zero durable assets.
117- **Counting badge scans as leads.** A scan is a person who walked slowly. Qualify before it enters the pipeline.
118- **Writing off "events" after one bad conference.** Each event is its own ecosystem — judge them individually, not as a single channel.
119- **Chasing the biggest conferences.** Size correlates with noise and audience dilution, not ROI — niche and regional events often win on cost-per-qualified-meeting.
120 
121## Related Skills
122 
123- **launch** — the event is a launch moment (announcement, Product Hunt, go-live)
124- **co-marketing** — joint webinars and partner summits: partnership mechanics live there, event execution here
125- **community-marketing** — ongoing community programs; events can seed or serve one
126- **public-relations** — podcast guesting and press at events
127- **lead-magnets** — gated replays and event content as magnets
128- **emails** / **sms** — the reminder and follow-up sequences themselves
129- **cold-email** — pre-event meeting-booking outreach
130- **revops** — routing, scoring, and source-tagging event leads
131- **attribution** — measuring multi-touch event influence honestly
132 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
SkillSet up the Discord channel/discord:configure — Discord Channel Setupanthropics/claude-plugins-official · by anthropicsSet up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks "how do I set this up" or "who can reach me," or wants to check channel status.★ 37.6k GitHub starsSkillRead Discord for financial research using opencliDiscord Skill (Read-Only)himself65/finance-skills · by himself65Read Discord for financial research using opencli (read-only). Use this skill whenever the user wants to read Discord channels, search for messages in trading servers, view guild/channel info, monitor crypto or market discussion groups, or gather financial sentiment from Discord. Triggers include: "check my Discord", "search Discord for", "read Discord messages", what's happening in the trading Discord", "show Discord channels", "list my servers", Discord sentiment on BTC", "what are people saying in Discord about AAPL", monitor crypto Discord", any mention of Discord in context of reading financial news, market research, or trading community discussions. This skill is READ-ONLY — it does NOT support sending messages, reacting, or any write operations.★ 3.3k GitHub starsSkillApply Russell Brunson's Expert Secrets framework to buildguia-matthieu/clawfu-skills · by guia-matthieuApply Russell Brunson's Expert Secrets framework to build a mass movement around expertise — create a charismatic leader persona, design a new-opportunity offer, craft belief-breaking stories, and structure a Perfect Webinar that converts. Use when: positioning as an expert to monetize knowledge, creating an online course or coaching program, designing a webinar sales presentation, building a tribe with an identity and cause, crafting an Epiphany Bridge origin story, or packaging expertise into a value ladder.★ 151 GitHub starsSkillWrites Reddit, Product Hunt, Hacker News , Indie Hackers Community post generatormarcosmodly/marketing-skill · by marcosmodlyWrites Reddit, Product Hunt, Hacker News (Show HN), Indie Hackers (Show IH), dev.to (#showdev), Discord, Slack, and Telegram posts that follow each community's actual rules. Researches that specific subreddit's or site's rules and what currently works there live, verifying each source is about the named target, then gives a plain Go/No-Go and only drafts if the post is welcome, written to read like a person wrote it and in the platform's own format (Slack mrkdwn, Telegram HTML). For Discord, Slack, and private Telegram groups, which have no public rules page, it asks the user for the rules instead of guessing. Use when the user wants to post or promote something in a subreddit, launch on Product Hunt, write a Show HN or Show IH, post on dev.to, or share in a Discord server, Slack workspace, Telegram channel or group, or any other rules-driven community or forum. Not for LinkedIn, X, Instagram, or Facebook posts.★ 42 GitHub starsSkillRead your YouTube audience from the comments: pullYouTube Audience Insightssergebulaev/youtube-skills · by sergebulaevRead your YouTube audience from the comments: pull commenters and top comments on any video, surface recurring questions and themes (content ideas), repeat commenters (superfans), sentiment, and which comments to reply to or pin. Also channel stats and niche trending, via the free official YouTube Data API. Triggers on "who commented on my video", "analyze my comments", "audience insights", "trending on YouTube". Not for writing a community post (use yt-community-post-writer).★ 36 GitHub starsSkillText updates, polls, image-caption postsYouTube Community Post Writersergebulaev/youtube-skills · by sergebulaevWrite YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer).★ 36 GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars