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/context-artifact.md
View on GitHub# Context artifact
`event-context.md` lives at the project root and is committed with the project when the project lives in git. One file, versioned, readable by every co-organizer. It is what makes the next session a warm start.
## Template
```markdown
# Event context
_Last updated: YYYY-MM-DD_
## Identity
- Event: name, and what someone attends it for.
- Edition: which one, and the date of the previous one if there was one.
- Funding model: volunteer community / company-owned / foundation / mixed.
- Positioning: what it stands for, against which alternative - from
`samber/dev-event-organizer-skills@event-positioning` if it has run.
## Format (the gate source)
- Shape: meetup / hackathon / unconference / single-day / multi-day conference.
- Track count, and the session-format mix.
- Delivery mode: in-person / virtual / hybrid.
- Workshop hours: yes or no.
- Properties this team runs, if more than one.
## Dates
- Doors open, and whether it is announced.
- CFP open and close. On-sale date. Sponsor budget windows that close.
- The venue's cancellation-fee rungs and the go/no-go date before each.
## Money
- Budget status, break-even figure and where it is recorded.
- Ticket ladder status. Sponsor rate card status. Sponsors signed.
## Programme
- Call status, submissions in, accepted, grid published or not.
## State
- In flight: work started and not finished.
- Decided: settled calls, not to be re-litigated.
- Open: live questions.
- Constraints: the landing date, one-off versus standing, the effort ceiling.
These three re-rank the short-list and the routines without re-asking Q6 and Q7.
## Team
- Name or role - decision rights on what.
## Session log
- YYYY-MM-DD - session goal → skill routed to → what changed here.
```
## Worked example (excerpt)
Both examples below are illustrative constructions showing the field shapes, not records of a real event.
```markdown
## Format (the gate source)
- Shape: single-day, single-track. No workshop hours.
- Delivery mode: in-person. Talks recorded and posted afterwards, no live stream.
- Properties: one. No second format under consideration.
## State
- In flight: call open, eleven submissions, no reviewers recruited yet.
- Decided: free entry, single track, no recording consent by default.
- Open: whether to accept a second sponsor.
- Constraints: doors 2026-11-07; standing, a few hours a week; four volunteers, no budget.
## Session log
- 2026-08-31 - "how do we pick talks" → `samber/dev-event-organizer-skills@event-talk-selection`
→ recorded the submission count and the missing reviewers as in-flight.
```
## Negative example - what not to write
```markdown
## Format (the gate source)
- Shape: TBD, probably a conference eventually.
- Delivery mode: we'd like it to be hybrid if we can.
## State
- Decided: nothing yet really.
- Constraints: we should be careful with budget.
```
Four failures:
- A `TBD` shape means the next session re-asks question 2 and every gate stays suspended - write "not fixed" and route to the format skill instead of recording an aspiration.
- "Probably a conference eventually" and "hybrid if we can" are wishes recorded in the field a gate is read from, which is how a router unlocks the wrong rows.
- "Nothing yet really" in a decided field is unfalsifiable, so nothing can be protected from re-litigation.
- "Careful with budget" gives the money model no number to work against; write the figure, or write that there is none.
## Archiving between editions
Before starting edition N, move the previous artifact aside rather than overwriting it - `event-context-2026.md` beside the live one is enough. `event-debrief` and `event-continuous-improvement` both read what the last edition actually decided, and an overwritten artifact leaves them reconstructing it from memory.
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 |