From skills
Writes conference talk proposals and outlines: CFP abstracts, talk structure with timing, and key slides flow. For technical developer conferences.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills:talk [conference topic or title][conference topic or title]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structured for technical developer conferences (25-30 min single track). Produces three deliverables: CFP abstract, talk outline with timing, key slides list.
Structured for technical developer conferences (25-30 min single track). Produces three deliverables: CFP abstract, talk outline with timing, key slides list.
The talk structure that gets accepted and remembered:
Visceral opening — a failure story, a question the audience can't answer, a stat that reframes what they thought they knew. Not "today I'm going to tell you about X."
The painful thing everyone does — establish shared experience. The audience needs to recognize themselves. If they're nodding, you have them.
The journey with failed attempts — how you discovered the solution, including what didn't work. This is what separates a talk from a blog post. The failed attempts are credibility — they show you lived this, not just read about it.
The insight with a demo — the thing they came for. Keep demos minimal. Have a backup screenshot. Live demos fail publicly; plan for it.
Monday morning takeaways — 3 concrete things they can do when they're back at their desk. Not "think differently about X" — actual actions.
Before writing, establish:
Format (400-500 words total):
TITLE
[Direct and specific. "How we reduced deploy time from 40 min to 90 sec"
beats "Optimizing CI/CD Pipelines". Concrete beats clever.]
ABSTRACT (250-300 words)
Paragraph 1: The problem — what's painful about this right now, why it matters today
Paragraph 2: The journey — what you tried, what failed, what you discovered
Paragraph 3: What attendees will leave with (specific, not vague)
WHAT ATTENDEES WILL LEARN
- [Specific skill or decision they'll be able to make]
- [Specific tool, pattern, or technique they'll use]
- [Mental model that changes how they approach this problem]
SPEAKER BIO HOOK (50 words)
Not a resume. One sentence about why you specifically are the right person
to give this talk — the thing that establishes credibility on this topic.
[0:00-2:00] Opening hook — the failure/question/stat
[2:00-7:00] Problem setup — the painful thing everyone does, why it's wrong
[7:00-15:00] Journey — what you tried, what failed, the turning point
[15:00-22:00] Resolution — the insight, live demo or concrete example
[22:00-25:00] Takeaways + Q&A setup
Adjust for actual length. Keep demo segments to 5-7 min max — they always run long.
Not the slides themselves — the logical flow. One line per slide/beat:
1. Opening image/question (no title slide to start)
2. "Here's the mistake" — the thing everyone does
3. Code showing the wrong way
4. The moment of discovery
5. Architecture diagram / key concept
6. Code showing the right way
7. Benchmark / result / proof
8. Demo (or screenshot if demo risky)
9. Three takeaways
10. One slide people will photograph
When the user asks for slide markdown (not just the outline), generate iA Presenter format:
# Slide Title
Content visible on slide (indented with tab)
Speaker notes without tab (invisible to audience)
// reminder comment
---
iA Presenter rules:
---// comment for author remindersStructure: Title slide → speaker intro → one or more slides per Story Circle step → closing with contact/resources.
Deliverables in this order:
Present 1–3 together — they inform each other and the reviewer needs to see the full shape.
| Priority | Stage | Load when | Reference |
|---|---|---|---|
| 1 | Outline | Building the narrative arc or structuring the talk story | references/story-circle.md |
| 2 | Slides | Generating iA Presenter slide markdown | references/ia-presenter-syntax.md |
npx claudepluginhub kriscard/skillsDrafts compelling conference talk proposals with hook-worthy titles and structured abstracts. Use for submissions to conferences, meetups, or internal tech talks.
Prepare and deliver technical talks that educate, inspire, and represent your team and company. Use for conferences, internal knowledge sharing, or building credibility.
Guides users through an interactive two-phase process to plan, storyboard, and draft slide copy for presentations in any context (talk, boardroom, email report).