speaker-notes
Skill1 starsChanged 3 months agoMITView on GitHub
Write or improve speaker notes for an existing presentation, including time budgets, opening language, slide transitions, demo cues, caveats, likely audience questions, and concise answers.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- yiweiwan/skillstheir own version, first seen May 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- yiweiwan/skills★ 1same name
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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-code-styleSkill
- create-deckSkill
- deck-architectSkill
- deck-reviewerSkill
- diagram-designSkill
- review-deckSkill
- speaker-notesSkill
- visual-directorSkill
- claude-code-styleSkill
- create-deckSkill
- deck-architectSkill
- deck-reviewerSkill
- diagram-designSkill
- review-deckSkill
- visual-directorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 8
Use the current user request as the brief.
- Distinctive: line 19
Write notes in the format native to the deck when practical:
- Distinctive: line 34
Keep notes conversational, scannable, and easy to deliver.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Create speaker notes
Use the current user request as the brief. Read the complete deck, source citations, and existing notes before writing. Infer the thesis, audience expertise, intended decision, language, duration, and delivery context.
For every slide provide:
- target time
- one-sentence purpose
- a natural talk track that adds value instead of reading the slide
- transition into the next page
- pronunciation, click, animation, or demo cues where useful
- caveats and source reminders for factual claims
Write notes in the format native to the deck when practical:
- HTML:
<aside class="notes">…</aside>inside each slide. - Marp: presenter-note comments supported by the existing workflow, or a clearly mapped
speaker-notes.mdwhen portability is uncertain. - PptxGenJS:
slide.addNotes('…'). - Other formats: preserve their established notes convention.
At the end provide:
- total estimated time
- optional cuts for a shorter version
- three likely audience questions
- concise, evidence-aware answers
- one recovery line for returning to the main story after a deep question
Keep notes conversational, scannable, and easy to deliver. Do not script every word unless the user asks for a verbatim speech.
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.