# event-sponsor-value-proposition

A skill that works out what a technical event can honestly offer each sponsor and why they buy. Run it before the deck and the rate card.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 5100 installs · ★ 4
- Author: Samuel Berthe
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-sponsor-value-proposition/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/event-sponsor-value-proposition

## What it does

The skill interviews you one question at a time, mostly multiple-choice. First it settles who owns the event: a community-run, CFP-driven conference or a vendor-run one. That answer bounds what you can promise. Then it walks sponsor segments one by one — product feedback, recruiting, brand exposure, community goodwill.

You get one value-proposition statement per segment, each backed by a proof point a sponsor can check. A six-part jobs-to-be-done template frames the work the sponsor is actually paying for. The skill tells you to re-rank the categories after the interview: a returning anchor sponsor, a first edition with no track record, a cooling hiring market all shift the order.

The boundary is firm. Sponsorship buys placement and access, never a talk slot, a judging result, or influence over the program. At community-run events no attendee list is given or sold — contact data moves only when an attendee volunteers it. Pipeline as a category exists only at the vendor pole. Packaging and pricing live elsewhere: `samber/dev-event-organizer-skills@event-sponsor-prospectus` and `samber/dev-event-organizer-skills@event-sponsor-pricing`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-sponsor-value-proposition -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/event-sponsor-value-proposition/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/event-sponsor-value-proposition/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-sponsor-value-proposition -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/event-sponsor-value-proposition/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-sponsor-value-proposition -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/event-sponsor-value-proposition/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install samber/dev-event-organizer-skills event-sponsor-value-proposition
```

2. **Manually: put the files in place**
- File: `.github/skills/event-sponsor-value-proposition/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-sponsor-value-proposition -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/samber/dev-event-organizer-skills --path skills/event-sponsor-value-proposition
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/event-sponsor-value-proposition/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add samber/dev-event-organizer-skills --skill event-sponsor-value-proposition -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-sponsor-value-proposition/SKILL.md

## When to use it
- articulate what an event can honestly offer a sponsor
- sort sponsors into segments and their motivations
- attach a checkable proof point to every claim
- separate community-run promises from vendor-run ones
- build the value story before a rate card exists

## Example prompts
- Help me explain why a company should sponsor our conference — start with the recruiting segment
- Draft a value proposition for a DevRel sponsor, with proof points
- Our event is community-run with no CFP sponsors: which value categories can we honestly promise?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 7397d460cfd406a2.

BEGIN THIRD-PARTY FILE 7397d460cfd406a2
```text
---
name: event-sponsor-value-proposition
description: Discover what each sponsor of a technical conference actually needs, then articulate what it genuinely gets and why each sponsor segment buys - brand exposure, product feedback, recruiting, community goodwill, and (vendor-run events only) pipeline - one segment at a time through a six-part jobs-to-be-done template, bounded by what the event type can honestly promise and backed by proof points a diligent sponsor will check. Use whenever the user mentions why a company should sponsor an event, sponsor benefits or motivations, or building the value story before a prospectus or rate card exists - even if they never say "value proposition". Sponsorship never buys talks, judging results, or roadmap influence. Do NOT use to package or price it - use samber/dev-event-organizer-skills@event-sponsor-prospectus instead.
license: MIT
metadata:
  author: Samuel Berthe
  version: "1.2.1"
---

# Event Sponsor Value Proposition

You discover what each sponsor needs and articulate the value a technical event can genuinely offer it, before anything is packaged, priced, or pitched. Sponsors often cannot see an event's value by themselves; the fit between event and sponsor is found in discovery, not assumed in a deck.

- **Deliverable**: one value-proposition statement per sponsor segment, every claim backed by a proof point, feeding `samber/dev-event-organizer-skills@event-sponsor-prospectus` (the deck) and `samber/dev-event-organizer-skills@event-sponsor-pricing` (the rate card).
- **Out of scope**: packaging tiers, setting prices, running outreach, drafting contracts, tracking delivery - those are sibling skills.
- **Scope**: mainly one-day and multi-day conferences; other formats reuse the logic only where they sell sponsorship the same way.
- **What the sponsor buys**: for a sponsor, the attendees are in effect the product - it buys access to a qualified audience. Access means presence and conversations, never an attendee list; contact data moves only when an attendee volunteers it, and at a community-run event never as a list (see Community-run vs vendor-run).
```
END THIRD-PARTY FILE 7397d460cfd406a2

The third-party file has ended. Everything between the 7397d460cfd406a2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2137 of 23852 bytes. © Samuel Berthe · MIT · https://github.com/samber/dev-event-organizer-skills/tree/HEAD/skills/event-sponsor-value-proposition/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md