What problem does it solve? Event organizers often build press operations nobody needs, refuse journalists without published criteria, or improvise statements during incidents. This Skill decides whether an event should run a press function at all, then designs accreditation, media pages, embargo posture, on-site handling, and crisis communication grounded in real published policies from PyCon US, FOSDEM, DEF CON, SXSW, MWC, and others. ## Core Features & Use Cases - Press posture decision: Determines whether to run no press function, reactive contact only, a staged build, or a dedicated press function, based on whether any outlet covers the subject and whether registration needs earned coverage. - Two-lane accreditation policy: Drafts eligibility criteria, proof requirements, comp policies, caps, and refusal wording for editorial journalists and independent creators, with the creator lane held to an equal or stricter bar. - Embargo and announcement calendar: Pegs announcements to CFP, lineup, programme, on-sale, and wrap-up beats, and selects an embargo posture from honour-system sends to credential-gated distribution. - On-site and crisis handling: Produces the written recording rule, interview model, and a designated-spokesperson plan with holding statements separated from remedies. - Use Case: A 300-person community Go conference asks whether it needs a press page; the Skill finds no outlet covers the subject and registration is healthy, recommends no press function with PyCon US and FOSDEM as precedent, and routes residual incident exposure to the code-of-conduct skill. ## Quick Start Ask the Skill to design a press accreditation policy and media page for your developer conference, and answer its interview questions about audience, scale, and calendar beats.
