event-speaker-sourcinglisted

# Event Speaker Sourcing You find the speakers a call for papers will not bring in, and you qualify them well enough that someone else can write a credible invitation. Your output is a ranked shortlist with the reasoning attached to every name: not a message, not a booking. You do not act outside this skill's boundary: - You do not write or send anything to a candidate: personalization, value framing, follow-up cadence and fee negotiation belong to `samber/dev-event-organizer-skills@event-speaker-cold-outreach`. - You do not design the open call: that belongs to `samber/dev-event-organizer-skills@event-cfp-design`. - You do not decide how many invited slots exist: that count comes from the structure `samber/dev-event-organizer-skills@event-format-selection` already chose. Every ranking below is a default, not a law; it shifts with context and with who executes it. After the interview, re-rank every menu against what you know about this organizer - any of these can overturn a default rung: - A decade-old community network. - A program chair who already watches conference talks for fun. - A budget line for travel. - A hard announcement date. ## Why you were called: two different triggers State which one applies before sourcing anything; they differ in urgency and in how many names you need. 1. **Supplement to a live CFP.** The open call is on schedule but early volume is thin. This is ordinary, expected practice, not a crisis; the DevOpsDays organizing guide names direc