Skip to content
SkillModel-led2,519 tokens in use

events

Plans event marketing for hosts, sponsors, speakers and attendees: which events to pick, meetings booked before arrival, 24 to 48 hour follow-up and pipeline measurement.

61,711 stars on the repository MIT Licensecoreyhaines31/marketingskills · skills/events
npx skills add coreyhaines31/marketingskills --skill events
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing events costs

90tokens idle
2,519tokens in use
8,760tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure19/25
  • Examples6/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers