tech-talk-outline

Converts an accepted conference talk abstract into a timed, rehearsable outline with slide skeleton and cut checkpoints.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill tech-talk-outline-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-talk-outline
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/tech-talk-outline
Command: npx skills add https://github.com/samber/developer-relations-skills --skill tech-talk-outline-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? An accepted conference abstract is not a talk. Speakers routinely write to the material instead of the slot, place demos before the audience believes the problem, memorize scripts that collapse on stage, and run over time with no plan for what to cut. This Skill turns the accepted abstract into a structured outline a speaker can rehearse, time, and trim live. ## Core Features & Use Cases - Arrow, arc, and pillars: Derives the single remembered sentence, presents 2-3 gated and ranked narrative arcs for the speaker to choose, and attaches concrete evidence to each pillar. - Time budget and demo placement: Builds a minute-by-minute budget with a 10-15% buffer, places the demo after the problem lands, and budgets it at twice its rehearsed length. - Slide skeleton and cut checkpoints: Produces an ordered list of what each slide must accomplish (never a slide-count target) plus speaker-note cues like "past 0:14 at slide 12, drop pillar 3". - Rehearsal gate: Uses the accordion method (3, 2, 1, 0.5 minute reps) to derive the cut list as a measurement, with a quality gate of two consecutive timed runs inside slot-minus-buffer. - Use Case: A staff engineer whose talk was accepted for a 25-minute slot pastes the abstract and gets an interview-driven workflow ending in a full outline document with arc, pillars, timing, demo placement, and a rehearsal plan. ## Quick Start Ask the assistant to turn your accepted conference abstract into a rehearsable talk outline for your specific slot length and audience.

Frequently Asked Questions about tech-talk-outline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a conference talk after my abstract gets accepted?

Start from the promise the accepted abstract made, derive a single-sentence takeaway (the arrow), choose a narrative arc that fits your material and audience, then build 2-3 evidenced pillars and a minute-by-minute budget. The outline, not a script or slide deck, is the rehearsable artifact.

Where should the live demo go in a technical talk?

Place the demo after the audience believes the problem, so it reads as proof rather than a product tour. Budget it at twice its rehearsed length, state what to watch before starting, and keep at least two minutes of speaking after it so an overrun cannot eat the conclusion.

How do I cut a 40-minute talk down to a 25-minute slot?

Use the accordion method: deliver the talk to 3, 2, 1, and 0.5-minute timers, then expand back up. What survives the shortest rep is the core; what reappears later is the cut list in order. Cut a whole pillar rather than thinning all of them.

How many slides should a 30-minute talk have?

There is no valid slides-per-minute rule; slide count is an outcome, not a target. A story-led talk can run on three slides while a dense technical talk can run a hundred in thirty minutes. Define what each slide must accomplish and let the count fall out.

Should I write my conference talk out word for word?

No. A memorized script is what causes on-stage freezing, because talking points survive losing your place while memorized prose does not. Use an outline with speaker-note cues and timing checkpoints instead, and measure your own speaking rate rather than trusting generic words-per-minute tables.

When should I avoid a live demo on stage?

Avoid unscripted live typing when rehearsal time is short, since it is the most expensive tier to prepare and the most fragile. A narrated screencast is the efficient default; reserve live demos for cases where liveness itself is the claim being proved.