Skip to content
cccskills
FreePublished on GitHub

talk-stage5-script

Develop a confirmed talk angle and title into a five-act script with speaker notes and timing. Receive a slide-by-slide specification and a completed prompt to paste into Kimi for presentation generation.

OriginalShow the original description

Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.

See how to install

Good for

  • Writing a full script after confirming the talk direction
  • Planning speaking time and pauses
  • Preparing slide specifications for a designer
  • Creating a presentation-generation prompt for Kimi

Files included (2)

  • SKILL.md6.8 KB
  • templates/kimi-prompt-template.md4.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Talk stage 5: Script

Produces the complete talk in 3 deliverables: the 5-act narrative with speaker notes, the slide specification, and the Kimi prompt ready to copy-paste.

Prerequisite: The user has validated angle + title at the Stage 4 CHECKPOINT. Do not run this stage without that confirmation.

When to use this skill

  • After Stage 4 CHECKPOINT is confirmed
  • When you have a validated angle + title
  • To produce the complete script and slide spec

What this skill does

  1. Verifies inputs: all upstream files + angle/title confirmation
  2. Loads the Kimi template: from templates/kimi-prompt-template.md
  3. Builds the pitch: 5-act structure with speaker notes and timing
  4. Builds the slide spec: slide by slide with visual, text, notes
  5. Generates the Kimi prompt: fills the template with talk content
  6. Saves 3 files

Input

  • talks/{YYYY}-{slug}-summary.md
  • talks/{YYYY}-{slug}-concepts.md
  • talks/{YYYY}-{slug}-angles.md
  • talks/{YYYY}-{slug}-titre.md
  • talks/{YYYY}-{slug}-timeline.md (optional, enriches speaker notes)
  • Chosen angle + chosen title (explicit user confirmation from Stage 4)

Output

  • talks/{YYYY}-{slug}-pitch.md
  • talks/{YYYY}-{slug}-slides.md
  • talks/{YYYY}-{slug}-kimi-prompt.md

pitch.md Format

# Pitch: {title}

**Event**: {event} | **Duration**: {duration} min | **Slides**: ~{n} slides
**Angle**: {selected angle}

---

## Global structure

| Act | Title | Duration | Slides |
|-----|-------|----------|--------|
| 1 | {act title} | {n} min | {n} slides |
...
| Total | | {duration} min | {n} slides |

---

## ACT 1: {TITLE} (Slides 1-{n}, ~{n} min)

{Narrative description of the act in 2-3 sentences: what happens, the emotion targeted}

---

**Slide {n}: {Slide title}**
- Visual: {visual description, simple and precise}
- Key text: {what appears on screen, max 10 words}
- Speaker notes: "{exact text to say, conversational and natural}"
- Duration: {n} min
- Pause: yes/no | {if yes: why, intended effect}

---

[Repeat for each slide in the act]

---

[Acts 2, 3, 4, 5: same structure]

---

## Key moments (must not be rushed)

| Moment | Slide | What happens | Technique |
|--------|-------|-------------|-----------|
| {moment} | {n} | {description} | Pause / Number / Anecdote |

---

## Timing check

| Act | Planned | Buffer | Total |
|-----|---------|--------|-------|
| ACT 1 | {n} min | 30s | {n} min |
...
| **Total** | **{n} min** | **{n} min** | **{n} min** |

Q&A planned: {n} min

slides.md Format

Slide-by-slide spec, ready to hand to a designer or pass to Kimi.

# Slides Spec: {title}

**Total**: {n} slides | **Event**: {event} | **Date**: {date}

---

### SLIDE 1: Title Slide

- **Main title**: {title}
- **Subtitle**: {subtitle or tagline}
- **Speaker**: {name}
- **Event**: {event} ({date})
- **Visual**: {background description, texture, image, mood}
- **Speaker notes**: "{text}"
- **Duration**: {n} sec

---

### SLIDE {n}: {Slide title}

- **Title**: {title}
- **Visual**: {precise visual description}
  - Type: {bar chart / timeline / diagram / big number / comparison table / screenshot placeholder}
  - Data: {specific values if chart}
