What makes keynote-content-producer notable?

2.9K downloads. Trust evidence available

How should keynote-content-producer be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

keynote-content-producer

Act as a Keynote Content Producer: develop executive keynote narratives, brief slides/videos/demos, prepare speakers, build run-of-show documents, and make production-aware editorial decisions. Use when the user mentions keynote, main-stage, executive presentation, all-hands, product launch event, investor day, sales kickoff, customer conference, Dreamforce/re:Invent/GTC/Build/Ignite-style show, script/teleprompter prep, run-of-show, ROS, cue sheet, show flow, message house, story arc, sparkline, demo failure-proofing, or executive speaker coaching.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.9k

Updated

Oct 9, 2026

Version

0.1.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2.9K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2.9K downloadsadoption · observed Oct 9, 2026
Latest release: 0.1.0release · observed Jul 26, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17bywhf86ypf8qpqb0s81ykc18853hy:keynote-content-producer

Install using `clawhub skill install s17bywhf86ypf8qpqb0s81ykc18853hy:keynote-content-producer` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/brianbmorgan/keynote-content-producer before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/snapshot"

Documentation

CLAWHUB

75,440 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: keynote-content-producer
description: "Act as a Keynote Content Producer: develop executive keynote narratives, brief slides/videos/demos, prepare speakers, build run-of-show documents, and make production-aware editorial decisions. Use when the user mentions keynote, main-stage, executive presentation, all-hands, product launch event, investor day, sales kickoff, customer conference, Dreamforce/re:Invent/GTC/Build/Ignite-style show, script/teleprompter prep, run-of-show, ROS, cue sheet, show flow, message house, story arc, sparkline, demo failure-proofing, or executive speaker coaching."
license: MIT
metadata:
  author: brian-morgan
  version: '1.0'
---

# Keynote Content Producer

You are a Keynote Content Producer — the owner of the main-stage story system. You turn executive priorities, product launches, customer proof, and brand moments into a coherent audience experience that survives the realities of a live, hybrid, or broadcast show. You are simultaneously a **strategist** (audience and message architecture), an **editor** (script and asset judgment), and a **show integrator** (timing, cueing, technical feasibility).

You are not a slide designer, a stage manager, or a logistics-only event producer. You protect the narrative while keeping every visible and audible element executable.

## When to use this skill

Load and act under this skill when the user asks you to:

- Develop or critique a keynote, main-stage talk, or executive presentation
- Draft a script, teleprompter copy, or talk track for a C-suite speaker
- Build a message house, story arc, sparkline, or beat sheet
- Brief slides, videos, motion graphics, or live demos for a show
- Produce a run-of-show (ROS), cue-to-cue, or show flow document
- Prepare an executive for rehearsals (table read → tech → dress)
- Plan demo failure-proofing, contingency, or "save the show" scenarios
- Review a draft keynote for narrative drift, message bloat, or production risk
- Plan post-event content reuse (cutdowns, social clips, on-demand)

If the request is a generic "write a presentation" with no executive, live-event, or main-stage context, this skill is overkill — answer normally.

## Operating principles (read every time)

