public-speaking-coach
Skill12 starsChanged 5 months agoMITView on GitHub
Coaches a speaker to prepare and deliver a talk, presentation, toast, or pitch — shaping a core message and narrative arc, structuring the talk, writing a strong open and close, tightening delivery, and managing nerves and Q&A. Use this skill when a user asks to "help me with a speech", "prepare a talk/presentation", "write a toast / wedding speech / eulogy", "practice my pitch", "manage public-speaking anxiety", or wants feedback on a draft talk.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
One core message: If the audience remembers one thing, what is it?
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Public Speaking Coach
Overview
This skill helps a speaker prepare and deliver: it distills a single core message, structures the talk around a narrative arc, crafts a memorable opening and closing, tightens the language for the ear (not the page), and coaches delivery, nerves, and Q&A. Works for keynotes, work presentations, pitches, toasts, weddings, and eulogies.
Keywords: public speaking, speech, presentation, talk, keynote, toast, wedding speech, eulogy, pitch, stage fright, speaking anxiety, storytelling, delivery, Q&A, slides.
When to use vs. not
Use this to plan, write, rehearse, or get feedback on any spoken delivery, and to manage speaking anxiety. It coaches structure and delivery — it can't rehearse your body language for you, so it always pushes the speaker to practice out loud. For severe, clinical anxiety, suggest professional support alongside the practical techniques.
Inputs to gather first
- Occasion + audience (who, how many, how formal, what they care about).
- Goal — what should the audience think, feel, or do afterward?
- Time limit and format (slides? podium? virtual? toast at a table?).
- Raw material — the speaker's points, stories, data, or a draft.
- Concerns — nerves, time overrun, a tough crowd, or Q&A.
Workflow
- Find the one core message. Force it into a single sentence the audience should remember. Everything serves this; if it doesn't, cut it. A talk about everything lands nothing.
- Define the goal as an outcome. Inform, persuade, inspire, or entertain — and what the audience does next. This sets tone and structure.
- Choose a structure / arc. Match the occasion: problem→solution, story arc, "What? So what? Now what?", or for toasts the relationship→anecdote→wish shape. One idea per section. See
references/structure-and-stories.md. - Write a strong open and close. Open with a hook (story, question, surprising fact, vivid image) — never "Hi, today I'm going to talk about." Close with a callback to the core message and a clear final line; for persuasion, an explicit call to action. The first and last 30 seconds carry the most weight.
- Write for the ear. Short sentences, concrete words, signposting ("three things…"), pauses, and stories over abstraction. Read it aloud and cut anything that trips the tongue. See
references/delivery-and-nerves.md. - Design slides as support, not script (if any): one idea per slide, visuals over bullet walls, never read them verbatim. The speaker is the message; slides are the echo.
- Rehearse out loud + time it. Practice standing, aloud, ideally recorded. Trim to ~90% of the limit. Internalize beats and transitions, not a word-for-word script (which sounds robotic and breaks under nerves).
- Prep nerves + Q&A. A breathing/warm-up routine, a reframe of adrenaline as energy, anticipated questions with crisp answers, and a graceful "I don't know — I'll follow up" line. See
references/delivery-and-nerves.md.
Decision framework
| Occasion | Structure | Tone |
| Conference talk | Story or problem→solution, one big idea | Engaging, authoritative |
| Work presentation | Bottom-line-up-front, then support | Clear, concise |
| Sales/investor pitch | Problem → solution → proof → ask | Confident, tight |
| Toast / wedding | Relationship → short anecdote → heartfelt wish | Warm, brief, personal |
| Eulogy | Who they were → 1–2 stories → what they leave us | Sincere, gentle, brief |
| Persuasive | Hook → stakes → argument → call to action | Conviction |
Worked example
See examples/wedding-toast.md for a structured, timed best-man toast built from rough notes.
Best Practices
- One core message. If the audience remembers one thing, what is it?
- Open with a hook, close with a callback — bookend the core message.
- Tell stories. Concrete beats abstract; people remember narrative, not bullet points.
- Write for the ear and rehearse aloud — and time it under the limit.
- Slides support, never script. You are the talk.
- Reframe nerves as energy; pause and breathe — silence reads as confidence.
Common Pitfalls
- No single message — trying to cover everything.
- Weak open ("Um, so, today…") that loses the room in 10 seconds.
- Reading slides or a word-for-word script in a monotone.
- Going over time — disrespects the audience and gets you cut off.
- Memorizing verbatim, then blanking when one word slips.
- No rehearsal out loud — silent review hides every stumble.
- For toasts/eulogies: too long, too many inside jokes, or winging it.
Other versions2 projects use a version of this.
Word for word · 2
- jaskirat1616/grok-skills★ 22100% same
- JayRHa/AgentSkills★ 12100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- 0-templateSkill
- ab-test-analyzerSkill
- adr-authorSkill
- api-designerSkill
- api-docs-writerSkill
- aws-cost-optimizerSkill
- bash-script-hardeningSkill
- blog-post-writerSkill
- book-summarizerSkill
- changelog-keeperSkill
- chart-chooserSkill
- code-reviewerSkill
- competitive-analysisSkill
- concept-explainerSkill
- cover-letter-writerSkill
- cron-schedulerSkill
- data-pipeline-architectSkill
- debug-detectiveSkill
- decision-matrixSkill
- dependency-upgraderSkill
- dockerfile-proSkill
- email-composerSkill
- error-handling-patternsSkill
- event-plannerSkill
- flashcard-generatorSkill
- gdpr-data-mapperSkill
- gift-advisorSkill
- github-actions-builderSkill
- git-workflowSkill
- habit-builderSkill
- incident-postmortemSkill
- interview-prepSkill
- job-description-writerSkill
- json-schema-authorSkill
- kubernetes-manifest-authorSkill
- language-tutorSkill
- meal-plan-builderSkill
- meeting-summarizerSkill
- mermaid-diagram-builderSkill
- nginx-config-proSkill
- observability-setupSkill
- okr-writerSkill
- pandas-data-cleaningSkill
- people-dataSkill
- performance-profilerSkill
- personal-budget-plannerSkill
- presentation-builderSkill
- project-plannerSkill
- prompt-engineerSkill
- proofreaderSkill
- rag-pipeline-designerSkill
- readme-generatorSkill
- refactoring-guideSkill
- regex-architectSkill
- release-notes-writerSkill
- resume-writerSkill
- salary-negotiatorSkill
- secrets-managerSkill
- secure-code-reviewSkill
- secure-password-policySkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

