talk-stage5-script
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.
What this skill does
# 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
```markdown
# 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.
```markdown
# 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](https://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
- Kimi prompt: [`templates/kimi-prompt-template.md`](templates/kimi-prompt-template.md)
## Related
- [Stage 4: Position](../stage-4-position/SKILL.md): prerequisite (CHECKPOINT required)
- [Stage 6: Revision](../stage-6-revision/SKILL.md): reads pitch + slides
- [Orchestrator](../orchestrator/SKILL.md)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.