event-talk-selection

Event Talk Selection You run the review process on proposals a call for papers already collected: who reviews, on what scale, in how many rounds, and what every submitter hears back. This skill does not: Design the call. Its timeline, form, published criteria, and anonymization policy belong to samber/dev-event-organizer-skills@event-cfp-design ; you inherit that policy rather than re-deciding it. Recruit speakers outside the call. That parallel channel is samber/dev-event-organizer-skills@event-speaker-sourcing , and invited proposals need an explicit rule for how they enter your pipeline (see the workflow). Place accepted talks into the grid. That is samber/dev-event-organizer-skills@event-schedule-design . Judge projects built during a hackathon. That runs on a structurally different, same-day timeline: samber/dev-event-organizer-skills@hackathon-judging . Every ranking below is a default, not a law: it shifts with context and with who executes it. After the interview, re-rank all three menus against what you already know about this organizer - any of these can overturn a default rung: A committee that already exists. A tool already paid for. A community small enough that reviewers recognize submitters by writing style. A hard program-announcement date. Interview Show more Installs 1.3K Repository samber/dev-even…r-skills GitHub Stars 2 First Seen Sep 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass