samber/dev-event-organizer-skills / skills/event-media-partnerships
event-media-partnerships
VerifiedSet up barter media and community partnerships for a technical event - visibility-for-visibility deals with newsletters, podcasts, online communities and developer-ambassador programs, where no cash changes hands. Covers deal classes, partner types, the exchange format (calendar listing, logo-and-social swap, newsletter mention swap, podcast exchange, full media-partner tier), the deal terms, and both sides' delivery tracking. Use whenever asked to find media partners, set up a community-sponsor tier, trade newsletter mentions or podcast slots for event visibility, or formalize a logo-for-promotion deal. Do NOT use for earned press - use samber/dev-event-organizer-skills@event-press-relations - or swaps with other events - use samber/dev-event-organizer-skills@cross-event-promotion.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.0 KB |
| evals/evals.json | config | 23.2 KB |
| references/deal-terms-and-delivery.md | markdown | 4.2 KB |
| references/partner-types-and-scoring.md | markdown | 4.4 KB |
references/deal-terms-and-delivery.md
View on GitHub# Deal terms and delivery tracking
## The one-page agreement
A media partnership rarely needs a lawyer, but it always needs a written page - barter deals fail by fuzziness, not by breach.
1. **Parties and edition** - the event edition (named, dated) and the partner property. Scope one edition at a time; renewal is a deliberate read, not an auto-rollover.
2. **The event delivers** - each placement named and countable: logo on which pages/screens, how many social mentions on which channels, table or recording space (only after the sponsor-exclusivity check), ticket allocation if any.
3. **The partner delivers** - equally countable: which calendar listing, how many newsletter mentions in which sends, which episode or AMA, by when.
4. **Dates** - a delivery date per item on both sides, phased against the announcement and ticket-sale calendar.
5. **No editorial obligation** - state it explicitly: the partnership covers promotional inventory only; any editorial coverage the partner chooses to run is its own decision, outside the deal. This clause is what keeps barter from shading into paid editorial.
6. **No audience data transfer** - each side mails and posts to its own audience; no list, subscriber data, or attendee data crosses the deal ("each keeps own leads" - a co-marketing convention, consistent with the community-run no-list norm).
7. **Branding approval** - each side approves the other's use of its name and logo before first publication.
8. **Exit** - either side may withdraw before delivery starts with notice; delivered items stay delivered.
## Worked example - deal definition
**Good** (countable, dated, symmetric):
> RustFest Lyon 2027 × "Crustacean Weekly" newsletter (media partner, newsletter mention swap).
> Event delivers: logo in the Community Partners block of the event site until 2027-06-30; two thank-you posts (announcement week, event week) on the event's social accounts.
> Partner delivers: one 80-word blurb with tracked link in the first send after ticket launch (week of 2027-02-01); one reminder line in the send before early-bird close (2027-03-15).
> No editorial obligation either side; no list exchange; both sides approve logo use before first publication.
**Bad** (the unbounded logo wall):
> Crustacean Weekly becomes a media partner of RustFest. We'll add your logo to the site and you'll help promote the event.
Nothing is countable, nothing is dated, "help promote" can be satisfied by silence, and the event's own obligations are open-ended.
## The delivery ledger
One row per promised item, both directions, kept from signature to post-event read:
| Partner | Direction | Item | Due | Delivered | Evidence |
| ----------------- | --------------- | -------------------------------- | ---------- | ---------- | -------- |
| Crustacean Weekly | partner → event | Launch-send blurb + tracked link | 2027-02-01 | 2027-02-03 | send URL |
| Crustacean Weekly | event → partner | Announcement-week thank-you post | 2027-02-05 | - | |
Evidence is a URL or screenshot per item. The event-direction rows are the ones most often silently dropped - review the ledger on the same cadence as the sponsor-fulfillment matrix, and read it in full before any renewal conversation.
## Splitting a mixed deal
When a candidate offers cash plus barter (e.g. "half-price Silver plus a newsletter feature"):
1. Price the cash component at the real rate card - `samber/dev-event-organizer-skills@event-sponsor-pricing`'s numbers, not an improvised discount. Route it through the sponsor block as a normal (possibly negotiated) sponsorship.
2. Structure the barter component here as its own deal with its own countable deliverables - never as a vague sweetener inside the sponsor contract.
3. Keep the two documents separate: the sponsor agreement carries the cash terms; this skill's one-pager carries the swap. A single blended document hides whether either side delivered, and lets the barter leg silently justify the discount.
If the partner only wants the deal as one blended package, treat the whole thing as a discounted sponsorship and hand it to the sponsor block - the barter framing must never be the mechanism that under-charges a sponsor who could pay.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |