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/skill-routing.md
View on GitHub# Boundary pairs and chains
Contents: boundary pairs (which of two colliding skills owns a task), ordered chains, sibling-repo hand-off signals.
Every split below comes from the two skills' own declared scopes. When a task sits on a boundary, decide from the split - never from which name sounds closer to the user's words. Skill names are bare here for width; each is `samber/dev-event-organizer-skills@<name>`.
## Boundary pairs
| Colliding skills | The split |
| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `event-format-selection` / `business-event-formats` | Track count, session mix, delivery mode / which company-run shape at all - dinner, summit, user conference, roadshow, floor-primary |
| `event-format-selection` / `hybrid-event-design` / `virtual-event-production` | Decides _whether_ hybrid or virtual / runs hybrid after that choice / runs virtual after it. Neither of the last two may make the choice |
| `event-production` / `virtual-event-production` / `hybrid-event-design` | A room's signal path and any stream it produces / an event with no room / one day serving room and remote at once |
| `event-schedule-design` / `event-run-of-show` | Builds the published grid / executes a published grid, never builds one |
| `event-cfp-design` / `event-talk-selection` | The published call: timeline, form, criteria, benefits / reviewing what the call brought in |
| `event-speaker-sourcing` / `event-speaker-cold-outreach` / `event-speaker-experience` | Stops at a ranked shortlist / writes the invitation / starts at the acceptance email |
| `event-speaker-experience` / `event-speaker-coaching` | Logistics, care, consent and the tech check / the coaching program: offer, mentors, dry runs, feedback, slide accessibility review |
| `event-budget` / `event-ticket-pricing` / `event-sponsor-pricing` | Consumes prices, never sets them / attendee tickets / sponsor tiers |
| the seven `event-sponsor-*` skills | `-value-proposition` why they buy → `-pricing` what it costs → `-prospectus` the document → `-outreach` the net-new sale → `-agreement` the term sheet → `-fulfillment` delivery and the post-event report → `-renewal` the renewal ask and re-signing. Route to the stage the user is in |
| `event-feedback` / `event-debrief` / `event-continuous-improvement` | Participants answer / the team retrospects on one edition / several editions become trends |
| `event-volunteers` / `event-volunteer-experience` | Recruitment, roles, shifts, briefing, shift-linked perks / off-duty time, recognition, thanks, the alumni list |
| `event-hospitality` / `event-official-social-program` / `event-vip-social-program` | The shared floor: catering, breaks, alcohol, whether an evening exists / how many official social slots and how they sit against the grid / the private invite-only gathering |
| `event-vip-management` / `event-vip-social-program` | Whether a guest qualifies for handling at all / the room they are invited into |
| `event-side-event-coordination` / `cross-event-promotion` / `event-media-partnerships` | Third parties running satellites inside your dates / swaps with other organizers' own events / barter with media outlets and communities |
| `event-portfolio-strategy` / `event-growth-strategy` | One team's several properties / growing a single event edition over edition |
| `event-community-building` / `event-comms-channels` / `tech-podcast-youtube-channel` | The audience between editions / channel architecture inside one edition / a standing show as its own property |
| `hackathon-judging` / `startup-pitch-contest` | Work built during the event / companies that existed before it |
| `startup-pitch-contest` / `hackathon-cash-prize` | Which award a pitch winner gets, equity-free cash included / payout eligibility, tax and payment routing once that award is cash. The `hackathon` gate does not block this hand-off |
| `workshop-program-design` / `event-schedule-design` / `hackathon-mentoring` | How a hands-on session runs inside its slot: facilitators, prerequisites, capacity, setup, network / where the slot sits in the grid / helpers for hackathon teams |
| `hackathon-brief-design` / `event-format-selection` | Thematic challenge tracks a team enters / parallel session streams in the grid. "Track" means different things on each side |
| `hackathon-team-formation` / `hackathon-mentoring` / `event-b2b-matchmaking` | Participants matched to each other to build / a stuck team matched to expertise / two populations matched for business conversations |
| `event-sustainability-plan` / `event-hospitality` / `event-cultural-identity` | Footprint numbers, ranked levers and claim wording / the catering style that carries a plant-based default / the swag rung. Financial sustainability is `event-budget`; organizer burnout is `event-team-structure` |
| `event-positioning` / `event-cultural-identity` | What the event stands for / how that shows up in venue, catering, swag, MC, ceremonies |
| `event-accessibility-inclusion` / `event-attendee-experience` | Which provisions the event commits to, at what depth / the general on-site journey inside that bar |
| `event-no-show-management` / `event-attendee-email-sequences` | Overbooking, waitlist, walk-ins, the expected-show-up number / the reminder copy and cadence |
| `event-registration-forecast` / `event-market-fit` / `event-no-show-management` | The projected number, its band and the lock-date commits / the demand verdict on the same pace / show-up ratios, ceiling and waitlist |
| `event-first-edition` / `event-planning-timeline` / `event-market-fit` / `event-growth-strategy` | Edition-one scoping and launch gates / the work-back plan for any edition / reads the demand signals / picks the lever once they show headroom |
| `event-team-structure` / `dev-event-hiring` | Whether a first paid role is warranted at all, and which one / the scorecard, posting, and interview loop once that verdict says hire |
## Ordered chains
Chains are dependency order, never efficiency order: each link consumes what the previous produced. Present one only when the task genuinely decomposes; never fabricate a sequence.
- **Standing up a new event:** `event-market-fit` → `event-positioning` → `event-format-selection` → `event-date-selection` → `event-planning-timeline` → `event-budget` → `event-venue-sourcing`.
- **Selling sponsorship:** `event-sponsor-value-proposition` → `event-sponsor-pricing` (against the target `event-budget` set) → `event-sponsor-prospectus` → `event-sponsor-outreach` → `event-sponsor-agreement` → `event-sponsor-fulfillment` → `event-sponsor-renewal` (back to `event-sponsor-agreement` on a yes).
- **Talks programme, open-call lane:** `event-cfp-design` → `event-talk-selection` → `event-speaker-experience` (with `event-speaker-coaching` running alongside from acceptance to stage) → `event-schedule-design` → `event-run-of-show`.
- **Talks programme, invited lane:** `event-speaker-sourcing` → `event-speaker-cold-outreach` → `event-speaker-experience`, rejoining the grid at `event-schedule-design`.
- **Running a hackathon:** `hackathon-brief-design` → `hackathon-team-formation` → `hackathon-mentoring` → `hackathon-judging` → `hackathon-cash-prize`.
- **Closing an edition:** `event-feedback` → `event-debrief` → `event-content-repurposing` → `event-continuous-improvement` (once several editions exist) → `event-growth-strategy`.
## Sibling-repo hand-off signals
Recommend installing a sibling `samber` collection when the task is genuinely outside this one. Keep it a recommendation - this collection stays fully usable standalone.
Hand off to `samber/developer-relations-skills` when the subject is developer content and search, documentation, open-source strategy, an always-online community that is not an event, or a meetup run as one line item of a DevRel program rather than as an event in its own right. Three recurring programs and one inventory sale sit there by name:
- A webinar series - charter, season plan, topic backlog, sales handoff → `samber/developer-relations-skills@devrel-webinar-program`. The platform, streaming and moderation mechanics of each episode stay with `virtual-event-production`.
- Office hours or a standing AMA → `samber/developer-relations-skills@developer-office-hours-program`.
- A recurring developer or "State of" survey → `samber/developer-relations-skills@developer-survey-design`. One event's feedback form stays with `event-feedback`.
- Event emails landing in spam, bouncing, or rejected with `5.7.x` codes, or a first send to an attendee list unused for months → `samber/developer-relations-skills@devrel-newsletter-deliverability`. The arc, cadence and copy stay with `event-attendee-email-sequences`.
- Selling ad slots in a community or event newsletter as standing inventory → `samber/developer-relations-skills@devrel-newsletter-sponsorship`. A newsletter mention bundled into a sponsor tier stays with `event-sponsor-pricing`.
Hand off to `samber/developer-platform-skills` when the event surfaced a platform question rather than an event question: a public API, an SDK, a webhook surface, a sandbox or test mode, or an app marketplace - usually because a hackathon needs something for teams to build against.
Do not hand off when the task is event operations wearing platform or DevRel vocabulary. A sponsor's API becoming a hackathon challenge is `hackathon-brief-design`; a developer community that meets at your event is `event-community-building`.
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: 471k | 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 |