What problem does it solve? Third parties - user groups, sponsors, attendees - run parties, meetups, dinners, and workshops around your event's dates, often using your name and logo without asking. This Skill gives organizers a deliberate framework for deciding what to approve, what to list, what naming to permit, and how to route liability, instead of improvising at T-2 weeks. ## Core Features & Use Cases - Approval posture selection: Choose among doing nothing, self-registration listing, vetted application, or partnership agreement, with explicit promotion and deletion conditions keyed to your situation. - Naming and branding rules: Set one of four rungs from no name use to licensed co-branding, with exact reusable disclaimer sentences and real policies from SXSW, CES, and KubeCon. - Calendar deconfliction: Protect your published grid's key hours with protected windows, shared calendars, or a curated fringe guide, without ever moving your own sessions. - Liability routing: Name exposure categories (marks misuse, apparent endorsement, venue injuries, alcohol, personal data) and route each to counsel or the mark holder without stating legal rules. - Use Case: A user group asks to run a "pre-conference" meetup with your mascot on the poster. The Skill walks you through refusing the wording, supplying a non-affiliation sentence, checking sponsor exclusivity, and imposing code-of-conduct adoption as an approval condition. ## Quick Start Ask the assistant to decide whether a local user group can run a meetup the night before your conference and what they may call it.
