AI导哈

营销与写作

event-media-partnerships

samber/dev-even…r-skills

Set 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.

  • 5834 次安装
  • 4 星标
  • 收录于

安装命令

npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-media-partnerships

SKILL.md

Event Media Partnerships

You set up reciprocal visibility deals between a technical event and media or community properties that are not themselves events: newsletters, podcasts, online communities (Slack/Discord, developer-ambassador programs), blogs, and media outlets. The exchange is symmetric exposure for exposure: the event gives logo placement and mentions, the partner gives a newsletter blurb, a podcast slot, or a community post. No cash changes hands by default. Organizer guides name this as a distinct tier, not an ad-hoc favor:

  • DevOpsDays organizing guide, "Community Sponsor": "Used for media outlets and other conferences that are interested in cross-promotion with you... usually you will not ask them to provide cash."
  • MLH organizer guide: "Strategic/Media Partners... Community Partners... typically for free."

Four boundaries, drawn explicitly because the sourced guides blur at least one of them:

  • Earned coverage is not a partnership. "We ask a publication to cover us" is a one-way ask the event neither controls nor reciprocates - that is samber/dev-event-organizer-skills@event-press-relations (press kit, journalist targeting, accreditation, embargoes). This skill's deals are two-way exchanges the event initiates and structures. MLH's own guide lists both in one breath without separating them - draw the line for the user every time.
  • Another conference is not a media property. The same newsletter-swap mechanics with another event's newsletter belong to samber/dev-event-organizer-skills@cross-event-promotion - settled boundary, both sides. This skill takes the "media outlets" half of DevOpsDays' tier phrase; that sibling takes "other conferences".
  • Cash reclassifies the deal. If a candidate deal mixes cash and barter (a discounted paid tier plus a reciprocal mention), split it: the cash component goes to the sponsor block (samber/dev-event-organizer-skills@event-sponsor-value-proposition and its siblings), and only the barter component stays here. Never let this skill's simplicity under-charge a sponsor who could pay.
  • The event's own channels are not this skill. Scheduling the event's own thank-you posts and amplification belongs to samber/dev-event-organizer-skills@event-social-media; a media partnership is inbound amplification from someone else's channel.

Like cash sponsorship in this collection, a barter deal buys placement and promotion - never a talk slot, editorial coverage, or program influence.

Every target in Measurement is self-set: what a newsletter swap or podcast exchange returns in registrations is whatever this event's own tracked links measure. If you can browse the web, check 2-3 live media-partner pages of comparable conferences before locking a public partner tier.

Every ranking below is a default, not a law: it shifts with context and with who executes it. After the interview, re-rank the format menu against what you know about this organizer. Each of the following overturns a default rung:

相关 Skills

dev-event-hiringsamber/dev-even…r-skillsEmployer-side hiring for tech-event-organizing roles - producer/manager/coordinator, and the community-manager-shaped end of the field. Calibrates the scorecard to operating context (in-house, agency, non-profit/community, or a standing conference business), builds the loop from the general event-planner sequence plus CMX's five-competency set and paid mini-audit work sample, flags the "one hire owns sponsorship, content and production" consolidation pattern seen in postings, sources candidates from general event-industry boards since no tech-specific one exists, and gates compensation on named sources (PCMA, BLS, Glassdoor) rather than a blended figure. Use when the user asks how to hire an event producer or manager, write a posting, design a loop, or hire an event community manager. Do NOT use for candidate prep (samber/dev-event-organizer-skills@dev-event-career) or team org design (samber/dev-event-organizer-skills@event-team-structure).设计与多媒体5882tech-podcast-youtube-channelsamber/dev-even…r-skillsRun an organizer's own standing podcast or video channel as a cross-edition media property - whether to sustain a channel at all, the cadence commitment and its named owner in the quiet months, guest sourcing from the speaker pool outward, the two-way feed with the event cycle, and the wind-down or handover when organizers change. Use whenever the user mentions starting a conference podcast or YouTube channel, publishing between editions, where episode guests come from, who owns the show when an organizer leaves, or closing one down - even if they never say "podcast". Do NOT use for cutting one edition's talk recordings into clips - use samber/dev-event-organizer-skills@event-content-repurposing instead.营销与写作5882hackathon-brief-designsamber/dev-even…r-skillsWrite the hackathon challenge document teams read before they build - problem statements sized to the time box, thematic challenge tracks, the published rules and eligibility text, the submission-artifact checklist, sponsor-challenge framing, and naming (never weighting) the evaluation categories. Use whenever the user mentions a hackathon brief, challenge or track prompts, hackathon rules or eligibility, submission guidelines, or turning a sponsor's API into a challenge - even if they never say "brief". Challenge tracks here are thematic categories a team enters, not parallel session streams. Do NOT use for rubric weights and judging mechanics - use samber/dev-event-organizer-skills@hackathon-judging instead.设计与多媒体5879event-talk-selectionsamber/dev-even…r-skillsRun the review and selection process on CFP submissions a technical event already collected - committee composition, how blind review executes (platform hiding versus a dedicated anonymizer role) and what it cannot fix, scoring rubrics, multi-round score-to-shortlist-to-program-fit cascades, conflict-of-interest recusal, diversity and first-time-speaker balancing, acceptance-rate management, and accept/decline/waitlist communication. Use whenever the user mentions a program committee, a talk rating grid, blind CFP review, choosing which submitted talks make the programme, reviewer conflicts of interest, or acceptance and rejection emails - even if they never say "selection". Do NOT use to design the call itself - use samber/dev-event-organizer-skills@event-cfp-design.测试与安全5875event-landing-pagesamber/dev-even…r-skillsBuild a technical event's public front door and the small site around it - the page shape for the funding model (a ticketed event's single-CTA hero, or a free event's stats hero with no registration to sell), the section set, a date-gated CTA state machine so Propose renders only during the CFP window and Register only inside the registration window, the accessibility target, and the event structured data. Use whenever asked to build or review a conference, meetup or hackathon website, write the event home page, decide what the page should show before tickets go on sale, or run a pre-launch check on an event site. Do NOT use to set prices or positioning - use samber/dev-event-organizer-skills@event-ticket-pricing or samber/dev-event-organizer-skills@event-positioning.测试与安全5872event-date-selectionsamber/dev-even…r-skillsPick the date a technical event runs on - the decision every other plan hangs off. Covers weekday versus weekend from whose calendar the audience lives on (working professionals versus students), seasonality and the calendars constraining the real audience, competing and anchor events scanned for both conflict and deliberate piggybacking, candidate windows negotiated against venue availability instead of one date fixed first, and the announcement gate on payment handling existing. Use whenever asked to choose an event date, pick a conference weekend, check date conflicts with other events, decide how far ahead to announce, or resolve a clash with a competing event. Do NOT use for the work-back schedule from that date - use samber/dev-event-organizer-skills@event-planning-timeline.智能体工作流5871