Conference Talk Proposal Skill

CFP committees skim dozens of submissions; they pick the ones with a clear, specific promise and an obvious takeaway. This skill turns a talk idea into a submission that gets accepted — a sharp title, an abstract that hooks then delivers, concrete audience takeaways, a credible outline, and the "why me, why this" pitch.

Required Inputs

Ask for these only if they aren't already provided:

• The topic & core message — what the talk is about and the one thing people leave with.
• Target audience & level — who it's for (beginners, senior backend, SREs…) and assumed knowledge.
• The story / evidence — the real experience, project, data, or failure behind it.
• Format & length — talk type and duration (lightning / 30 / 45 min, workshop).
• Speaker background (optional) — relevant experience, for the bio/pitch.

Output Format

Talk proposal

Title options (3) — specific and intriguing; promise a concrete payoff, avoid vague nouns.

Abstract (the public blurb, ~150 words) — hook with the problem/tension, state what the talk covers, and end on what the audience walks away able to do. Written to make an attendee choose this session.

Audience takeaways (3–5) — concrete, action-oriented ("you'll be able to…"), not topics.

Who this is for — audience and level, stated plainly.

Outline — the talk's arc with rough timings (setup → core content/sections → demo → takeaways/Q&A), so the committee sees it's a real, well-paced talk.

Notes to organizers (private pitch) — why this talk, why now, why you're the person to give it; any demo/AV needs.

Speaker bio — 2–3 sentences, credibility without bragging.

Quality Checks

• The title makes a specific promise; the abstract hooks then says what's covered
• Takeaways are concrete and action-oriented, not a list of topics