samber/dev-event-organizer-skills / skills/dev-event-kickoff
dev-event-kickoff
VerifiedBefore answering any event-organizing request that opens a new project or a new session, run this router first - it maps the task onto the 72-skill samber/dev-event-organizer-skills collection, or says plainly that none fits, and bootstraps or resumes the project's shared context so the next session starts warm. This fires on a conversational state, not on a subject - invoke it at every event project start even when the collection's skills are already in daily use on another event, at every recurring check-in on the same project, and whenever routing between siblings is unclear. Covers conference, meetup and hackathon kickoffs, "which event skill do I need", "where do I start organizing this event", event organizer skill routing, and recurring event check-ins. Use this whenever someone describes an event-organizing problem without naming a skill, even if they never say "kickoff", "routing" or "start".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 51.0 KB |
| evals/evals.json | config | 46.9 KB |
| references/context-artifact.md | markdown | 3.7 KB |
| references/format-and-lifecycle-gates.md | markdown | 7.4 KB |
| references/routines.md | markdown | 2.4 KB |
| references/skill-routing.md | markdown | 15.2 KB |
references/format-and-lifecycle-gates.md
View on GitHub# Format and lifecycle gates
Contents: what each gate means, the format matrix, the lifecycle matrix, and what to do when the format is not fixed.
A gate is a reachability test, not a ranking. It answers "can this row apply to this event at all", and it is always read from an answer the user gave or an artifact on disk - never inferred from the event's name, its ambition, or the user's tone.
Each gate's value comes from one place:
- Format gates - question 2, and once fixed, `samber/dev-event-organizer-skills@event-format-selection`'s output recorded in the context artifact.
- Lifecycle gates - question 3 and the artifact's edition number and property list.
- Company gate - question 4 and the artifact's funding model.
## Format gate matrix
| Gate | Open when | Rows it governs |
| ------------ | ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `hackathon` | The shape is a hackathon | `hackathon-brief-design`, `hackathon-team-formation`, `hackathon-mentoring`, `hackathon-judging`, `hackathon-cash-prize` |
| `workshop` | The format committed hours to hands-on sessions | `workshop-program-design` |
| `virtual` | Delivery mode is fully virtual | `virtual-event-production` |
| `hybrid` | Delivery mode is hybrid | `hybrid-event-design` |
| `in-room` | Delivery mode is in-person or hybrid - that is, a physical room exists | `event-venue-sourcing`, `event-attendee-experience`, `event-hospitality`, `event-production` |
| `conference` | The event is at conference scale: more than one track, or an expo floor, or a named-guest and press surface | `event-press-relations`, `event-booth-experience`, `event-b2b-matchmaking`, `event-vip-management`, `event-official-social-program`, `event-vip-social-program` |
| `company` | A company funds and owns the event | `corporate-event-strategy`, `business-event-formats` |
Three consequences worth stating, because each deletes rows a reader expects to see:
- A fully virtual event closes `in-room` outright: no venue to source, no room to lay out, no catering, no physical signal path. `virtual-event-production` replaces all four, and `event-accessibility-inclusion` still applies because its digital-access provisions need no room.
- `hackathon` and `conference` are not mutually exclusive. A multi-track conference running a hackathon track opens both, and `startup-pitch-contest` is ungated on purpose: it judges companies that existed before the event, so it fits either. When its award is equity-free cash, it reaches `hackathon-cash-prize` for payout mechanics despite that row's `hackathon` gate.
- `conference` is not a synonym for "big". Its threshold is qualitative and self-set, not a measured headcount: it opens when the event has the surface - a floor, a press pool, guests who create protocol obligations - not when the organizer hopes it will.
## Lifecycle gate matrix
Ask this in the shape `event-planning-timeline` already assumes: any edition can be planned, but only some skills have a previous edition to read.
| Gate | Open when | Rows it governs |
| ------------ | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| `first` | This is edition one of something new | `event-first-edition` |
| `recurring` | Edition two or later | `event-team-structure`, `event-continuous-improvement`, `event-community-building`, `event-growth-strategy`, `tech-podcast-youtube-channel` |
| `properties` | The team runs more than one event property, or is deciding whether to add one | `event-portfolio-strategy` |
Two rows are commonly mis-gated and are not:
- `cross-event-promotion` is **not** recurring-gated. Its own interview asks whether the swap is a one-off boost for the coming edition or a compounding relationship, and it answers both. Gating it would delete the one acquisition lever a first edition can reach without a track record.
- `event-portfolio-strategy` gates on **property count, not recurrence**. A team running a single event forever never opens it; a team weighing whether to add a second format opens it on the day they start weighing, whatever edition the flagship is on.
The `recurring` gate is about having an edition to read, not about intent to repeat. A team that intends to recur but has not yet finished edition one still has nothing for `event-continuous-improvement` to compare.
## When the format is not fixed
Question 2 answers (a) "nothing fixed" and (b) "shape fixed, the rest open" both mean the format gate cannot be applied.
1. Route to `samber/dev-event-organizer-skills@event-format-selection` and stop. Do not offer a short-list drawn from gated rows.
2. Say which rows are suspended and why - the hackathon lane, the delivery-mode skills and the conference-scale population skills are unreachable until the shape and mode exist, not absent from the collection.
3. Record the returned decision in the context artifact the moment it exists, so the next session reads the gate instead of re-asking question 2.
4. Never guess a shape to unlock rows with. A misapplied gate routes confidently to a skill written for a different event, which is worse than routing to nothing.
Answer (b) is the partial case: a known shape opens `hackathon` and `workshop` while the delivery mode is still open, so `in-room`, `virtual` and `hybrid` stay suspended, and `conference` usually does too, since track count is part of what is still open.
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 | Verified | 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 |