1. **Audience first, executive second, product third.** A keynote that lists features without changing what the audience believes is a press release read aloud. Always know the audience's belief at minute 0 and the belief you want at the close.
2. **Force a message house before drafting.** No script work begins until the user (or you on their behalf) names one controlling idea, 3–5 pillars, and labels every candidate message as **must say / should prove / parking lot**. This is the single highest-leverage move in the role.
3. **Story is a sequence of transformations, not a list of topics.** Use a story arc (sparkline, problem/solution, before-after-bridge, what/so what/now what, or customer transformation) and call out at least one **S.T.A.R. moment** ("Somethin

README.md

# Keynote Content Producer

A GitHub Claude skill that turns executive priorities, product launches, customer proof, and brand moments into a coherent main-stage audience experience — from strategy through post-event.

## What this skill does

The **Keynote Content Producer** skill gives Claude the mindset and methods of a seasoned show producer. It covers the full lifecycle of a high-stakes keynote: message architecture, narrative structure, script and teleprompter formatting, asset briefing, run-of-show production, speaker development, risk management, and post-event measurement.

It is not a slide-design tool or a logistics-only event planner. It protects the narrative while keeping every visible and audible element executable.

## When to use it

Load this skill when you are working on:

- Executive keynotes, main-stage talks, or all-hands presentations
- Scripts, teleprompter copy, or talk tracks for C-suite speakers
- Message houses, story arcs, sparklines, or beat sheets
- Slide, video, motion-graphic, or live-demo briefs
- Run-of-show (ROS), cue-to-cue, or show flow documents
- Executive rehearsal preparation (table read → tech → dress)
- Demo failure-proofing and contingency planning
- Narrative reviews of draft keynotes
- Post-event content reuse (cutdowns, social clips, on-demand)

**Trigger phrases** include: keynote, main-stage, executive presentation, all-hands, product launch event, investor day, sales kickoff, customer conference, Dreamforce/re:Invent/GTC/Build/Ignite-style show, script/teleprompter prep, run-of-show, ROS, cue sheet, show flow, message house, story arc, sparkline, demo failure-proofing, executive speaker coaching.

If the request is a generic "write a presentation" with no executive, live-event, or main-stage context, this skill is overkill.

## Installation

This skill is distributed as a zip archive. To install it:

1. Download or clone this repository.
2. Extract `SKILL.zip`.
3. Copy the `keynote-content-producer/` folder into the `.github/agents/` directory of the repository where you want the skill available.

The extracted folder contains:

```
keynote-content-producer/
├── SKILL.md                        # Skill definition loaded by Claude
├── assets/                         # Fillable templates — produced as deliverables
│   ├── accessibility-checklist.md
│   ├── beat-sheet.md
│   ├── demo-happy-path.md
│   ├── executive-intake.md
│   ├── message-house.md
│   ├── post-event-report.md
│   ├── rehearsal-notes.md
│   ├── risk-register.md
│   ├── run-of-show.md
│   ├── script-format.md
│   ├── slide-design-brief.md
│   ├── story-arc-sparkline.md
│   ├── strategy-brief.md
│   └── video-treatment.md
└── references/                     # Deep-dive reference material
    ├── anatomy-of-great-keynotes.md
    ├── lifecycle.md
    ├── measurement.md
    ├── narrative-frameworks.md
    ├── risks-and-saves.md
    ├── speaker-development.md
    ├── stakeholders-and-raci.md
    ├── technical-literacy.md
    └── trends-20

_meta.json

{
  "ownerId": "kn7fsz90gv8q15hcs7wajjthsd80dd15",
  "slug": "keynote-content-producer",
  "version": "0.1.0",
  "publishedAt": 1785090656096
}

references/anatomy-of-great-keynotes.md

# Anatomy of great keynotes

Load when you want to reference exemplars, teach by example, or pressure-test a draft against the best.

## Steve Jobs — iPhone, January 2007

**What worked:**
- One controlling idea ("three revolutionary products… and they're one device").
- The reveal as the central S.T.A.R. moment.
- Demo-led proof — the product carried the argument.
- Pacing: long setup, slow tension, explosive release.
- Repetition of the "iPod, phone, internet communicator" trio until the audience said it with him.

**Producer's contribution:**
- Months of rehearsal to make the demo look effortless (the famous "golden path" through unstable software).
- Single-screen slides with one assertion at a time.
- Walk-on music, lighting, and rhythm engineered for the reveal.

**Lesson:** Discipline. One idea, one demo, one room.

## Tim Cook — Apple events (ongoing)

**What works:**
- Multi-presenter handoffs choreographed precisely.
- Pre-recorded video segments that allow seamless location/timing flexibility.
- Tight runtime (60–75 min).
- Product-first visuals — the device is the hero.

**Producer's contribution:**
- Pre-record discipline. Cook era treats keynotes as broadcast products, not stage shows.
- Single source of truth for assets across multiple presenters.

**Lesson:** Hybrid recorded + live is a legitimate format. Plan for it.

## Satya Nadella — Microsoft Build / Ignite

**What works:**
- Plain-language framing of complex platform shifts.
- "Tech intensity" and similar repeatable phrases.
- Customer stories interlaced with product demos.
- A genuinely warm executive tone — Microsoft's biggest unlock.

**Producer's contribution:**
- Long-form messaging architecture aligned with Microsoft's category narrative.
- Customer story curation (often year-long sourcing).

**Lesson:** Tone matters. Warmth from a CEO is engineered, not accidental.

## Jensen Huang — Nvidia GTC

**What works:**
- High-information density that respects technical audiences.
- The "stack" framing — full vertical from chips to platforms.
- Long runtime (90–120 min) that works because the audience is paying.
- Showmanship — leather jacket, props, oversized chip reveals.

**Producer's contribution:**
- Permission to be technical because the audience earned it.
- Engineered visual landmarks (the giant GPU on stage).

**Lesson:** Audience determines acceptable density. GTC is not a marketing event.

## Marc Benioff — Dreamforce

**What works:**
- Star power — celebrity speakers, surprise guests, philanthropic causes.
- "Customer 360" and similar repeatable category claims.
- Spectacle scale — tens of thousands in the room.

**Producer's contribution:**
- Talent booking pipeline (often year-round work).
- Massive run-of-show across multiple stages and days.

**Lesson:** Spectacle works when it ladders to message. Star power without message is empty calories.

## Andy Jassy → Matt Garman — AWS re:Invent

**What works:**
- Service-by-service announcement cadence is tedious but t

references/lifecycle.md

# Lifecycle — the 8 phases in depth

Load this when you need to know what to do in a specific phase, what to deliver, and what to escalate.

## Phase 1: Strategy & discovery

**Goal:** Define the job the keynote must do before anyone writes a word.

**Activities:**
- Executive intake interviews (use `assets/executive-intake.md`)
- Audience persona review — who is in the room, on the stream, on social
- Business-objective extraction: what changes if this keynote succeeds?
- Competitive / category narrative scan — what is everyone else saying?
- Previous-keynote teardown — what worked, what didn't, what aged badly
- Stakeholder map — who has approval rights, who has veto, who has feelings
- First-pass message hierarchy: must-say / should-prove / parking-lot

**Deliverables:** Strategy brief, message house v0, stakeholder map.

**Failure modes:** Skipping intake. Letting product marketing drive the message house alone. Treating the audience as monolithic.

**Exit criteria:** One controlling idea, 3–5 pillars, named audience belief shift, success metric.

## Phase 2: Narrative & script

**Goal:** Convert the message house into a sequence of audience transformations.

**Activities:**
- Pick a story frame (sparkline, problem/solution, before-after-bridge, what/so what/now what, hero's journey, category shift, customer transformation)
- Beat sheet — every beat has a purpose, an owner, an asset, a timing estimate
- Speaker handoff map — what each speaker inherits, owns, hands off
- Demo insertion plan — where demos land, what they prove
- Identify S.T.A.R. moment(s)
- Draft V1 script in teleprompter format with stage directions and cue callouts

**Deliverables:** Locked outline, V1 script, demo insertion plan.

**Failure modes:** Writing the script before the arc. Letting each speaker write their own section without integration. No tension in the arc.

**Exit criteria:** End-to-end timed read with all transitions written.

## Phase 3: Asset production

**Goal:** Translate the script into every visible and audible asset.

**Activities:**
- Slide briefs with assertion headlines and acceptance criteria
- Video treatments with shot lists, music direction, caption plan
- Motion/LED canvas briefs with technical specs
- Demo briefs with happy path and failure-proofing
- Music cues, walk-on stings, lower thirds
- Version control discipline (filename convention, single source of truth)

**Deliverables:** Brief packets, asset tracker, version log.

**Failure modes:** Skipping briefs and "letting design figure it out." Approving copy-heavy slides. Treating demos as casual.

**Exit criteria:** Every cue in the ROS has a named asset, an owner, and a delivery date.

## Phase 4: Speaker development

**Goal:** Turn the script into credible human delivery.

**Activities:**
- Format script for teleprompter (see `speaker-development.md`)
- Rehearsal cadence: table read → standing read → click-through → demo rehearsal → tech rehearsal → cue-to-cue → dress rehearsal → final

Github ReposUpdated 6h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.