samber/dev-event-organizer-skills / skills/event-speaker-cold-outreach
event-speaker-cold-outreach
VerifiedWrite and sequence the cold invitation to a speaker a shortlist already picked - the message, not the search. Covers what a first invitation must disclose up front (event basics, honest budget and travel terms, the answer deadline, how you found them), personalization built from the shortlist's own "why", ranked first-touch channels, follow-up cadences that add a new angle instead of bumping, and the fee conversation where speakers have no rate card. Use whenever the user mentions writing a speaker invitation, pitching a keynote candidate, following up on an unanswered invitation, or a speaker who asks for a fee - even if they never say "outreach". Do NOT use to find or qualify candidates - use samber/dev-event-organizer-skills@event-speaker-sourcing instead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 28.7 KB |
| evals/evals.json | config | 34.2 KB |
| references/cadence-and-fee-conversation.md | markdown | 9.7 KB |
| references/invitation-message-craft.md | markdown | 7.1 KB |
references/invitation-message-craft.md
View on GitHub# Invitation message craft
Contents: the five-part structure · length and vocabulary · subject lines · the disclosure checklist · a worked invitation · a worked failure.
## The five-part structure
1. **One line proving you did the homework.** Their specific recent work - the talk, the post, the project - named precisely enough that it could not have been written to anyone else. This line doubles as the consent disclosure: it states how you found them.
2. **The ask, in one sentence.** The slot, the event, the date. Not a build-up, not a paragraph about the event's mission.
3. **Why it matters to them**, not to you: why this audience, this room, this stage. An invitation that explains why the program needs them has answered the wrong question.
4. **Proof, as evidence rather than adjectives.** Attendance and audience composition, who else is confirmed, what last edition's room was actually like. Numbers you can stand behind, and nothing you cannot.
5. **A specific, low-friction ask.** A proposed next step with a date attached - "would a 20-minute call Thursday work?" - never "let me know if you're interested."
The honest terms (budget, deadline) attach to part 3 or part 5, wherever they read least like a footnote. They are not optional and they are not deferred; see the checklist below.
## Length and vocabulary
- **Cap the first email at roughly 150 words.** A speaker's inbox gives you a screen, not a page. Everything that does not fit belongs to the second touch or to the call.
- **Banned vocabulary:** revolutionary, disruptive, game-changing, best-in-class, cutting-edge, thought leader, rockstar, ninja, guru. These read as marketing copy to exactly the audience most allergic to it, and none of them is evidence.
- **No superlatives about the candidate.** "The leading expert on X" is unfalsifiable flattery and invites the reader to disagree with you in the first ten seconds. Name what they did; let it carry the weight.
- **Run a humanizer pass** in your preferred humanizer skill before sending. A practitioner who reads model-written email all day recognizes the cadence instantly, and an invitation that reads as generated undercuts the personalization it is built on.
- **Short signature.** A long signature block is a pitch-killer: name, role, event, one line.
## Subject lines
- **Under 50 characters.**
- **Lead with the specific**, not with the transaction. "A platform-engineering keynote, not another CEO slot" over "Speaking invitation from DevConf".
- **Promise the slot, not the honour.** "Invitation to speak at X" tells the reader nothing they can evaluate; the theme and the audience do. A generic "X and Y Partnership" against the specific "Meet the Best Students in X Town this February" - the specific, curiosity-driving form is the one to write.
## Disclosure checklist for the first message
- [ ] **Event basics**: size, location, dates.
- [ ] **How you found them**, in the first line. A directory listing, conference speaker page, or public profile is consent to be _found_, never consent to be _pitched_. Stating the discovery route is what makes the approach legible rather than harvested, and you follow the contact route they actually published rather than a guessed address.
- [ ] **The specific angle**, from the sourcing packet's "why" - their work, not their reputation.
- [ ] **Why this slot, this audience, this stage** - aimed at a speaker's incentive (peer audience, a room worth being seen in, a hearing for a topic), not the organizer's need. Where recordings are published, one verifiable reach figure for last edition, with its source.
- [ ] **Honest terms**: what the budget covers - including "nothing beyond a ticket" or "unconfirmed" - and the date you need an answer by. For an event outside the region's main hub, state travel and lodging separately. Silence on money reads worse to a speaker than to a sponsor: a sponsor expects a negotiation, a speaker is being asked to block a calendar.
- [ ] **The travel lead time, named** whenever the candidate has to travel and the answer date sits inside roughly four to six weeks. Do not let them discover the constraint.
- [ ] **A specific, low-friction next step** with a proposed date.
- [ ] **No links, no attachments, no images.** Corporate phishing filters auto-trash mail carrying them, and a speaker's work address is that kind of inbox. The CFP page, the program, the logo and the meeting link all wait for touch two.
## A worked invitation
> **Subject:** A talk on incident review that isn't a postmortem template
>
> Hi Priya - I watched your SREcon talk on why blameless postmortems stall at the second incident, and the section on review fatigue is the thing our audience keeps arguing about in the hallway track.
>
> I'd like to invite you to give the 35-minute session on that theme at NordOps on 14 March in Gothenburg. It's a single-track community day, around 300 attendees, mostly platform and SRE practitioners running production.
>
> Two people have already confirmed on adjacent topics, so you would not be the only voice on it - which is the version of this conversation our room actually wants.
>
> We cover travel and two nights' lodging. We don't pay speaker fees; I'd rather tell you that now than after you've blocked the week. I need an answer by 20 January so there's time to arrange travel.
>
> Would a 20-minute call on Thursday or Friday work?
What it does:
- opens on specific evidence and thereby states the discovery route
- asks in one sentence
- frames the value as the audience and the conversation rather than the event's need
- gives real numbers
- states the budget honestly and unprompted
- names a deadline tied to the travel lead time
- closes with a dated, low-friction ask
Roughly 150 words, no links, no attachments.
## A worked failure
The same invitation written the common way. Each fault is a rule above, broken.
> **Subject:** Speaking Invitation - NordOps 2026 Call for Keynote Speakers
>
> Dear Ms. Priya,
>
> My name is [organizer] and I am one of the organizers of NordOps, an exciting and disruptive conference bringing together the best-in-class minds in DevOps. As a recognized thought leader in the SRE space, you would be a fantastic addition to our lineup!
>
> We came across your profile and were very impressed. Our event is going to be an unforgettable experience for everyone involved.
>
> Please find attached our speaker prospectus and let me know if you might be interested in participating. You can read more at [link] and see last year's photos at [link].
>
> Looking forward to hearing from you!
>
> [six-line signature block with logo]
The faults, in order:
1. Subject line generic and over 50 characters.
2. Wrong honorific guessed from a name.
3. Four banned words in two sentences.
4. "We came across your profile" is discovery with no evidence attached, exactly the harvested-list reading the disclosure rule exists to avoid.
5. No event basics: no date, no city, no size.
6. The value is asserted, never evidenced.
7. Not one word about money.
8. No deadline.
9. An attachment, two links and a logo that will get the whole thing auto-trashed before anyone reads any of the above.
10. The ask is open-ended, so even a reader who wanted to say yes has nothing to say yes to.
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: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |