Write per-slide speaker notes that a presenter can deliver, added to each slide's notes pane.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add black141312/ada --skill speaker-notes --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Speaker Notes?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/black141312-speaker-notes)More formats (shields.io, HTML) on the badges page.
---
name: speaker-notes
description: Write per-slide speaker notes that a presenter can deliver, added to each slide's notes pane.
category: pptx
---
# Speaker Notes
Use when a deck needs a spoken script or presenter guidance — slides carry the headline, notes carry what the presenter actually says.
1. Read each slide's headline and visuals to understand the point that slide must land.
2. Write the notes as spoken language: the opening line, the key point, and a transition into the next slide.
3. Keep each slide's notes to roughly 30-90 seconds of speech (about 75-200 words); trim anything the slide already shows.
4. Add timing cues, the "so what" for any chart, and reminders for demos or audience questions.
5. Write notes into `slide.notes_slide.notes_text_frame.text` in python-pptx (this auto-creates the notes slide).
6. Read the notes end-to-end as a continuous script to check the narrative flows between slides.
## Rules
- Notes are a script to speak, not bullet points to read aloud — write in full, natural sentences.
- Never just restate the slide text; add the context, story, or data interpretation behind it.
- Match the speaker's voice and the talk's time budget; cut ruthlessly if over.
- Always end a slide's notes with a one-line bridge to the next slide.
- Flag any claim that needs a source or a number the presenter must confirm.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.