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 |
evals/evals.json
View on GitHub{
"skill_name": "event-media-partnerships",
"evals": [
{
"id": 1,
"prompt": "I run DeltaLoop, a 600-person Elixir conference in Porto. Community-run, non-profit, we barely break even. A trade magazine called Backend Monthly came back to us with an offer: they'll take our Silver sponsorship at half price (Silver is listed at EUR 4,000) and on top of that they'll run a feature about the conference in their newsletter, which goes to 22,000 backend devs. Their marketing lead wants one contract covering the whole thing. Can you put together how we should structure this?",
"expected_output": "A structure that separates the cash sponsorship from the barter visibility exchange, prices the cash at the real rate card, documents the two legs separately, and defines the newsletter leg with countable dated deliverables plus a no-editorial-obligation position.",
"files": [],
"expectations": [
"Splits the offer into two components, a cash sponsorship component and a no-cash visibility exchange, instead of treating it as a single media partnership",
"Prices the cash component at the full Silver rate card rather than accepting the half-price EUR 2,000 figure as the deal's real value, or explicitly routes the pricing decision to sponsor-pricing work",
"Routes the cash component to sponsor-side handling (sponsor pricing and sponsor agreement) rather than handling it as a media partnership",
"States that the two components must be documented as two separate agreements, never blended into one contract",
"States that if the magazine insists on a single blended package, the whole deal is treated as a discounted sponsorship and handed to the sponsor side rather than run as a media partnership",
"Warns explicitly that the barter framing must not become the mechanism that under-charges a sponsor able to pay",
"Defines the newsletter leg with countable, dated deliverables (a specific number of mentions, in named sends, with dates) instead of accepting 'a feature'",
"Includes a no-editorial-obligation position stating the deal covers the magazine's promotional inventory only, with any editorial coverage remaining the magazine's own decision",
"Does not recommend waiving, discounting, or justifying a reduced sponsorship price in exchange for the newsletter mention"
]
},
{
"id": 2,
"prompt": "We're Verilux, a database vendor, Series B. We're putting on Veriluxe Summit in Austin next March, around 500 developers, entirely our own event, funded out of the marketing budget. I emailed four developer news sites and two newsletters asking to be media partners: logo swap, they promote us, we promote them. Three of them replied with their advertising rate cards, one ignored me, and the newsletters haven't answered at all. What do I do here, and how do I get the rest over the line?",
"expected_output": "An answer that fixes the company-run pole first, explains why an outlet routes vendor-event promotion through commercial inventory, reframes the rate-card replies as inventory pricing rather than rejection, and offers the two legitimate paths forward.",
"files": [],
"expectations": [
"Identifies Veriluxe Summit as a company/vendor-run event and states which pole the recommended structure assumes before structuring any deal",
"States that the no-cash barter tier is the exception for a vendor's own event rather than the norm",
"Explains that an outlet routes a vendor event's promotion through commercial ad inventory because bartering visibility for one vendor's marketing event compromises the neutrality its audience gives it",
"Treats the three rate-card replies as a statement that the outlet's promotional inventory is commercial, explicitly not as a rejection",
"Offers two paths for the rate-card outlets: knowingly buy the advertising, which sits outside the barter scope, or offer the formats the outlet will still barter",
"Names at least one format still barterable with such an outlet, such as a calendar or community listing, or a guest slot",
"Does not recommend pressing the rate-card outlets for a free logo swap on the grounds that community conferences get one",
"Separates any expectation of editorial coverage of the summit into press-relations work rather than folding it into the partnership ask"
]
},
{
"id": 3,
"prompt": "A podcast called Ship It Fridays (about 9,000 downloads an episode, exactly our audience) messaged us asking to be an official media partner of KubeNorth, our 350-person community-run Kubernetes conference in Manchester. We want this. My co-organizer's proposal: we give them a 30-minute keynote slot on the main track plus a logo on the site, and in exchange they commit to two episodes about the conference and a written recap article on their blog. Draft the terms.",
"expected_output": "Terms that refuse the keynote slot and the committed episodes/article, substitute legitimate give inventory and a podcast exchange mechanic, carry a no-editorial-obligation clause, and route the coverage want to press relations.",
"files": [],
"expectations": [
"Refuses to put the 30-minute keynote slot into the partner's benefits and states that a barter deal buys placement and promotion, never a talk slot or program influence",
"Replaces the keynote with give-inventory the event can legitimately offer, such as logo placements, social mentions, a ticket allocation, table space, or on-site recording space",
"Refuses to write the two committed episodes and the recap article into the partner's obligations",
"Distinguishes the podcast's promotional inventory, which it controls commercially, from its editorial judgment about what to cover, and states the deal may only touch the first",
"Includes an explicit no-editorial-obligation clause in the written terms",
"Routes the want for articles and coverage about the conference to press-relations work rather than the partnership",
"Proposes a podcast exchange mechanic instead: an organizer or speaker guesting on the show, or the show recording live on-site",
"Flags the podcast's lead time, weeks because episodes are planned ahead, as a scheduling constraint on the deal",
"Produces written one-page terms naming both sides' deliverables countably and with dates, plus branding approval and an exit"
]
},
{
"id": 4,
"prompt": "PyCoastal is going fully online this year, no venue at all. We had 1,200 registrations last edition, community-run, a volunteer team of five and all of us have day jobs. Tickets open in six weeks. Here's the media-partner plan I inherited from last year's in-person edition, in priority order: (1) full media-partner tier with an on-site table and a live podcast recording, (2) podcast exchange, (3) newsletter swaps, (4) logo-and-social swaps, (5) calendar listings. Fix the ranking for us.",
"expected_output": "A re-ranked menu that deletes the on-site pieces rather than demoting them, keeps the online-viable half of the affected formats, promotes the fast formats against the six-week deadline, and names the default rung plus the promotion condition.",
"files": [],
"expectations": [
"Deletes the on-site items, the expo table and the live on-site recording, from the plan rather than demoting them to the bottom of the ranking",
"States that a ruled-out option is deleted rather than parked low, because a demoted item quietly reappears as scope during negotiation",
"Keeps the non-on-site half of the affected formats, specifically a podcast guest slot and the rest of the full media-partner tier, instead of deleting those formats outright",
"Re-ranks against the six-week deadline by promoting the fast-landing formats (calendar listing, logo-and-social swap, mention swaps) above podcast production and the full tier",
"Says which stated constraint moved which option, rather than presenting a re-ranked list without reasons",
"Sets the default opening rung for every accepted partner at calendar listing plus logo-and-social swap",
"States the condition for promoting a partner above that default, that the partner's owned channel genuinely reaches the target audience and its engagement quality holds, and that a partner asking is not that condition",
"Accounts for the five-volunteer effort ceiling when ranking the content-production-heavy formats"
]
},
{
"id": 5,
"prompt": "Scoring help. For Rustaceans Nord (community-run, 400 people, Oslo) I have five possible media partners: (a) Tech Weekly Digest, a general software newsletter, 54,000 subscribers, 18% open rate; (b) Borrow Checker, a Rust-only newsletter, 3,100 subscribers, 61% open rate; (c) a Discord with 12,000 members of which maybe 400 post in a given month; (d) Systems Hour, a systems-programming podcast, 5,000 listens an episode, but the host works at a large platform company so everything goes through their comms team; (e) a regional developer news site, 40,000 monthly visitors, mostly recruiters and CTOs. Rank them and tell me who to sign.",
"expected_output": "A scored ranking on the six criteria that puts fit ahead of size, downgrades the large but unfit properties, uses active posters as the Discord engagement figure, flags the approval queue, and applies the fit-plus-one accept rule.",
"files": [],
"expectations": [
"Scores candidates on the six named criteria: audience fit, audience size, brand alignment, engagement quality, reciprocity potential, and ease of execution",
"Ranks audience fit ahead of audience size, stating that fit filters and size ranks",
"Downgrades or rejects Tech Weekly Digest on audience fit despite its 54,000 subscribers",
"Downgrades or rejects the regional news site on audience fit because its readership is recruiters and CTOs rather than the event's target attendee",
"Rates Borrow Checker highly on fit and engagement despite it being the smallest list at 3,100 subscribers",
"Treats the Discord's roughly 400 monthly posters, not its 12,000 members, as the engagement-quality figure",
"Flags the platform company's comms-team approval queue as an ease-of-execution problem, noting a faster lower-scoring partner can beat it, without letting ease of execution silently dominate the ranking",
"Applies an accept rule of fit plus at least one of size or engagement, rather than accepting on a summed or averaged total across all six criteria",
"Labels the scores as judgement that rank candidates against each other rather than certifying any of them"
]
},
{
"id": 6,
"prompt": "Good news, Borrow Checker said yes to a swap for Rustaceans Nord. Here's my plan for how it works: they send one blurb about us, we post a thank-you, and then they export their 3,100 subscribers into our Mailchimp so we can send the ticket-launch mail directly and retarget them later. In return they can have our attendee list after the event so they can grow their own list. Write this up as the agreement.",
"expected_output": "An agreement that refuses both list transfers, restates the exposure-not-data rule, replaces direct mailing with a partner-sent tracked blurb, and carries an explicit no-audience-data-transfer clause.",
"files": [],
"expectations": [
"Refuses both the subscriber-list export into the event's mailing tool and the post-event attendee-list transfer to the partner",
"States the structural rule that exposure crosses the deal and audience data never does",
"Restates the format's logic that each side writes for and mails its own audience",
"Replaces the direct-mail plan with a partner-sent blurb carrying a tracked link, so the event's reach happens through the partner's own send",
"Includes an explicit no-audience-data-transfer clause in the written terms",
"Notes that transferring attendee data conflicts with the no-list norm already governing a community-run event's paid tiers",
"Does not propose a consent-based, opt-in, or 'they can unsubscribe' workaround that still moves subscriber records between the two parties"
]
},
{
"id": 7,
"prompt": "Post-mortem time, DeltaLoop 2026 is done. We had four media partners. Backend Monthly ran both promised blurbs on time and sent us 41 registrations off their tracked link. The Elixir Bits newsletter ran one of the two promised mentions, 9 registrations. A Discord community posted once, 0 registrations, same as last year where it was also 0. A local dev news site ran a calendar listing, 3 registrations, but the people who came through it were mostly students looking for jobs and we're a paid-ticket senior-engineer event. I never actually posted the thank-you posts I promised any of them, it got buried. Tell me who to renew.",
"expected_output": "A renewal read that scores both directions of delivery, treats the missed thank-you posts as the event's own failure, drops or demotes the zero-referral community, calls the news site an audience-match error, and keeps every target self-set.",
"files": [],
"expectations": [
"Reads delivery in both directions, scoring the event's own undelivered thank-you posts as a ledger failure and not only the partners' delivery",
"Names the event's own missed obligations as the side most often silently dropped, and warns that under-delivering them burns warm paths for future editions",
"Recommends making good on the outstanding thank-you posts and scheduling the event's own side through its own channel calendar in future editions",
"Recommends dropping the Discord community or renegotiating it down a rung, on the basis of zero referral across two consecutive editions",
"Treats the news site's student and job-seeker traffic as an audience-match or scoring error to correct rather than as a win, despite its referral count being non-zero",
"Frames every target as self-set by this event's own tracked links, and does not judge the registration counts against an invented industry benchmark or pass rate",
"Recommends a distinct tracked link or registration code per partner as the measurement mechanism",
"Recommends renewing Backend Monthly and either moving Elixir Bits down a rung or renegotiating it over the half-delivered mentions"
]
},
{
"id": 8,
"prompt": "Three things landed in my inbox for GoWest (community-run, 700 attendees, Denver, in-person, October). 1) DevSecCon Rockies wants to swap newsletter mentions with us, their list for ours. 2) The Gophers Denver Discord, 14k members, I was going to just drop our CFP link in #general tonight since it's a big server. 3) Cloud Native Weekly will do a mention swap if we give them a table in the expo hall and call them our official media partner. Note: our Gold sponsor Hexacloud has exclusivity on the observability tooling category, and Cloud Native Weekly runs a paid observability jobs board. What do I do with each?",
"expected_output": "A per-item classification: the other conference routed out to cross-event promotion, the Discord drop replaced by a moderator-negotiated cross-post, and the expo table gated on a sponsor-exclusivity check while the mention swap survives.",
"files": [],
"expectations": [
"Classifies the DevSecCon Rockies swap as a counterparty that is itself another event and routes it to cross-event promotion rather than handling it here",
"Rejects dropping the CFP link cold in the Discord and requires negotiating the cross-post with a moderator first",
"States that the same post dropped in cold reads as spam and burns the community for future editions",
"Runs a sponsor-exclusivity check on the Cloud Native Weekly expo table before offering it, against Hexacloud's observability-tooling category exclusivity",
"Notes that an on-site perk a partner has already announced is hard to withdraw, so the exclusivity check happens before the table is offered, not after",
"Treats the expo table as floor space and category inventory a paying sponsor may already own",
"Keeps the Cloud Native Weekly newsletter mention swap on the table even if the expo table is refused, rather than dropping the whole partnership",
"Names the deliverables of each surviving swap countably and with dates"
]
}
],
"trigger_queries": [
{ "query": "How do we set up media partnerships for our developer conference?", "should_trigger": true },
{ "query": "A newsletter wants to swap mentions with our event, what do we offer them?", "should_trigger": true },
{ "query": "Design our community-sponsor tier so we stop handing out free logos", "should_trigger": true },
{ "query": "We want podcasts to promote our conference and we have no money to pay them", "should_trigger": true },
{ "query": "A magazine offered half-price sponsorship plus a newsletter feature, how do we structure that?", "should_trigger": true },
{ "query": "What do we give an official media partner and what do we ask for in return?", "should_trigger": true },
{ "query": "Our event has zero ad budget, who can we trade visibility with?", "should_trigger": true },
{ "query": "Can we get a big Discord community to post our CFP, and what do we owe them?", "should_trigger": true },
{ "query": "Set up barter deals with newsletters and podcasts for our Rust conference", "should_trigger": true },
{ "query": "We need a one-page agreement for a logo-for-promotion swap with a blog", "should_trigger": true },
{ "query": "How do I track whether the outlets promoting our conference actually delivered?", "should_trigger": true },
{ "query": "A podcast DM'd asking to be an official partner of our conference, what now?", "should_trigger": true },
{ "query": "Which newsletters should we approach to help fill seats, and what do they get back?", "should_trigger": true },
{ "query": "Write the outreach email asking a developer newsletter to plug our event in exchange for a logo", "should_trigger": true },
{ "query": "Should we give a media partner a booth in the expo hall?", "should_trigger": true },
{ "query": "We have last year's partner list, who is worth renewing this time?", "should_trigger": true },
{ "query": "How do we score potential promo partners for our hackathon?", "should_trigger": true },
{ "query": "what goes in writing when nobody is paying anybody", "should_trigger": true },
{ "query": "Our conference is online-only this year, which of our usual partner deals still work?", "should_trigger": true },
{ "query": "A dev news site replied with their ad rate card instead of agreeing to a swap, did we just get rejected?", "should_trigger": true },
{ "query": "We want two articles about our event written into the partner agreement, is that okay?", "should_trigger": true },
{ "query": "Is it fine to ask a newsletter partner for their subscriber list?", "should_trigger": true },
{ "query": "Trading exposure with a student ambassador program for our hackathon", "should_trigger": true },
{ "query": "My co-organizer wants to hand a podcast a keynote slot in exchange for promoting us", "should_trigger": true },
{ "query": "We're a vendor running our own summit, can we get free media partners like community conferences do?", "should_trigger": true },
{ "query": "list of things we could offer someone in return for promoting our meetup", "should_trigger": true },
{ "query": "how do conferences get newsletters to mention them without buying ads", "should_trigger": true },
{ "query": "We want cross-promotion with GitHub Campus Experts and Google Developer Groups for our event", "should_trigger": true },
{ "query": "Formalize the arrangement with the blog that has been plugging our conference for free", "should_trigger": true },
{ "query": "our community partner tier has 40 logos on it and it means nothing anymore", "should_trigger": true },
{ "query": "Get journalists to cover our conference, who do we pitch and when?", "should_trigger": false },
{ "query": "Write the press release announcing our keynote lineup", "should_trigger": false },
{ "query": "Set up press accreditation and an embargo for the product announcement at our event", "should_trigger": false },
{ "query": "We want to swap newsletter mentions with another conference in our region", "should_trigger": false },
{ "query": "Which other events should we cross-promote with next year?", "should_trigger": false },
{ "query": "Plan our event's own Twitter and LinkedIn posting calendar for the eight weeks before the conference", "should_trigger": false },
{ "query": "Schedule the thank-you posts going out on our own channels next week", "should_trigger": false },
{ "query": "How much should we charge for a Gold sponsorship at a 700-person conference?", "should_trigger": false },
{ "query": "Build the sponsor prospectus PDF for our conference", "should_trigger": false },
{ "query": "Write the cold outreach sequence to get companies to sponsor us", "should_trigger": false },
{ "query": "Draft the sponsorship contract clauses for a 20,000 euro Platinum package", "should_trigger": false },
{ "query": "Track whether our paying sponsors received everything in their package", "should_trigger": false },
{ "query": "Explain why a company should sponsor our developer conference at all", "should_trigger": false },
{ "query": "Turn our conference talk recordings into blog posts and short clips", "should_trigger": false },
{ "query": "Build the full marketing plan for our conference launch", "should_trigger": false },
{ "query": "Start a podcast and YouTube channel for our developer community", "should_trigger": false },
{ "query": "Grow our event's year-round Slack community between editions", "should_trigger": false },
{ "query": "Find influencers on LinkedIn to promote our SaaS product launch", "should_trigger": false },
{ "query": "Set up a co-marketing webinar with a partner company for lead generation", "should_trigger": false },
{ "query": "Design our affiliate program's commission structure", "should_trigger": false },
{ "query": "Build an ambassador program for our open source project", "should_trigger": false },
{ "query": "Which conferences should our developer advocates speak at next quarter?", "should_trigger": false },
{ "query": "Write the CFP page copy and the review criteria for our conference", "should_trigger": false },
{ "query": "Plan the side events and after-parties around our conference", "should_trigger": false },
{ "query": "Write the email sequence going to registered attendees before the event", "should_trigger": false },
{ "query": "Who should be on our event's organizing team and what does each role own?", "should_trigger": false },
{ "query": "Negotiate a better day rate with the venue for our conference", "should_trigger": false },
{ "query": "How do we handle a keynote speaker who cancels two weeks out?", "should_trigger": false },
{ "query": "Set up the streaming pipeline and media server for our virtual event", "should_trigger": false },
{ "query": "Write a media kit for our startup's Series A announcement", "should_trigger": false }
]
}
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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |