event-talk-selection

Designs the review and selection process for conference CFP submissions, from committee structure to decline emails.

1|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-talk-selection-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-talk-selection
Source: https://github.com/samber/dev-event-organizer-skills/tree/main/skills/event-talk-selection
Command: npx skills add https://github.com/samber/dev-event-organizer-skills --skill event-talk-selection-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Once a call for papers closes, organizers face hundreds of proposals, a handful of slots, and no defensible process for choosing between them. This Skill turns a raw submission pool into a documented selection process: who reviews, on what rubric, with what anonymization depth, and what every submitter hears back. ## Core Features & Use Cases - Committee and rubric design: Chooses between a small consensus committee, solo curation, a multi-tier cascade, or a distributed reviewer pool, each paired with its matching scoring scale (letter-grade advocate, multi-criteria star, or numeric 0-3). - Anonymization and conflict-of-interest execution: Implements blind review at platform-hiding or dedicated-anonymizer depth, briefs reviewers on recusal rules, and pre-decides arbitration for disputes. - Decision communication: Sequences acceptances, waitlists, and declines with templates, confirmation deadlines, and per-proposal feedback rules. - Use Case: Your conference received 190 proposals for 22 slots and six organizers can review. Use this Skill to set up the committee, replace a naive 1-5 average with the advocate scale, fix a cut rule before ranking, and draft the accept, waitlist, and decline emails in the correct order. ## Quick Start Ask the Skill to design the review committee, scoring rubric, and notification sequence for your conference's CFP submissions, stating your proposal count, slot count, and reviewer headcount.

Frequently Asked Questions about event-talk-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the review process for conference CFP submissions?

Start from the published call's promises, then pick a committee model sized to your pool: a small consensus committee for pools one room can read, or a multi-tier cascade for multi-track events with thousands of submissions. Write the rubric and cut rule down before any scoring begins.

What scoring rubric should reviewers use to rate talk proposals?

The rubric follows the committee model. Committees that meet use the letter-grade advocate scale (A/B/C/D/X) aggregated as best-worst pairs; reviewers who never meet use a multi-criteria star scale; distributed platform pools use a numeric 0-3 scale. Every score requires a mandatory written comment.

Does blind review make a conference program more diverse?

No published evidence shows anonymized review changes acceptance outcomes by demographic. Blind review is defensible as a process commitment, but under-representation is addressed by outreach before the call closes, not by the review process afterwards.

What is the rule when a reviewer knows a submitter?

Reviewers abstain rather than score and disclose, covering both close colleagues and competing employers, plus suspected identification of an anonymized author. All conflict-of-interest handling in this field is honour-system self-recusal, so decide in advance who arbitrates refusals.

What order should acceptance and rejection emails be sent in?

Send acceptances first with a confirmation deadline, waitlist notices at the same time, and declines only after acceptances are confirmed. Build and order the waitlist before notifying anyone, and never give waitlisted speakers a probability of promotion.

When should I not use this talk selection process?

Do not use it to design the call for papers itself, recruit invited speakers, place accepted talks into the schedule grid, or judge hackathon projects. Those belong to separate skills for CFP design, speaker sourcing, schedule design, and hackathon judging.