samber/dev-event-organizer-skills / skills/event-side-event-coordination
event-side-event-coordination
VerifiedApprove and coordinate third-party-run satellite events around a technical event - the vetting gate, calendar deconfliction against the published grid, name and logo usage rules, and the disclaimer stating what the main event does not vouch for. Use whenever a user group, sponsor or attendee wants to run a party, meetup, dinner, workshop or afterparty during the event's dates, when someone is already using the event's name on their own page, or when fringe events collide with the main programme - even if they never say "side event". Approving nothing is often the right answer; routes trademark and liability exposure to counsel. Do NOT use for the organizer's own evening programme - use samber/dev-event-organizer-skills@event-official-social-program instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 31.2 KB |
| evals/evals.json | config | 33.9 KB |
| references/application-and-criteria.md | markdown | 9.1 KB |
| references/naming-and-liability-wording.md | markdown | 9.5 KB |
references/application-and-criteria.md
View on GitHub# Application, criteria and the decision record
What a satellite organizer has to tell you, what you decide against, how the decision is recorded, and how it is withdrawn.
Contents: What the application collects · The published criteria set · The two cross-checks · The decision record · Withdrawal · Refusal wording, positive and negative
---
## What the application collects
Collect only what a criterion actually consumes. Every extra field is a reason for somebody not to submit, and the first menu's coverage axis is what you lose.
Recruiting-funnel research is the closest measured analogue for a gated submission process, not an event-specific figure. Tracked click-to-submission data finds each added minute of application complexity costs roughly a tenth of the candidate pool, and single-page forms complete at a meaningfully higher rate than multi-step ones. The numbers belong to hiring funnels, but the direction - friction costs submissions - is the same mechanism the approval-posture menu's coverage axis assumes.
1. **Who is responsible.** A named human and a way to reach them during the event, plus the organization behind them if there is one. Not a brand, not an email alias - a person who will answer on the evening the thing actually runs.
2. **What it is.** Format, expected headcount, whether it is ticketed and whether money changes hands.
3. **When and where.** Start and end, the venue with an address, and whether the venue is yours, theirs or a third party's.
4. **Who it is for.** Open to any attendee, invite-only, or restricted to a subset. An invite-only satellite is not disqualifying; an invite-only satellite presented as open is.
5. **What they intend to call it,** and every place your event's name or logo would appear - their page, tickets, signage, social posts.
6. **What they are asking you for.** A listing, a mention, permission to use the name, floor space, nothing at all. Most requests conflate several of these and the applicant has usually not separated them.
7. **Their accessibility and alcohol answers,** in one line each. You are not designing their event, but a satellite that is stairs-only or bar-only is one your own audience is excluded from, and you should know before you list it.
## The published criteria set
Write these before the first application. Criteria authored in response to a request are a judgment about that requester and will be read as one.
- **Overlap.** Does it run against a protected window of your published grid? This is the only criterion with a mechanical answer.
- **Audience.** Is it aimed at people who came for your event, or is your event a convenient crowd for something unrelated?
- **Responsibility.** Is there a named person, and does that person accept the code-of-conduct condition below?
- **Commercial shape.** Is it a recruiting event, a product pitch, a paid training course? None of these is automatically refused, but each is a different answer and your criteria should say which.
- **Conflict.** Does it collide with a sponsor's exclusivity, or with a paid inventory item somebody bought? See below.
- **Capacity to say no.** State in the criteria that you may refuse without giving reasons beyond these. An organizer who owes a reason for every refusal will approve everything.
Rank refusals by which criterion failed, not by who asked. Publish the criteria themselves, not the applications or the decisions.
A real vetted-application process runs on close to this shape at conference scale. The UN Ocean Conference's side-event guidelines ask any accredited organizer for an online proposal naming the event's thematic focus, speakers and contribution, judge it against how closely it relates to the conference's own theme, refuse duplicate proposals outright, and give priority to submissions made in partnership over single-organizer ones.
Unsuccessful applicants are never told they were refused: "the Conference Secretariat will review submissions and only notify those organizers whose events have been approved" (UN Ocean Conference side-event guidelines). The decision record below exists to avoid repeating that silence. A record kept only for the approved half tells you nothing about what you turned away or why.
## The two cross-checks
Both belong to siblings and neither is optional.
**Sponsor exclusivity.** `samber/dev-event-organizer-skills@event-sponsor-fulfillment` holds the signed agreements and the exclusivity clauses in them. A satellite run by a sponsor's direct competitor, listed on your page during your dates, is the same failure `samber/dev-event-organizer-skills@cross-event-promotion` names for comped booth space: in-kind value that occupies inventory somebody paid for. Check the clauses before approving, not before publishing.
**Code-of-conduct adoption.** Make it a condition of approval that the satellite adopts a code of conduct and names a contact for it. Hand `samber/dev-event-organizer-skills@event-code-of-conduct` the confirmed list so its scope clause can name the approved satellites explicitly.
That skill records MLH's scope covering "all hackathon venues, hackathon-related social events, hackathon-supplied transportation, and online interactions related to the event." (MLH, recorded in that skill's reference file), a breadth worth reading before assuming your own clause already reaches somebody else's venue. CNCF runs a lighter version of the same condition for the co-located events it runs alongside KubeCon + CloudNativeCon, tying it to registration rather than to a separate signature: "Your registration for or attendance at any CNCF event... indicates your agreement to abide by this policy and its terms," with compliance stated as non-negotiable (Linux Foundation Events, KubeCon + CloudNativeCon sponsor-hosted co-located event guide). That is a second working instance of the condition this skill imposes at approval.
The franchise case is the one where adoption is not yours to negotiate. The same record carries MLH's member-event obligation, "As an organizer of a Member Event, you are expected to adopt, make publicly available, and enforce the MLH Code of Conduct," (MLH). Where your event runs under an umbrella agreement, find out what that agreement already says about events run around yours before writing a criterion that contradicts it.
## The decision record
One row per request, kept whether you approve or refuse:
| Field | Why it is there |
| --------------------------- | ---------------------------------------------------------- |
| Requester and named contact | The person you call during the event |
| What was asked for | Listing, name use, floor space, nothing |
| Decision and date | The record that makes a later refusal consistent |
| Criterion that decided it | What you point at when asked why |
| Naming rung granted | Which of the four, so the approval response is unambiguous |
| Listed where | Your page, the guide, nowhere |
| Withdrawal conditions | See below |
The record is internal. Publishing decisions turns a refusal into a public verdict on somebody's event.
## Withdrawal
Keep a withdrawal right separate from any breach of the criteria. `samber/dev-event-organizer-skills@event-sponsor-agreement` records a reputational termination right from a real sponsorship contract, permitting an organizer to stop where "it reasonably determines that it would be detrimental to the reputation and goodwill" of the organization (PyCon US 2020 sponsorship contract, recorded in that skill's clause library). The shape transfers directly: an approval you cannot withdraw is a permission granted for every future edition, and the thing you will want to withdraw is rarely a criterion violation.
Say in the approval response what withdrawal means in practice - the listing comes down, the naming permission ends, and any materials already printed are the satellite organizer's problem, not yours. That last clause is the reason the naming rung matters more than the listing does.
## Refusal wording, positive and negative
The difference is whether the refusal is about the event or about the person.
**Do this.** State the criterion, state the decision, offer the one thing you can still offer, and stop.
> We are not listing this one: it runs against our closing keynote, which is a protected window for us. You are welcome to run it - please just move it clear of that window if you would like it on the fringe page, and either way do not use our logo on the ticket page.
**Not this.** Explaining, softening, and leaving the decision open is how a refusal becomes a negotiation and how a criteria set becomes a case-by-case argument.
> We love what you're doing and would really like to support it, but we're a bit worried about the timing and how it might look to some of our sponsors, so maybe let's see how the schedule shapes up and circle back closer to the date?
The second version also fails the person: they cannot plan against it, and they will print materials anyway.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |