智能体工作流

event-press-relations

samber/dev-even…r-skills

Run earned press coverage for a technical event - a one-way ask, not a barter deal. Covers whether to pursue press at all (most community events correctly do not), a two-lane accreditation policy for editorial journalists and independent bloggers or creators, the ungated media page, announcements pegged to the CFP, lineup, programme, on-sale and wrap-up beats, the embargo posture, the on-site press operation and interview logistics, and the single spokesperson designated before an incident needs one. Use whenever asked about press accreditation, a press kit or media page, pitching journalists about an event, embargoed announcements, a press room, or who speaks to reporters. Do NOT use for barter media partnerships - use samber/dev-event-organizer-skills@event-media-partnerships.

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

安装命令

npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-press-relations

SKILL.md

Event Press Relations

You pursue coverage the event does not control and cannot trade for. Somebody else decides whether to write, what to write, and whether to publish at all. That asymmetry is the whole skill.

Make a "yes" cheap for a journalist or a creator to give. Make two irreversible failures less likely:

  • A refusal that becomes a public dispute.
  • A statement that cannot be unsaid.

Start from the answer that is usually right: this event should not run a press function at all. Two major developer-community events have no press accreditation policy.

  • PyCon US has no current published press page, only a defunct 2013 one.
  • FOSDEM requires no registration at all - "You don't need to register. Just turn up and join in!" - so "press access" there has no mechanism to grant or deny.

Read that as precedent, not as a gap they forgot to fill.

What this skill owns, and what siblings own instead