- **Key text**: {what appears, max 30 words total}
- **Metrics displayed**: {numbers if metrics slide}
- **Speaker notes**: "{exact text}"
- **Duration**: {n} min
- **Act**: {act number}

---

[Repeat for each slide]

---

## Screenshots to capture

| Slide | Screenshot | Source | Status |
|-------|-----------|--------|--------|
| {n} | {description} | {tool/URL} | To capture / Available |

kimi-prompt.md

Fill the template at templates/kimi-prompt-template.md with the talk's content.

Required sections to complete:

  • Full title and subtitle
  • Speaker name + event + date + duration + language + slide count
  • Design requirements (adjust color palette if different from default)
  • Slide Content Structure (section by section, all 5 acts)
  • Screenshot placeholders (slides awaiting real captures)
  • Tone reference (adapt to the talk's style)

Verify no {PLACEHOLDER} remains in the final file before handing to the user.

Script construction rules

  • 1 idea per slide: never more, never less
  • Speaker notes = what you say, not what you read: minimal slides, conversational notes
  • Numbers are heroes: metrics appear large and alone on their slide
  • Anecdotes > explanations: "one Tuesday morning, 3 bugs..." > "git worktrees enable parallelism"
  • Explicit transitions: note the link between each act in the notes
  • Realistic timing: add 10% buffer total (slides always run long)

Anti-patterns

  • Slides loaded with bullets (never more than 5 words per line)
  • Speaker notes in technical jargon (read them aloud to validate)
  • Vague Kimi prompt ("make it look nice"): each slide must be precise
  • Omitting screenshot placeholders from the Kimi prompt
  • Generating more slides than the duration allows (2-3 min/slide for REX)

Validation checklist

  • Pitch covers 5 acts with coherent timing (within 10% of target duration)
  • Each slide has visual + text + speaker notes
  • Key moments identified (pauses, punchlines, transitions)
  • Slides spec ready to hand to a designer
  • Kimi prompt complete (all template sections filled)
  • Screenshots to capture listed with source
  • No {PLACEHOLDER} remaining in kimi-prompt.md
  • 3 files saved

Using the Kimi prompt

  1. Open {slug}-kimi-prompt.md
  2. Verify no {PLACEHOLDER} remains (search the file)
  3. Go to kimi.com (free account, no API needed)
  4. Start a new conversation
  5. Copy-paste the entire prompt
  6. Kimi generates the presentation

For iterative refinement: add follow-up messages targeting specific slides. "Slide 7: make the number larger, remove the bullet list."

Tips

  • Speaker notes are the heart of this stage; they're what distinguishes a good talk from a good slide deck
  • The Kimi template includes a dark design system with orange accent colors. Adapt Color Palette in the template if your brand has different colors
  • Generate more slides than needed in the first pass, then cut (easier than writing from scratch)

Templates

Related

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.

  • Review skills before release
  • Compare agent definitions with reference templates
  • Quickly check critical quality criteria
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 18, 2026

audit-codebase

FreeSummary

Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.

  • Assessing the overall health of an inherited project
  • Reviewing exposed credentials and security risks
  • Identifying dependency and test coverage gaps
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 18, 2026

autoresearch

FreeSummary

Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.

  • Finding code patterns to prioritize for cleanup
  • Preparing measurement files for an improvement loop
  • Repeating targeted edits to reduce casts to any
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 18, 2026

best-of-n

FreeSummary

Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.

  • Comparing implementation options before choosing one
  • Verifying a solution when a wrong choice would be costly
  • Keeping evaluation evidence for delivery or audit
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 18, 2026

canary

FreeSummary

Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.

  • Recording a healthy baseline before deployment
  • Monitoring production immediately after deployment
  • Checking key pages for slower responses or failures
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 18, 2026

catchup

FreeSummary

Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.

  • Restoring project context after /clear
  • Reviewing recent changes after a long break
  • Checking unfinished work before choosing the next task
FlorianBruniaux/claude-code-ultimate-guide6.2KUpdated Oct 18, 2026

See all skills by FlorianBruniaux

Report a problem with this skill