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/routines.md
View on GitHub# Routine mechanics
The ranked candidate set, its axes and its promotion conditions live in the skill body, at the point where the choice is made. This file covers only the mechanics: the dry-run format, the calendar anchors, and cleanup.
## Dry-run format
Show every proposed routine in this shape and get approval before creating anything. The values below are illustrative; substitute the project's own:
```
Routine: ticket-pace check
Trigger: the 1st of each month while registration is open
Runs: samber/dev-event-organizer-skills@event-market-fit
Output channel: a dated section appended to event-context.md, plus a message in the
organizers' channel when the pace index falls below its checkpoint
Cost: one reading per firing; no work unless the number is off
First fire: 2026-09-01
Stops: on the doors-open date
```
Two fields are the ones routines usually lack:
- **Output channel** - without one, the routine fires into the void and gets silenced, which buries the routine that mattered; if you cannot name where the result lands, drop it.
- **Stop condition** - without one, it outlives the edition it was built for; an event has a finish line, so almost every routine here should retire itself on a date.
## Calendar anchors
Prefer a date the project already has over an arbitrary schedule:
- Doors open → the work-back checkpoints, and the retirement date for most routines.
- CFP open and close → reviewer recruitment before, selection after.
- On-sale date and each pricing-tier boundary → the ticket-pace check.
- Each rung of the venue's escalating cancellation-fee curve → a go/no-go review placed _ahead_ of the rung, never on it.
- Sponsor budget windows → the pipeline and renewal sweep, timed to the window rather than to a month.
- The debrief date → the post-edition trend read, which cannot fire before it.
Two lead times are systematically underestimated on events:
- Anything needing a signature from outside the organizing team.
- Anything a volunteer has to do around a day job.
Set both triggers earlier than feels necessary.
## Cleanup
Retire, explicitly and out loud, before installing anything new:
- Routines tied to a date that has passed.
- Routines pointing at a renamed or removed skill.
- Routines that have fired repeatedly without producing an action.
- Every routine carried from edition N-1 without being re-anchored to edition N's dates - the commonest form of noise here, because it looks correct and fires at nothing.
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 |