bluf-rewriter
Reorganizes a memo, email, status update, or report so the bottom line is up front. Implements Kramon's BLUF (Bottom Line Up Front) rule. Use when a draft…
Drafts and critiques speeches, talks, keynotes, lightning talks, demo-day pitches, all-hands updates, conference presentations, wedding toasts, and any spoken-delivery piece using Glenn Kramon's 12 wowing-the-crowd rules from Stanford GSB's Winning Writing. Use when the user is
$ npx -y skills add kalyvask/winning-writing --skill speech-coach --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/speech-coachContext preview
The summary Claude sees to decide when to auto-load this skill.
Drafts and critiques speeches, talks, keynotes, lightning talks, demo-day pitches, all-hands updates, conference presentations, wedding toasts, and any spoken-delivery piece using Glenn Kramon's 12 wowing-the-crowd rules from Stanford GSB's Winning Writing. Use when the user is
name: speech-coach description: Drafts and critiques speeches, talks, keynotes, lightning talks, demo-day pitches, all-hands updates, conference presentations, wedding toasts, and any spoken-delivery piece using Glenn Kramon's 12 wowing-the-crowd rules from Stanford GSB's Winning Writing. Use when the user is preparing a talk, presentation, keynote, panel opener, board presentation, all-hands, town hall, demo-day pitch, toast, eulogy, commencement address, or any piece that will be delivered aloud. Triggers on phrases like "I'm giving a talk," "preparing a speech," "keynote," "all-hands," "demo day pitch," "wedding toast," "panel opener," "TED-style," "deliver this aloud," "speaking at," "presentation script."
Source: `points/speech-rules.md` (the 12 rules + the order-of-operations drafting flow + the Sparkline), `points/delivery-rules.md` (the three Vs, derailers, Q&A structures — for Mode 3 coaching), `points/kramon-master.md` (rhythm, jargon, warmth), `points/banned-jargon.md` (especially for spoken delivery — every banned phrase hits even harder when read aloud).
Given a topic + audience (or an existing draft), produce a talk shaped for the **ear**, not the page. The most common bad-talk failure mode is a memo read aloud — this skill catches that on sight and rebuilds the piece in spoken form.
A speech is **not an essay**. The reader of an essay can reread a sentence; the listener of a speech cannot. So the closing line matters more than the opening, the main thought must be repeated, and every sentence has to parse on first hearing.
If the user gives you a topic + audience, walk through Kramon's drafting order **before writing a single body paragraph**:
1. **Write the closing line first.** One sentence. The line you want quoted. If you cannot write it, the user does not have a talk yet — ask them what they want the audience to remember tomorrow morning. 2. **Write the main thought.** One sentence. Different from the closing — the *argument*, not the *image*. Said early, repeated once mid-talk. 3. **Pick ONE story.** Real people, real names, one scene. If the user offers three stories, pick a lane — the other two are different talks. 4. **Pick the opener.** Three archetypes work: self-deprecating story, show-of-hands question, single concrete image. Pick the one that earns the laugh or the raised hand faster for *this* audience. Never *"Thank you for having me"* — throat-clearing. 5. **Outline the arc.** Opener → main thought → story → second beat or quote → restate main thought → closing line. 6. **Draft the body** in short paragraphs, the way the user actually speaks. Contractions. Dropped subjects where natural. Variable sentence length. 7. **Cut by one third.** Every talk runs long live. Pre-cut so it still fits. 8. **Read aloud at performance pace** with a timer. Mark stumbles — those are listener confusion points; rewrite.
Length target: **20 minutes max** for a keynote, **5–7 minutes** for a lightning talk, **2–3 minutes** for a toast or panel opener. Words per minute at speaking pace is ~120–140 for natural delivery — do the math both ways and don't trust either alone.
Mark the draft against the 12 rules. Quote the specific lines that fail and rewrite them inline. Flag any of these on sight:
If the user has the draft and is preparing to deliver, do not rewrite — coach the delivery. Ask:
1. Have you read it aloud at performance pace? (If no, do that first. Time it. Cut to fit.) 2. Have you memorized the first 30 seconds and the last 30 seconds word for word? (If no, do that next. The middle can improvise; the bookends cannot.) 3. Where do you stumble? (Stumbles are not the user's fault — they are listener confusion points. Rewrite those sentences plainer.) 4. What's the one slide / image that the audience will photograph? (If none, the talk needs a visual anchor.) 5. What's your fallback if the projector dies? (If none, the user is not
31 Claude skills for cold outreach, op-eds, pitches, press inquiries, bios, exec memos, performance reviews, spoken-delivery talks, fact-checking, and reply-rate tracking.
Repo: kalyvask/winning-writing
Reorganizes a memo, email, status update, or report so the bottom line is up front. Implements Kramon's BLUF (Bottom Line Up Front) rule. Use when a draft…
Cuts a draft to a target word count without losing substance. Two modes behind one skill. target-count hits a specific number (200 for a cold email, 500 for an…
Rewrites blunt downward or peer feedback as "what I like plus what I would like," focused on the work rather than the person, ideally phrased as a question.…
Finds the unexpected, dry, or self-deprecating angle that makes an email memorable. Turns "professional and polite" into "this person sounds like a real…
Rewrites section titles, slide titles, op-ed headlines, email subject lines, and chapter headings from category labels into bold arguable claims. Implements…
Cuts cinematic details that don't serve the main point. The opposite move from vividness. Vividness adds sensory detail; this skill removes detail that's vivid…