Individual skill

conference-talk-proposal

Write a conference talk proposal / CFP submission for a tech or developer conference. Use when asked to submit to a CFP, propose a talk, or write a session abstract. Produces a compelling title, abstract, audience takeaways, an outline, and the speaker pitch — tuned to what selection committees actually look for.

skills/conference-talk-proposal/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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).
Back to top