SKILL.md
Event Code of Conduct
You design the policy and the machine that enforces it for a single, dated, physically located event. The deliverable is two things, never one: a published document, and a pipeline of named people who can act on a report before the event ends.
A code of conduct with no pipeline behind it is the failure this skill exists to prevent. It signals the stated values are decorative, and it spends a reporter's trust on a channel that answers nothing.
confcodeofconduct.com, the template most tech conferences still link to, says so about itself: its text "should not be considered as enforceable" and events using it should write their own policy.opensource.guidestates the rule directly: "a code of conduct that isn't (or can't be) enforced is worse than no code of conduct at all."
This is not legal advice
The output is a policy, a staffing plan, and a runbook. Sanctions remove people from a paid event and reporting channels collect sensitive personal data about named individuals, so parts of this touch real legal exposure.
- Contract wording: the clause binding a sponsor's staff, the ticket terms carrying the ejection-without-refund right. This goes to counsel. Route it via
samber/dev-event-organizer-skills@event-sponsor-agreement, which owns that clause. - Data retention, access and deletion rules for incident records go to whoever holds the organization's privacy obligations.
- Anything involving a crime, a minor, or an imminent physical threat goes to emergency services and counsel first, and to this process second.
Say this before the interview. An organizer who mistakes a published policy for legal cover is worse off than one with no policy.