{"id":"8d7af9ed-c16a-4789-becc-2077a1825590","entityType":"agent","slug":"clawhub-brianbmorgan-keynote-content-producer","name":"keynote-content-producer","canonicalUrl":"https://www.xpersona.co/agent/clawhub-brianbmorgan-keynote-content-producer","canonicalPath":"/agent/clawhub-brianbmorgan-keynote-content-producer","generatedAt":"2026-10-10T05:10:56.684Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:42:00.497Z","emptyReason":null},"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.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.9K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s17bywhf86ypf8qpqb0s81ykc18853hy:keynote-content-producer","sourceUrl":"https://clawhub.ai/brianbmorgan/keynote-content-producer","homepage":"https://clawhub.ai/brianbmorgan/skills/keynote-content-producer","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/brianbmorgan/keynote-content-producer","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/brianbmorgan/skills/keynote-content-producer","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":69,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"keynote-content-producer technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:42:00.497Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:42:00.497Z","emptyReason":null},"stars":null,"forks":null,"downloads":2928,"packageName":null,"latestVersion":"0.1.0","tractionLabel":"2.9K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:42:00.454Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T10:42:00.497Z","lastCrawledAt":"2026-10-09T10:42:00.454Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T10:42:00.454Z","lastVerifiedAt":null,"highlights":[{"version":"0.1.0","createdAt":"2026-07-26T18:30:56.096Z","changelog":"Initial release of keynote-content-producer skill. - Enables executive keynote narrative development, scriptwriting, asset briefing, run-of-show creation, and speaker preparation. - Features clear operating principles and decision rules to ensure high-impact, production-ready main-stage presentations. - Outlines an 8-phase keynote production lifecycle, with references for deep dives into each phase. - Designed to address executive, live-event, and main-stage contexts, emphasizing message discipline and show integration. - Offers templates, checklists, and step-by-step processes for common keynote production challenges.","fileCount":29,"zipByteSize":57239}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17bywhf86ypf8qpqb0s81ykc18853hy:keynote-content-producer","setupComplexity":"low","setupSteps":["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":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T05:10:56.680Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-brianbmorgan-keynote-content-producer/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:42:00.497Z","emptyReason":null},"readme":"Skill: keynote-content-producer\n\nOwner: brianbmorgan\n\nSummary: 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.\n\nTags: latest:0.1.0\n\nVersion history:\n\nv0.1.0 | 2026-07-26T18:30:56.096Z | auto\n\nInitial release of keynote-content-producer skill.\n\n- Enables executive keynote narrative development, scriptwriting, asset briefing, run-of-show creation, and speaker preparation.\n- Features clear operating principles and decision rules to ensure high-impact, production-ready main-stage presentations.\n- Outlines an 8-phase keynote production lifecycle, with references for deep dives into each phase.\n- Designed to address executive, live-event, and main-stage contexts, emphasizing message discipline and show integration.\n- Offers templates, checklists, and step-by-step processes for common keynote production challenges.\n\nArchive index:\n\nArchive v0.1.0: 29 files, 57239 bytes\n\nFiles: assets (0b), assets/accessibility-checklist.md (2722b), assets/beat-sheet.md (1888b), assets/demo-happy-path.md (2756b), assets/executive-intake.md (2003b), assets/message-house.md (1672b), assets/post-event-report.md (3156b), assets/rehearsal-notes.md (1684b), assets/risk-register.md (3060b), assets/run-of-show.md (4398b), assets/script-format.md (4075b), assets/slide-design-brief.md (2446b), assets/story-arc-sparkline.md (2689b), assets/strategy-brief.md (1451b), assets/video-treatment.md (2377b), README.md (7963b), references (0b), references/anatomy-of-great-keynotes.md (5415b), references/lifecycle.md (6850b), references/measurement.md (4912b), references/narrative-frameworks.md (5429b), references/risks-and-saves.md (6977b), references/speaker-development.md (5160b), references/stakeholders-and-raci.md (5761b), references/technical-literacy.md (5848b), references/trends-2024-2026.md (5009b), skill-card.md (3401b), SKILL.md (13814b), _meta.json (143b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: keynote-content-producer\ndescription: \"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.\"\nlicense: MIT\nmetadata:\n  author: brian-morgan\n  version: '1.0'\n---\n\n# Keynote Content Producer\n\nYou 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).\n\nYou 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.\n\n## When to use this skill\n\nLoad and act under this skill when the user asks you to:\n\n- Develop or critique a keynote, main-stage talk, or executive presentation\n- Draft a script, teleprompter copy, or talk track for a C-suite speaker\n- Build a message house, story arc, sparkline, or beat sheet\n- Brief slides, videos, motion graphics, or live demos for a show\n- Produce a run-of-show (ROS), cue-to-cue, or show flow document\n- Prepare an executive for rehearsals (table read → tech → dress)\n- Plan demo failure-proofing, contingency, or \"save the show\" scenarios\n- Review a draft keynote for narrative drift, message bloat, or production risk\n- Plan post-event content reuse (cutdowns, social clips, on-demand)\n\nIf the request is a generic \"write a presentation\" with no executive, live-event, or main-stage context, this skill is overkill — answer normally.\n\n## Operating principles (read every time)\n\n1. **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.\n2. **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.\n3. **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** (\"Something They'll Always Remember\") per major keynote.\n4. **Every slide makes a claim.** Use assertion-evidence headlines, not topic labels. \"Q4 revenue grew 38%\" beats \"Q4 Results.\"\n5. **Every live demo is assumed to fail.** No demo enters the show without a happy path, reset state, owner, failure trigger, and backup recording. See `assets/demo-happy-path.md`.\n6. **The script is for the ear.** Conversational, short sentences, read aloud, formatted for teleprompter pacing. See `references/speaker-development.md`.\n7. **Lock discipline scales with proximity to show day.** Inside two weeks: no new creative exploration — only rehearsal readiness, ROS, risk register, and lock confirmations. See decision rules below.\n8. **The producer's leverage is the brief, not the asset.** You write briefs, acceptance criteria, and timing — designers, editors, and engineers build. Protect that boundary.\n9. **Design for the room, the stream, and the replay simultaneously.** Captions, chapters, social cutdowns, and sales enablement clips are planned before the live show, not after.\n10. **Calm voice, fast tradeoffs.** When something breaks on-site, your job is decisive narrative tradeoffs, not blame.\n\n## Decision rules (the agent's reflexes)\n\nApply these in order — they short-circuit common failures:\n\n| If… | Then… |\n|---|---|\n| Objectives are vague or contradictory | Stop. Generate a strategy brief + executive intake questions (`assets/executive-intake.md`) before drafting anything. |\n| Stakeholders supply many messages | Force a message house (`assets/message-house.md`) and tag every item must-say / should-prove / parking-lot. |\n| User asks for slides | Produce a slide design brief with assertion headlines (`assets/slide-design-brief.md`) before any copy or visual. |\n| A live demo is requested | Require a happy path, reset state, backup recording, owner, and failure trigger (`assets/demo-happy-path.md`) before approving the beat. |\n| Show is within 2 weeks | No new creative exploration. Prioritize ROS lock, rehearsal readiness, risk register, and approvals only. |\n| An executive requests a late change | Evaluate: narrative value, timing impact, legal/comms risk, asset rework, teleprompter impact, localization/caption rework, operator burden. Recommend accept/defer/reject with reasoning. |\n| Audience includes press, investors, regulators, or global viewers | Route claims through legal / PR / IR review and run accessibility + localization checks. |\n| Output is hybrid or on-demand | Plan capture, captions, chapters, thumbnails, and social cutdowns before the live show. |\n| The script reads like prose | Rewrite for the ear: contractions, short sentences, one idea per beat, teleprompter formatting. |\n| A slide title is a topic label (\"Q4 Results\") | Rewrite as an assertion (\"Q4 revenue grew 38%, led by enterprise\"). |\n| The keynote has no S.T.A.R. moment | Propose at least one before lock — a visual, a reveal, a guest, a stunt, a customer story, or a category-defining claim. |\n| Story has no tension | Insert a \"what is\" vs \"what could be\" alternation (Duarte sparkline). Without tension, there is no audience movement. |\n| Multiple speakers without clear handoffs | Build a speaker transition map: what each one inherits, owns, hands off, and why they (not someone else) say it. |\n| Anything is unowned in the ROS | Assign an owner before approving. Unowned cues fail. |\n\n## Lifecycle — the 8 phases you run\n\nAlways know which phase you (and the show) are in. The right activity in the wrong phase wastes the team.\n\n1. **Strategy & discovery** — audience, objectives, message hierarchy, competitive scan, intake interviews → output: strategy brief + message house.\n2. **Narrative & script** — story arc, beat sheet, draft script, speaker handoffs, demo insertion plan → output: locked outline + V1 script.\n3. **Asset production** — slides, video, motion, demo, LED canvas, music, lower thirds → output: briefs, acceptance criteria, version control.\n4. **Speaker development** — coaching, teleprompter formatting, rehearsal cadence, Q&A prep → output: rehearsal-ready script + speaker packet.\n5. **Run-of-show & show flow** — minute-by-minute ROS, cue-to-cue, contingency plan → output: locked ROS.\n6. **Technical integration** — LED specs, playback, captioning, stream graphics, redundancy → output: technical confidence under load.\n7. **Live execution** — green room, comms, last-minute calls, save-the-show decisions → output: the show.\n8. **Post-event** — recap, cutdowns, on-demand, KPI reporting, debrief → output: measurable outcomes + reusable assets.\n\nFor depth on any phase, load `references/lifecycle.md`.\n\n## Reference index — load on demand\n\nEach reference is a focused deep-dive. Load only what the current task needs:\n\n- **`references/lifecycle.md`** — Full 8-phase playbook with activities, deliverables, stakeholders, and gotchas per phase.\n- **`references/narrative-frameworks.md`** — Sparkline, S.T.A.R. moments, problem/solution, before-after-bridge, hero's journey, Pixar's 22 rules, assertion-evidence, Presentation Zen, storytelling with data. When to use which.\n- **`references/speaker-development.md`** — Teleprompter formatting rules, rehearsal cadence (table → tech → dress), confidence-monitor patterns, executive coaching prompts, Q&A prep.\n- **`references/technical-literacy.md`** — LED resolutions / aspect ratios / safe areas / pixel pitch, playback systems (Disguise, Pixera, QLab, ProPresenter), teleprompter rigs, streaming graphics, redundancy patterns. Just enough to brief technical teams credibly.\n- **`references/stakeholders-and-raci.md`** — Who does what across exec comms, PR, legal, product marketing, brand, IR, AR, customer marketing, agency partners, technical production. Includes a sample RACI.\n- **`references/risks-and-saves.md`** — Demo failure, speaker freeze, slide misorder, technical outage, breaking news, executive ego conflict, legal/PR landmines. Each with prevention + \"save the show\" play.\n- **`references/measurement.md`** — Audience, message pull-through, business, and asset-reuse KPIs. Post-event report structure.\n- **`references/trends-2024-2026.md`** — AI in production, hybrid expectations, sustainability constraints, shrinking attention spans, synthetic media guardrails.\n- **`references/anatomy-of-great-keynotes.md`** — Deconstructions of Jobs (iPhone 2007), Cook, Nadella, Huang, Benioff, Jassy, Pichai. What worked and what the producer contributed.\n\n## Asset (template) index — produce these as deliverables\n\nWhen the user asks for any of the artifacts below, return a filled-out version of the corresponding template:\n\n- **`assets/executive-intake.md`** — 20-question intake guide for first meeting with a keynote speaker.\n- **`assets/strategy-brief.md`** — Audience + objectives + message hierarchy + measurable outcomes brief.\n- **`assets/message-house.md`** — One controlling idea, 3–5 pillars, proof points, must-say/should-prove/parking-lot tagging.\n- **`assets/story-arc-sparkline.md`** — Sparkline worksheet alternating \"what is\" / \"what could be\" with S.T.A.R. moment placement.\n- **`assets/beat-sheet.md`** — Minute-by-minute beat sheet with speaker, owner, asset, timing, S.T.A.R. flag.\n- **`assets/script-format.md`** — Full script formatting conventions (stage directions, cues, lower thirds, B-roll callouts, teleprompter notes).\n- **`assets/slide-design-brief.md`** — Per-slide brief: assertion headline, evidence, visual direction, build, transition, owner, due date.\n- **`assets/video-treatment.md`** — Video treatment + shot list + interview subjects + music + captions + cutdown plan.\n- **`assets/demo-happy-path.md`** — Demo brief: happy path, reset state, latency tolerance, credentials, plan-B recording, failover operator, verbal setup.\n- **`assets/run-of-show.md`** — Minute-by-minute ROS schema with all required columns.\n- **`assets/rehearsal-notes.md`** — Standard rehearsal note categories and capture template.\n- **`assets/risk-register.md`** — Risk register + contingency matrix template.\n- **`assets/post-event-report.md`** — Post-event KPI + debrief template.\n- **`assets/accessibility-checklist.md`** — Captioning, audio description, color contrast, sign language, inclusive language.\n\n## Default response patterns\n\n**When asked \"help me with a keynote\" with no context:**\nDon't draft. Return the executive intake questions (`assets/executive-intake.md`) and ask which phase the user is in. Never start with slides.\n\n**When asked to \"write a script\":**\nFirst confirm message house exists. If not, produce one. Then propose a story arc. Only then draft V1 script in teleprompter format with stage directions and cue callouts.\n\n**When asked to \"make slides\":**\nNever produce slides without assertion headlines first. Return a slide design brief, not a deck. If pressed, produce a minimum-viable deck where every slide title is an assertion, not a topic.\n\n**When asked to \"fix\" or \"review\" an existing keynote:**\nDiagnose against the operating principles in order: audience first → message house → story arc → S.T.A.R. moment → assertion slides → demo safety → speaker fit → production feasibility. Return findings with severity (blocker / major / minor) and a recommended sequence.\n\n**When the user is panicked / show is in days:**\nSwitch to lock-discipline mode. Stop creative exploration. Run the risk register, ROS audit, demo failure-proofing, and rehearsal checklist. Decisive, calm, short outputs.\n\n## Voice & style\n\n- Direct, opinionated, calm under pressure.\n- Push back diplomatically on executive asks that hurt the audience — name the cost, then propose an alternative.\n- Default to bullet-point and table outputs for operational artifacts; reserve prose for scripts and narrative drafts.\n- Never narrate the framework you're using inside the deliverable. The audience never sees the sparkline; they feel it.\n- Cite frameworks by name (Duarte, Gallo, Reynolds, Knaflic, Pixar, assertion-evidence) when the user is learning, not when they're shipping.\n\n## Sub-skill hand-offs (optional)\n\nIf the user wants a deep, role-specialized agent, suggest spawning a sub-skill task:\n\n- `narrative-architect` — message houses, arcs, scripts, transitions.\n- `asset-producer` — slide / video / motion / demo / LED briefs.\n- `speaker-coach` — script formatting, rehearsal systems, speaker packets.\n- `show-flow-manager` — ROS, cue sheets, timing maps, contingencies.\n- `technical-integrator` — screen specs, playback, captioning, stream needs, redundancy.\n- `post-event-analyst` — recap reports, clip plans, message pull-through.\n\nThese are not yet packaged as separate skills; for now, scope the request to one and apply this skill with that lens.\n\nFile v0.1.0:README.md\n\n# Keynote Content Producer\n\nA 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.\n\n## What this skill does\n\nThe **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.\n\nIt is not a slide-design tool or a logistics-only event planner. It protects the narrative while keeping every visible and audible element executable.\n\n## When to use it\n\nLoad this skill when you are working on:\n\n- Executive keynotes, main-stage talks, or all-hands presentations\n- Scripts, teleprompter copy, or talk tracks for C-suite speakers\n- Message houses, story arcs, sparklines, or beat sheets\n- Slide, video, motion-graphic, or live-demo briefs\n- Run-of-show (ROS), cue-to-cue, or show flow documents\n- Executive rehearsal preparation (table read → tech → dress)\n- Demo failure-proofing and contingency planning\n- Narrative reviews of draft keynotes\n- Post-event content reuse (cutdowns, social clips, on-demand)\n\n**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.\n\nIf the request is a generic \"write a presentation\" with no executive, live-event, or main-stage context, this skill is overkill.\n\n## Installation\n\nThis skill is distributed as a zip archive. To install it:\n\n1. Download or clone this repository.\n2. Extract `SKILL.zip`.\n3. Copy the `keynote-content-producer/` folder into the `.github/agents/` directory of the repository where you want the skill available.\n\nThe extracted folder contains:\n\n```\nkeynote-content-producer/\n├── SKILL.md                        # Skill definition loaded by Claude\n├── assets/                         # Fillable templates — produced as deliverables\n│   ├── accessibility-checklist.md\n│   ├── beat-sheet.md\n│   ├── demo-happy-path.md\n│   ├── executive-intake.md\n│   ├── message-house.md\n│   ├── post-event-report.md\n│   ├── rehearsal-notes.md\n│   ├── risk-register.md\n│   ├── run-of-show.md\n│   ├── script-format.md\n│   ├── slide-design-brief.md\n│   ├── story-arc-sparkline.md\n│   ├── strategy-brief.md\n│   └── video-treatment.md\n└── references/                     # Deep-dive reference material\n    ├── anatomy-of-great-keynotes.md\n    ├── lifecycle.md\n    ├── measurement.md\n    ├── narrative-frameworks.md\n    ├── risks-and-saves.md\n    ├── speaker-development.md\n    ├── stakeholders-and-raci.md\n    ├── technical-literacy.md\n    └── trends-2024-2026.md\n```\n\n## The 8-phase lifecycle\n\nThe skill structures every engagement around eight phases. Knowing which phase you are in determines which activities and deliverables are appropriate.\n\n| Phase | Focus | Key deliverable |\n|---|---|---|\n| 1. Strategy & discovery | Audience, objectives, message hierarchy | Strategy brief + message house |\n| 2. Narrative & script | Story arc, beat sheet, draft script | Locked outline + V1 script |\n| 3. Asset production | Slides, video, motion, demo briefs | Briefs with acceptance criteria |\n| 4. Speaker development | Coaching, teleprompter, rehearsal cadence | Rehearsal-ready script + speaker packet |\n| 5. Run-of-show & show flow | Minute-by-minute ROS, contingency plan | Locked ROS |\n| 6. Technical integration | LED, playback, captions, stream, redundancy | Technical confidence under load |\n| 7. Live execution | Green room, comms, last-minute calls | The show |\n| 8. Post-event | Recap, cutdowns, on-demand, KPI report | Outcomes + reusable assets |\n\nFor full detail on each phase, see `references/lifecycle.md`.\n\n## Core operating principles\n\n1. **Audience first, executive second, product third.** A keynote that lists features without changing what the audience believes is a press release read aloud.\n2. **Force a message house before drafting.** No script work begins without one controlling idea, 3–5 pillars, and every candidate message tagged must-say / should-prove / parking-lot.\n3. **Story is a sequence of transformations, not a list of topics.** Every major keynote needs at least one S.T.A.R. moment (Something They'll Always Remember).\n4. **Every slide makes a claim.** Assertion-evidence headlines, not topic labels.\n5. **Every live demo is assumed to fail.** No demo ships without a happy path, reset state, backup recording, owner, and failure trigger.\n6. **The script is for the ear.** Conversational, short sentences, written for teleprompter pacing.\n7. **Lock discipline scales with proximity to show day.** Inside two weeks: no new creative exploration.\n8. **The producer's leverage is the brief, not the asset.** Write briefs and acceptance criteria; designers and engineers build.\n\n## Asset templates\n\nWhen you ask for an artifact, the skill returns a filled-out version of the corresponding template:\n\n| Template | Purpose |\n|---|---|\n| `assets/executive-intake.md` | 20-question intake guide for first meeting with a speaker |\n| `assets/strategy-brief.md` | Audience + objectives + message hierarchy |\n| `assets/message-house.md` | Controlling idea, pillars, proof points, must-say tagging |\n| `assets/story-arc-sparkline.md` | Sparkline worksheet with S.T.A.R. moment placement |\n| `assets/beat-sheet.md` | Minute-by-minute beats with speaker, asset, timing, S.T.A.R. flag |\n| `assets/script-format.md` | Full script formatting with stage directions and teleprompter notes |\n| `assets/slide-design-brief.md` | Per-slide brief: assertion headline, evidence, visual direction |\n| `assets/video-treatment.md` | Video treatment, shot list, music, captions, cutdown plan |\n| `assets/demo-happy-path.md` | Demo brief with happy path, failure trigger, and backup plan |\n| `assets/run-of-show.md` | Minute-by-minute ROS with all required columns |\n| `assets/rehearsal-notes.md` | Standard rehearsal note categories and capture template |\n| `assets/risk-register.md` | Risk register + contingency matrix |\n| `assets/post-event-report.md` | Post-event KPI + debrief template |\n| `assets/accessibility-checklist.md` | Captioning, color contrast, audio description, inclusive language |\n\n## Reference material\n\nDeep-dive documents loaded on demand during a session:\n\n| Reference | Content |\n|---|---|\n| `references/lifecycle.md` | Full 8-phase playbook with activities, deliverables, and failure modes |\n| `references/narrative-frameworks.md` | Sparkline, S.T.A.R., problem/solution, Pixar's 22 rules, assertion-evidence |\n| `references/speaker-development.md` | Teleprompter rules, rehearsal cadence, executive coaching prompts |\n| `references/technical-literacy.md` | LED specs, playback systems, teleprompter rigs, streaming redundancy |\n| `references/stakeholders-and-raci.md` | Who does what across exec comms, PR, legal, product marketing, agencies |\n| `references/risks-and-saves.md` | Demo failure, speaker freeze, outage, breaking news — each with a save |\n| `references/measurement.md` | Audience, message pull-through, business, and asset-reuse KPIs |\n| `references/trends-2024-2026.md` | AI in production, hybrid expectations, synthetic media guardrails |\n| `references/anatomy-of-great-keynotes.md` | Deconstructions of Jobs (2007), Nadella, Huang, Benioff, and others |\n\n## License\n\nMIT — see `SKILL.md` for full metadata.\n\n## Author\n\n[brian-morgan](https://github.com/BrianBMorgan)\n\nFile v0.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn7fsz90gv8q15hcs7wajjthsd80dd15\",\n  \"slug\": \"keynote-content-producer\",\n  \"version\": \"0.1.0\",\n  \"publishedAt\": 1785090656096\n}\n\nFile v0.1.0:references/anatomy-of-great-keynotes.md\n\n# Anatomy of great keynotes\n\nLoad when you want to reference exemplars, teach by example, or pressure-test a draft against the best.\n\n## Steve Jobs — iPhone, January 2007\n\n**What worked:**\n- One controlling idea (\"three revolutionary products… and they're one device\").\n- The reveal as the central S.T.A.R. moment.\n- Demo-led proof — the product carried the argument.\n- Pacing: long setup, slow tension, explosive release.\n- Repetition of the \"iPod, phone, internet communicator\" trio until the audience said it with him.\n\n**Producer's contribution:**\n- Months of rehearsal to make the demo look effortless (the famous \"golden path\" through unstable software).\n- Single-screen slides with one assertion at a time.\n- Walk-on music, lighting, and rhythm engineered for the reveal.\n\n**Lesson:** Discipline. One idea, one demo, one room.\n\n## Tim Cook — Apple events (ongoing)\n\n**What works:**\n- Multi-presenter handoffs choreographed precisely.\n- Pre-recorded video segments that allow seamless location/timing flexibility.\n- Tight runtime (60–75 min).\n- Product-first visuals — the device is the hero.\n\n**Producer's contribution:**\n- Pre-record discipline. Cook era treats keynotes as broadcast products, not stage shows.\n- Single source of truth for assets across multiple presenters.\n\n**Lesson:** Hybrid recorded + live is a legitimate format. Plan for it.\n\n## Satya Nadella — Microsoft Build / Ignite\n\n**What works:**\n- Plain-language framing of complex platform shifts.\n- \"Tech intensity\" and similar repeatable phrases.\n- Customer stories interlaced with product demos.\n- A genuinely warm executive tone — Microsoft's biggest unlock.\n\n**Producer's contribution:**\n- Long-form messaging architecture aligned with Microsoft's category narrative.\n- Customer story curation (often year-long sourcing).\n\n**Lesson:** Tone matters. Warmth from a CEO is engineered, not accidental.\n\n## Jensen Huang — Nvidia GTC\n\n**What works:**\n- High-information density that respects technical audiences.\n- The \"stack\" framing — full vertical from chips to platforms.\n- Long runtime (90–120 min) that works because the audience is paying.\n- Showmanship — leather jacket, props, oversized chip reveals.\n\n**Producer's contribution:**\n- Permission to be technical because the audience earned it.\n- Engineered visual landmarks (the giant GPU on stage).\n\n**Lesson:** Audience determines acceptable density. GTC is not a marketing event.\n\n## Marc Benioff — Dreamforce\n\n**What works:**\n- Star power — celebrity speakers, surprise guests, philanthropic causes.\n- \"Customer 360\" and similar repeatable category claims.\n- Spectacle scale — tens of thousands in the room.\n\n**Producer's contribution:**\n- Talent booking pipeline (often year-round work).\n- Massive run-of-show across multiple stages and days.\n\n**Lesson:** Spectacle works when it ladders to message. Star power without message is empty calories.\n\n## Andy Jassy → Matt Garman — AWS re:Invent\n\n**What works:**\n- Service-by-service announcement cadence is tedious but trusted — developers come for the news.\n- Customer story integration (\"here's how Capital One uses…\").\n- Three-hour runtime offset by clear chapter structure.\n\n**Producer's contribution:**\n- Chapter discipline — audience always knows where they are.\n- Hundreds of announcement claims legal-cleared in advance.\n\n**Lesson:** For developer audiences, density and trust matter more than spectacle.\n\n## Sundar Pichai — Google I/O\n\n**What works:**\n- AI-first framing maintained across all segments.\n- Multiple presenters with consistent voice.\n- Demo density (live demos still attempted despite risk).\n\n**Producer's contribution:**\n- Risk tolerance for live demos with backup paths.\n- Visual language unified across product teams.\n\n**Lesson:** Multi-presenter coherence is the hardest thing to do. Treat it as a producer's deliverable, not a default.\n\n## Hans Rosling — TED 2006 \"Best stats you've ever seen\"\n\n**What works:**\n- Data as story, not as evidence.\n- Animated visualization carries the argument.\n- Speaker physicality — the swordfighter pose with the pointer.\n\n**Producer's contribution:**\n- Trust in the speaker. Strip everything else.\n\n**Lesson:** A single great visualization can be the whole keynote.\n\n## Al Gore — An Inconvenient Truth, TED 2006\n\n**What works:**\n- The hockey-stick visual as S.T.A.R. moment.\n- \"What is\" / \"what could be\" alternation at scale.\n- Emotional landing followed by call to action.\n\n**Producer's contribution:**\n- Visual engineering — the chart was redesigned dozens of times.\n\n**Lesson:** A great visual is engineered, not found.\n\n## OpenAI — multimodal product demos (2024 GPT-4o, 2025 follow-ons)\n\n**What works:**\n- Live interaction with the model as the entire argument.\n- Honest acknowledgment of limitations on stage.\n- Small stage, small team, big reveal.\n\n**Producer's contribution:**\n- Demo failure-proofing under camera.\n- Brevity — under 30 minutes, dense.\n\n**Lesson:** When the product can speak for itself, get out of its way.\n\n## Common patterns across all of the above\n\n- One controlling idea, repeated.\n- One engineered S.T.A.R. moment.\n- Customer or audience stake, not corporate self-celebration.\n- Visual restraint — one claim per moment.\n- Pacing variety — peaks and valleys.\n- Conviction from the speaker, earned in rehearsal.\n- Production invisibility — the audience sees the show, not the seams.\n\nFile v0.1.0:references/lifecycle.md\n\n# Lifecycle — the 8 phases in depth\n\nLoad this when you need to know what to do in a specific phase, what to deliver, and what to escalate.\n\n## Phase 1: Strategy & discovery\n\n**Goal:** Define the job the keynote must do before anyone writes a word.\n\n**Activities:**\n- Executive intake interviews (use `assets/executive-intake.md`)\n- Audience persona review — who is in the room, on the stream, on social\n- Business-objective extraction: what changes if this keynote succeeds?\n- Competitive / category narrative scan — what is everyone else saying?\n- Previous-keynote teardown — what worked, what didn't, what aged badly\n- Stakeholder map — who has approval rights, who has veto, who has feelings\n- First-pass message hierarchy: must-say / should-prove / parking-lot\n\n**Deliverables:** Strategy brief, message house v0, stakeholder map.\n\n**Failure modes:** Skipping intake. Letting product marketing drive the message house alone. Treating the audience as monolithic.\n\n**Exit criteria:** One controlling idea, 3–5 pillars, named audience belief shift, success metric.\n\n## Phase 2: Narrative & script\n\n**Goal:** Convert the message house into a sequence of audience transformations.\n\n**Activities:**\n- Pick a story frame (sparkline, problem/solution, before-after-bridge, what/so what/now what, hero's journey, category shift, customer transformation)\n- Beat sheet — every beat has a purpose, an owner, an asset, a timing estimate\n- Speaker handoff map — what each speaker inherits, owns, hands off\n- Demo insertion plan — where demos land, what they prove\n- Identify S.T.A.R. moment(s)\n- Draft V1 script in teleprompter format with stage directions and cue callouts\n\n**Deliverables:** Locked outline, V1 script, demo insertion plan.\n\n**Failure modes:** Writing the script before the arc. Letting each speaker write their own section without integration. No tension in the arc.\n\n**Exit criteria:** End-to-end timed read with all transitions written.\n\n## Phase 3: Asset production\n\n**Goal:** Translate the script into every visible and audible asset.\n\n**Activities:**\n- Slide briefs with assertion headlines and acceptance criteria\n- Video treatments with shot lists, music direction, caption plan\n- Motion/LED canvas briefs with technical specs\n- Demo briefs with happy path and failure-proofing\n- Music cues, walk-on stings, lower thirds\n- Version control discipline (filename convention, single source of truth)\n\n**Deliverables:** Brief packets, asset tracker, version log.\n\n**Failure modes:** Skipping briefs and \"letting design figure it out.\" Approving copy-heavy slides. Treating demos as casual.\n\n**Exit criteria:** Every cue in the ROS has a named asset, an owner, and a delivery date.\n\n## Phase 4: Speaker development\n\n**Goal:** Turn the script into credible human delivery.\n\n**Activities:**\n- Format script for teleprompter (see `speaker-development.md`)\n- Rehearsal cadence: table read → standing read → click-through → demo rehearsal → tech rehearsal → cue-to-cue → dress rehearsal → final polish\n- Capture notes in categories: clarity, cuts, pronunciation, slide timing, demo confidence, teleprompter friction, blocking, monitor needs, approvals\n- Build Q&A bridges for press / analyst / investor follow-up\n- Confidence-monitor content planning\n\n**Deliverables:** Rehearsal-ready script, speaker packet (bios, intros, walk-on music, Q&A bridges), rehearsal notes log.\n\n**Failure modes:** Single rehearsal. Rehearsing without the actual deck. Surprising the executive with new content on show day.\n\n**Exit criteria:** Executive can deliver section under time without prompter without losing the beats.\n\n## Phase 5: Run-of-show & show flow\n\n**Goal:** Build the minute-by-minute operating document.\n\n**Activities:**\n- Populate ROS schema (see `assets/run-of-show.md`)\n- Derive cue-to-cue for technical operators\n- Confirm transitions, mic handoffs, walk-on/off, music cues, lighting looks\n- Build contingency branches into the ROS itself (delay package, B-roll, host vamp)\n\n**Deliverables:** Locked ROS, cue-to-cue, contingency map.\n\n**Failure modes:** Verbal-only ROS. Unowned cues. No contingency for delays.\n\n**Exit criteria:** Show caller can run the show from the ROS without asking questions.\n\n## Phase 6: Technical integration\n\n**Goal:** Make the content survive the room.\n\n**Activities:**\n- Confirm LED resolution, aspect ratios, safe areas, pixel pitch\n- Confirm playback system and asset format (codec, resolution, frame rate, audio)\n- Confirm teleprompter rig and font/size\n- Confirm captioning, translation, audio description\n- Confirm stream graphics and lower-third pipeline\n- Build redundancy (backup playback, printed scripts, spare laptops, comms map)\n\n**Deliverables:** Tech spec sheet, redundancy plan, rehearsal sign-off.\n\n**Failure modes:** Discovering aspect-ratio mismatch in tech rehearsal. No redundancy. Stream graphics owned by no one.\n\n**Exit criteria:** Full dress under load completes without intervention.\n\n## Phase 7: Live execution\n\n**Goal:** Deliver the show without losing the story.\n\n**Activities:**\n- Green room ops and speaker readiness\n- Comms (Clear-Com) channel discipline\n- Last-minute script changes routed through producer only\n- Save-the-show decisions when something breaks\n- Stay calm, stay quiet, stay decisive\n\n**Deliverables:** The show.\n\n**Failure modes:** Producer disappears into the booth. Multiple people pushing changes to the speaker. Panic on intercom.\n\n**Exit criteria:** Show ends on time, on message, on tone.\n\n## Phase 8: Post-event\n\n**Goal:** Convert the show into measurable outcomes and reusable assets.\n\n**Activities:**\n- Capture archival masters and ISOs\n- Cut social clips, on-demand chapters, sales enablement reels\n- Pull metrics: audience reaction, message pull-through, social/SOV, press coverage, pipeline influence, recruiting, share price (for investor-facing)\n- Run a structured debrief (what worked / what to change / what to kill)\n- Update template library with lessons\n\n**Deliverables:** Recap report, cutdown library, debrief notes, template updates.\n\n**Failure modes:** No debrief. Hero footage with no captions. Cutdowns delivered weeks late.\n\n**Exit criteria:** Stakeholders have what they need to use the keynote for the next 12 months.\n\n## Phase-by-phase escalation rules\n\n- **Phase 1–2:** Escalate when stakeholders cannot agree on the controlling idea. Do not draft until resolved.\n- **Phase 3:** Escalate scope creep — new demos, new videos, new speakers — to the executive sponsor with cost.\n- **Phase 4:** Escalate executive unavailability for rehearsal. No rehearsal = no lock.\n- **Phase 5–6:** Escalate any cue with no owner. Unowned cues fail.\n- **Phase 7:** Producer decides in the moment. Escalation is post-show.\n- **Phase 8:** Escalate KPI gaps to the sponsor with proposed instrumentation for next time.\n\nFile v0.1.0:references/measurement.md\n\n# Measurement — what success looks like\n\nLoad when planning KPIs, building a post-event report, or pushing back on a keynote that can't justify its existence.\n\n## Measurement principles\n\n1. **Instrument before you produce.** If you can't define success at Phase 1, you'll fabricate it in Phase 8.\n2. **Multiple audiences, multiple metrics.** A flagship keynote has 4–6 distinct audiences (customers, prospects, employees, press, analysts, investors). Each needs its own scorecard.\n3. **Distinguish leading and lagging.** Social buzz is leading; pipeline influence is lagging. Both matter, but don't confuse them.\n4. **Resist vanity metrics alone.** Views, impressions, and reach are necessary but never sufficient.\n5. **Compare to baseline.** A number without context is theater.\n\n## KPI catalog\n\n### Audience reaction\n- In-room sentiment (post-event survey, NPS)\n- Stream chat sentiment / reactions\n- Drop-off rate (where did stream viewers leave?)\n- Average watch time (live + on-demand)\n- Standing ovations / laughs / gasps (yes, these matter and can be tracked)\n\n### Message pull-through\n- Did press use your headline language?\n- Did analysts repeat your category framing?\n- Did social mentions cluster around the controlling idea?\n- Were the message house pillars echoed in customer / partner posts?\n- **This is the single most underused KPI.** A keynote that doesn't move language doesn't move belief.\n\n### Share of voice / press\n- Volume of coverage vs. prior keynote and vs. competitors\n- Tier-1 placement counts\n- Sentiment of coverage (positive / neutral / negative)\n- Headline accuracy — did press get the message right?\n\n### Social\n- Branded hashtag adoption\n- Influencer / employee amplification\n- Quote tweets / shares of specific moments\n- Top 5 clipped moments (what the internet remembered)\n\n### Business impact\n- Pipeline influenced (sales attribution to event)\n- Demos requested / trials started post-event\n- MQL / SQL lift in the week following\n- Deal acceleration on existing pipeline\n- For investor events: share price reaction in the 24h / 1wk window\n\n### Recruiting & brand\n- Career page traffic\n- Application volume in following weeks\n- Employer brand sentiment\n\n### Asset reuse (the multiplier)\n- Number of sales-enablement cutdowns delivered\n- On-demand views in the first 30 / 60 / 90 days\n- Customer-facing clip embeds\n- Internal all-hands / training reuse\n\n### Production-quality KPIs (the producer's scorecard)\n- Show ran on time (over/under by minutes)\n- Cues missed / called late\n- Demo success rate (live vs. backup)\n- Rehearsal hours per minute of stage time\n- Number of last-week script changes\n- Time from show end → cutdowns published\n\n## Post-event report structure\n\n**Executive summary (1 page)**\n- Show overview (audience, format, runtime)\n- Headline outcomes (3–5 bullets, with numbers)\n- Headline risks / learnings (3–5 bullets)\n\n**By the numbers**\n- Live attendance / stream peak / on-demand to-date\n- Sentiment + NPS\n- Press, social, analyst summary\n- Pipeline / business impact (caveat lead time)\n\n**Message pull-through analysis**\n- Did the controlling idea land? Evidence.\n- Pillar-by-pillar pull-through.\n- Unwanted narratives that emerged. Why.\n\n**Moment-by-moment**\n- Top 5 best-received moments (live + clipped)\n- Bottom 3 underperforming moments\n- Recommended cutdowns\n\n**Production debrief**\n- What worked\n- What to change\n- What to kill\n- Process improvements for next time\n\n**Next-step playbook**\n- Cutdown roadmap (clip list, owner, due date)\n- Sales enablement plan\n- On-demand and SEO plan\n- Follow-on content (blog, op-ed, podcast, webinar)\n\n## Cutdown roadmap (the post-event multiplier)\n\nFor every flagship keynote, plan at least these cuts:\n\n| Cut | Length | Audience | Use |\n|---|---|---|---|\n| Full keynote (on-demand) | Original | All | Owned platform, SEO |\n| Highlight reel | 3–5 min | Press, social | LinkedIn, X, YouTube |\n| Speaker spotlight | 1–2 min per exec | Recruiting, brand | LinkedIn, internal |\n| Customer story spotlight | 2–3 min | Sales | Pipeline acceleration |\n| Demo spotlight | 1–2 min | Product marketing | Website, demo requests |\n| Moment clips (10–30s) | <30s | Social | Vertical, captioned |\n| Quote cards (static) | N/A | Social, sales decks | Asynchronous distribution |\n| Sales kickoff cut | 5–10 min | Internal | SKO replay |\n\nPlan all cuts BEFORE the show — they affect camera capture, ISO needs, and music licensing.\n\n## Honest limits of measurement\n\n- Brand impact is real but slow.\n- Pipeline attribution to single events is messy; use a hold-out or pre/post comparison.\n- Press coverage is a function of news cycle as much as content quality.\n- Social numbers reward stunts more than substance — don't optimize for them alone.\n\nA keynote that changes what the audience believes will eventually move the business. Trust the leading indicators and instrument enough to prove it later.\n\nFile v0.1.0:references/narrative-frameworks.md\n\n# Narrative frameworks — when to use which\n\nLoad this when the user asks for story structure, arc design, or message architecture. Pick one frame per keynote — do not mix.\n\n## The frames\n\n### Duarte sparkline (default for tech keynotes)\nAlternate \"what is\" vs \"what could be.\" Builds tension and release. End on a \"new bliss\" — the future state the audience now believes is possible.\n\n**Use when:** product launch, category shift, vision keynote.\n**Avoid when:** straightforward operational update or earnings-style readout.\n\n### Problem / solution\nName the audience's pain in their words. Present the solution. Prove it. Close with what they should do.\n\n**Use when:** B2B keynote with clear ICP pain, sales-adjacent shows.\n**Avoid when:** the \"problem\" is contrived or insults the audience's intelligence.\n\n### Before / after / bridge\nShow today's reality, paint tomorrow's reality, then the bridge from one to the other (your product, your category, your call to action).\n\n**Use when:** transformation stories, internal all-hands, change management.\n**Avoid when:** the \"after\" is unprovable in the room.\n\n### What / so what / now what\nInformation → implication → action. Crisp, executive-friendly.\n\n**Use when:** investor updates, board briefings, analyst day segments.\n**Avoid when:** you need emotional movement; this frame is rational.\n\n### Hero's journey\nAudience is the hero, you are the guide. Call to adventure, refusal, mentor, threshold, ordeal, return with the elixir.\n\n**Use when:** developer keynotes, community shows, customer success stories.\n**Avoid when:** time is tight; the frame needs room to breathe.\n\n### Customer transformation\nOpen with a customer's \"before.\" Walk through their journey. End with their \"after.\" Your product is the supporting character.\n\n**Use when:** customer conferences, sales kickoffs, case-study segments.\n**Avoid when:** the customer hasn't given air-tight approval to the story.\n\n### Category shift\nName the old game. Declare the new game. Position the audience on the right side of the shift.\n\n**Use when:** category-creation moments, repositioning keynotes (e.g., \"the era of X is over\").\n**Avoid when:** you can't actually defend the category claim — analysts will eat you alive.\n\n### Demo-led proof\nThe demo IS the argument. Setup → reveal → implication. Minimal slide scaffolding.\n\n**Use when:** product launches where the product speaks for itself (Jobs/iPhone 2007, OpenAI demos).\n**Avoid when:** demo confidence is low or the product isn't yet visually obvious.\n\n## S.T.A.R. moments (Duarte)\n\n\"Something They'll Always Remember.\" Plan at least one per major keynote. Categories:\n\n- **The reveal** — Jobs pulling iPhone from his pocket; Apple pulling MacBook Air from a manila envelope.\n- **The repeatable phrase** — Nadella's \"tech intensity,\" Benioff's \"Customer 360.\"\n- **The visual** — Al Gore's hockey stick, Huang's giant GPU on stage.\n- **The stunt** — Gates releasing mosquitoes at TED, OpenAI live multimodal demos.\n- **The guest** — surprise customer, surprise celebrity, surprise founder return.\n- **The number** — one stunning statistic the audience repeats afterward.\n\nA S.T.A.R. moment is engineered, not accidental. If you don't have one by Phase 2, invent one or accept the keynote will be forgettable.\n\n## Slide / visual frameworks\n\n### Assertion-evidence\nEvery slide title is a claim (a complete sentence), not a topic label. Body is visual evidence for the claim.\n\n- Wrong: \"Q4 Performance\"\n- Right: \"Q4 revenue grew 38%, led by enterprise contracts over $1M\"\n\n### Presentation Zen (Garr Reynolds)\n- Slides support the speaker; they are not the speaker.\n- Use empty space. Avoid clutter.\n- Visual > textual. One idea per slide.\n\n### Storytelling with Data (Cole Nussbaumer Knaflic)\n- Don't show data — tell a story with it.\n- Eliminate clutter. Use color to focus, not decorate.\n- Always name the \"so what\" beside the chart.\n\n### 10/20/30 (Guy Kawasaki)\n10 slides, 20 minutes, 30-point font minimum. Heuristic for pitch decks; useful pressure-test for any executive talk.\n\n## Storytelling primitives worth borrowing\n\n### Pixar's 22 (operating prompts for keynote writers)\n- \"You admire a character for trying more than for their successes.\"\n- \"Once upon a time… every day… one day… because of that… because of that… until finally…\"\n- \"Why must you tell THIS story? What's the belief burning within you?\"\n- \"Discount the 1st thing that comes to mind, and the 2nd, 3rd, 4th, 5th — get the obvious out of the way.\"\n\n### Aristotle's three-act structure\nSetup → confrontation → resolution. The oldest reliable shape; works for any 30-60 minute keynote.\n\n### Tension and release\nAudiences need both. A keynote that is all peaks is exhausting; all valleys is boring. Plan the emotional contour explicitly: where are the laughs, the gasps, the proofs, the pauses.\n\n## How to pick\n\nAsk, in order:\n\n1. **What does the audience need to believe afterward?** → that names the destination.\n2. **What do they believe now?** → that names the starting tension.\n3. **Is there a customer story strong enough to carry the arc?** → if yes, customer transformation.\n4. **Is the product the proof?** → if yes, demo-led.\n5. **Is this a category bet?** → if yes, category shift or sparkline.\n6. **Is the audience rational (investors/analysts)?** → what/so what/now what.\n7. **Otherwise:** default to Duarte sparkline.\n\nFile v0.1.0:references/risks-and-saves.md\n\n# Risks & save-the-show plays\n\nLoad before tech rehearsal, on show day, or whenever an executive says \"what if X happens?\"\n\nThe job isn't to prevent every risk — it's to know which risks matter, prevent the preventable ones, and have a decisive play ready for the rest.\n\n## Risk register format\n\nFor each risk, document: trigger, likelihood, impact, prevention, owner, and the save-the-show play.\n\n## The catalog\n\n### Demo failure\n- **Trigger:** Network drop, latency spike, login issue, model nondeterminism, UI regression, dependency outage.\n- **Likelihood:** High. Always assume it.\n- **Impact:** Catastrophic for the moment; recoverable with a good play.\n- **Prevention:** Happy path lock 72h pre-show. Reset script. Caged network. Wired backup. Pre-recorded backup of the exact same demo. Failover operator on comms.\n- **Save:** Cut to backup recording. Speaker continues as if planned. Never apologize for \"technical difficulties\" — narrate over it. If recording also fails, narrate the outcome and move on.\n\n### Speaker freeze\n- **Trigger:** Memory blank, prompter scroll error, unfamiliar audience, nerves.\n- **Likelihood:** Medium for inexperienced speakers; low for veterans.\n- **Impact:** Audience awareness builds with every second of silence.\n- **Prevention:** Multiple rehearsals. Confidence monitor with current bullet. Paper script in podium. Pre-agreed silent cue from producer = \"skip to next beat.\"\n- **Save:** Show caller cues prompter back. If freeze persists 5+ seconds, jump to next slide / video / demo. Co-host or off-stage voice bridges. After event, never single out the speaker in debrief documents.\n\n### Slide misorder / wrong file\n- **Trigger:** Version control failure, last-minute swap, duplicate filenames.\n- **Likelihood:** Medium with weak version control.\n- **Impact:** Confidence-shaking but survivable.\n- **Prevention:** Single source of truth. Filename convention with date + version. Lock check at dress. Operator has the final master only.\n- **Save:** Speaker pauses, says \"let me come back to that.\" Show caller advances to next ready slide. Cue-to-cue resumes when corrected.\n\n### Technical outage (playback, monitor, comms)\n- **Trigger:** Hardware failure, signal drop, software crash, power.\n- **Likelihood:** Low with proper redundancy; high without.\n- **Impact:** Show-stopping if redundancy isn't designed in.\n- **Prevention:** Two of everything critical (playback, prompter, mic, comms). Spare machines hot. Rehearse under load. Printed scripts in wing. Comms map.\n- **Save:** Hot-swap to backup. Camera-only speech mode. Host vamps. B-roll delay package. Stage manager moves to plan B blocking.\n\n### Breaking news during show\n- **Trigger:** External event (market move, geopolitical event, tragedy, competitor announcement) lands during your keynote.\n- **Likelihood:** Rare but real.\n- **Impact:** Can make celebratory content feel tone-deaf.\n- **Prevention:** Modular opening that can be swapped. Comms + legal on standby. Producer monitors news.\n- **Save:** Producer + exec sponsor + comms huddle, decide whether to acknowledge, modify, or proceed. Shorter celebratory tone, updated CTA, prepared bridge language. Never ignore something the audience knows.\n\n### Executive ego conflict\n- **Trigger:** Two executives want the same moment, the same number, or veto each other.\n- **Likelihood:** High at multi-speaker keynotes.\n- **Impact:** Damages narrative coherence and team morale.\n- **Prevention:** Pre-wired speaker map. Sponsor adjudication early. Document agreed handoffs.\n- **Save:** Triangulate through Exec Comms / CMO sponsor. Never let the conflict reach the speaker on show day.\n\n### Late executive script changes\n- **Trigger:** Executive sees the final script the day before and rewrites their section.\n- **Likelihood:** Very high.\n- **Impact:** Cascades to slides, prompter, legal review, captioning, localization, demo setup.\n- **Prevention:** Multiple rehearsals (so they're not seeing it fresh on day-of). Lock discipline. A clear \"what late changes cost\" cheat sheet for the exec sponsor.\n- **Save:** Producer triages: accept (if low-risk and high-value), defer (if too late), or counter-propose (if intent is good but execution wrong). Document trade-offs to the sponsor.\n\n### Legal / PR landmine\n- **Trigger:** A claim, a competitive callout, an unapproved customer story, an unreleased feature mention, a forward-looking statement without safe-harbor language.\n- **Likelihood:** Medium without disciplined review.\n- **Impact:** Press cycles, regulatory exposure, customer trust damage.\n- **Prevention:** Hard legal/PR/IR gate at T-minus 3 weeks. No claims enter the script without source attribution. Customer permissions in writing.\n- **Save:** Pull the moment. Rewrite the bridge. If discovered post-show, coordinate corrected communication immediately.\n\n### Demo \"concept\" vs. \"real\" mismatch\n- **Trigger:** Marketing wants to show a feature that engineering hasn't built yet.\n- **Likelihood:** High at product launches.\n- **Impact:** Reputation damage if presented as live.\n- **Prevention:** Clear labeling: \"live demo\" vs. \"concept render\" vs. \"feature in development.\" Engineering signs off on demo claims.\n- **Save:** Reposition framing on the fly. \"Here's where we're headed\" beats \"here's what we have.\"\n\n### Music / IP rights failure\n- **Trigger:** Walk-on music, video soundtrack, or stock visual not properly licensed for live + stream + on-demand.\n- **Likelihood:** Medium without rights audit.\n- **Impact:** Stream takedown, lawsuit, brand damage.\n- **Prevention:** Music supervisor or legal review of every audio cue. Licensed library default.\n- **Save:** Swap to library cue. Acknowledge in post-event if needed.\n\n### Captioning / accessibility failure\n- **Trigger:** ASR mis-transcribes a key term, captioner falls behind, sign interpreter not in shot.\n- **Likelihood:** Medium.\n- **Impact:** Excludes audience segments; reputational risk.\n- **Prevention:** Glossary for ASR. Human + AI captioning together. Pre-event walkthrough with interpreter.\n- **Save:** Producer escalates to stream operator. Post-event, corrected captions on on-demand.\n\n## The show-day mindset\n\nWhen something breaks:\n\n1. **Notice it before the audience does.** Producer's first job in the booth is situational awareness.\n2. **Pick the play.** Don't deliberate. The play is in your risk register.\n3. **Call it on comms.** One voice, clear and short. \"Going to backup demo. Now.\"\n4. **Brief the speaker between beats.** \"We're going to backup, stay calm, you're great.\"\n5. **Never apologize on stage.** The audience forgives what they don't notice. Narrate over the seam.\n6. **Debrief after.** Document the trigger, the play, the outcome. Update the register.\n\n## What separates senior producers\n\n- They've been here before. The play is muscle memory.\n- They make the call quickly and own it.\n- They protect the speaker from blame.\n- They debrief without theater — what failed, what to change, what to keep.\n\nFile v0.1.0:references/speaker-development.md\n\n# Speaker development\n\nLoad when prepping an executive for delivery, formatting a teleprompter script, or designing a rehearsal cadence.\n\n## Write for the ear, not the eye\n\nThe single most common failure: scripts written like a press release. Symptoms include long sentences, subordinate clauses, formal vocabulary, and no contractions. The fix:\n\n- **Sentences ≤ 15–20 words.** Break long thoughts into beats.\n- **Contractions on.** \"We're,\" \"you're,\" \"it's.\" Executives without contractions sound robotic.\n- **One idea per sentence.** Compound sentences kill teleprompter pacing.\n- **Read aloud test.** If you can't say it in one breath, rewrite.\n- **No nested clauses.** Subordinate clauses derail the prompter.\n- **Concrete > abstract.** \"Our 10,000 enterprise customers\" beats \"our broad customer base.\"\n- **Numbers are landmarks.** \"$1.2 billion\" sticks; \"significant growth\" doesn't.\n- **Pronouns work.** \"You\" pulls the audience in; \"we\" includes them; \"they\" distances.\n\n## Teleprompter formatting conventions\n\n- **Font size:** Start at 48–60pt for typical on-camera setups with the speaker 5–8 feet from the prompter.\n- **Line length:** Short. ~6–8 words per line is comfortable.\n- **All caps:** Avoid — they slow reading and feel like shouting.\n- **Punctuation:** Use commas, em-dashes, and ellipses to drive cadence. Periods = full stops, hard breaths.\n- **Stage directions:** Brackets, italicized, separate line. `[PAUSE]`, `[BEAT]`, `[GESTURE TO SCREEN]`, `[VIDEO ROLLS]`.\n- **Cue callouts:** ALL CAPS in brackets on their own line. `[CUE: VIDEO 003 — \"Customer Story: Acme\"]`\n- **Pronunciation guides:** Inline phonetic for any name the speaker might trip on. `Saoirse (SUR-sha)`.\n- **Builds:** Mark slide builds in the margin so the speaker knows what's appearing as they speak.\n- **Speaker handoffs:** Bold, distinct formatting. Walk-on/walk-off music cues noted.\n\n## Rehearsal cadence\n\nMove from low fidelity to high fidelity. Each rehearsal has a purpose; do not collapse them.\n\n| Rehearsal | Purpose | Fidelity |\n|---|---|---|\n| Table read | Hear the script aloud, time it, find clunky language | Seated, no slides |\n| Standing read | Body in motion, blocking notes | Standing, paper script |\n| Click-through | Confirm script + slides + transitions | Speaker + deck, no AV |\n| Demo rehearsal | Confirm demo flow, reset, backup | Demo machine + operator |\n| Tech rehearsal | Confirm all cues, AV, playback, lighting | Full crew, partial speakers ok |\n| Cue-to-cue | Operators only — every cue called, no full performance | Crew, no audience |\n| Dress rehearsal | Full run as if live | Full crew, full speakers, full audience simulation |\n| Final polish | Speaker confidence, last cuts, last nerves | 1:1 with each executive |\n\n**Minimum acceptable:** Table read + click-through + tech rehearsal + dress. Anything less is malpractice for a flagship keynote.\n\n## Rehearsal note categories\n\nAlways capture in these buckets — never freeform:\n\n- **Story clarity** — was the beat understood?\n- **Cuts for time** — what to remove if we're long\n- **Pronunciation** — anything the speaker tripped on\n- **Slide timing** — builds in/out of sync\n- **Demo confidence** — would I bet the show on this demo as currently configured?\n- **Teleprompter friction** — line breaks, font size, scroll speed\n- **Body/blocking** — where the speaker stands, when they move, where they look\n- **Confidence-monitor needs** — what should appear on the floor monitor\n- **Approvals** — what is still unapproved by legal / PR / IR / brand\n\n## Confidence-monitor patterns\n\nThe confidence monitor (downstage, facing the speaker) shows:\n\n- The slide currently on the main screens (so the speaker knows what the audience sees)\n- A countdown timer for the segment\n- Sometimes: the next slide or the next bullet\n- Sometimes: a producer note (\"SLOW DOWN,\" \"WRAP,\" \"GO TO DEMO\")\n\nDecide upfront what the speaker sees. Changing it on show day rattles them.\n\n## Q&A and bridge prep\n\nFor any keynote with press, analyst, or investor exposure:\n\n- Draft 10 likely questions, ranked by sensitivity.\n- For each, build a 30-second bridge: acknowledge → reframe → key message.\n- Identify any topic the speaker should decline (\"I can't comment on that today\").\n- Pre-clear sensitive language with legal/IR.\n\n## Executive coaching prompts\n\nWhen the executive is good but not great, push on these:\n\n- **Pacing:** Where are you rushing? Where are you holding?\n- **Eye lines:** When do you look at camera vs. the room?\n- **Hands:** Comfortable, intentional gestures, or are they distracting?\n- **Vocal variety:** Are you using your full range, or stuck in one register?\n- **The pause:** Are you using silence as a tool, or filling it with \"um\"?\n- **Conviction:** Do you believe what you're saying? The audience can tell.\n\n## Things to never do\n\n- Surprise the executive with new content on show day.\n- Let a speaker rehearse without the actual deck.\n- Approve a script the speaker hasn't read aloud.\n- Skip the demo rehearsal because \"it always works.\"\n- Change confidence-monitor content the day of.\n- Let the executive write their own teleprompter cues.\n\nFile v0.1.0:references/stakeholders-and-raci.md\n\n# Stakeholders & RACI\n\nLoad when planning approvals, escalations, or cross-functional alignment for a keynote.\n\n## The core cast\n\n### Executives (the speakers)\n- **CEO / CMO / CPO / CTO / CFO** — the speakers themselves. They own POV and final delivery.\n- **Their chiefs of staff / EAs** — your scheduling lifeline. Befriend them.\n\n### Executive communications\n- Owns voice, message discipline, reputation risk, internal-external consistency.\n- Often the producer's closest partner for script.\n\n### Product marketing\n- Owns positioning, claims, competitive differentiation, launch readiness, demo content.\n- The most common source of message bloat. Manage with the message house.\n\n### Product management & engineering\n- Owns what is real, what is shipping, what is demo-able vs. concept-only.\n- The most common source of last-minute \"we can't say that yet.\"\n\n### Brand & design\n- Owns visual identity, look and feel, typography, motion language.\n- Partners on slide brief, video treatment, scenic.\n\n### PR & corporate communications\n- Owns media strategy, pre-briefs, press release sync, embargoes.\n- Will need final claims vocabulary and headline language.\n\n### Investor Relations (IR)\n- Mandatory review for any forward-looking statements at investor-adjacent events.\n- Reg FD, safe harbor language — non-negotiable.\n\n### Legal & compliance\n- Reviews claims, customer story permissions, competitive callouts, IP, music rights, trademark usage, regulatory language.\n\n### Analyst Relations (AR)\n- Pre-briefs analysts, manages analyst day overlap, surfaces analyst-sensitive talking points.\n\n### Customer marketing\n- Owns customer guest experience, story release approvals, customer brand usage.\n\n### Sales / field marketing\n- Cares about pipeline impact, sales-enablement cutdowns, post-event collateral.\n\n### Event ops & global events\n- Owns venue, attendee experience, registration, scenic, catering — everything around the keynote.\n\n### Technical production (in-house or agency)\n- Show caller, technical director, stage manager, AV crew, scenic, lighting, audio, video, broadcast.\n\n### Agency partners (if used)\n- Creative agency, production agency, video house, motion shop, demo development, scenic fabricators.\n\n## Sample RACI for a flagship keynote\n\nR = Responsible (does the work) · A = Accountable (one owner, signs off) · C = Consulted · I = Informed\n\n| Workstream | R | A | C | I |\n|---|---|---|---|---|\n| Strategy brief | Keynote producer | VP Events / Exec Comms | CMO, Product Marketing | Speakers, Brand |\n| Message house | Keynote producer | Exec Comms | Product Marketing, PR, IR | Speakers, Sales |\n| Story arc / script | Keynote producer | Exec Comms | Speakers, Brand, Product Marketing | Legal, PR |\n| Slide design | Presentation design lead | Keynote producer | Brand, Product Marketing | Speakers |\n| Video assets | Video producer | Keynote producer | Brand, Product Marketing, Legal | Speakers |\n| Demo content | Demo engineer | Product Manager | Keynote producer, Product Marketing | Engineering |\n| Customer stories | Customer marketing | Keynote producer | Legal, PR | Sales |\n| Run-of-show | Keynote producer | Show producer / Exec Producer | Technical director, Show caller | All crew |\n| Cue-to-cue | Show caller | Show producer | Technical director, Operators | Producer |\n| Speaker prep | Keynote producer | Exec Comms | Speakers, Chiefs of staff | PR |\n| Rehearsals | Keynote producer | Show producer | All speakers, Technical | Exec sponsor |\n| Legal review | Legal counsel | Legal counsel | Keynote producer, PR, IR | Exec sponsor |\n| Captioning / accessibility | Event ops | Keynote producer | Stream vendor | Brand |\n| Post-event cutdowns | Video producer | Keynote producer | Sales, Brand, Customer marketing | All |\n| KPI reporting | Keynote producer | Exec sponsor | Marketing ops, PR, Sales | All |\n\n## Approval gates (the lock points)\n\nPlot these on the calendar working backward from show day:\n\n1. **Strategy brief locked** — T-minus 12 weeks\n2. **Message house locked** — T-minus 10 weeks\n3. **Outline / beat sheet locked** — T-minus 8 weeks\n4. **V1 script draft** — T-minus 6 weeks\n5. **Slide V1 / video V1 / demo V1** — T-minus 5 weeks\n6. **Script V2 (rehearsal-ready)** — T-minus 4 weeks\n7. **Legal / PR / IR review** — T-minus 3 weeks\n8. **Final script lock** — T-minus 2 weeks\n9. **Asset lock** — T-minus 1 week\n10. **ROS lock** — T-minus 5 days\n11. **Dress rehearsal sign-off** — T-minus 1 day\n12. **Show**\n\nShorter timelines compress proportionally but the gates remain — skipping legal review to save time is how you end up in the news for the wrong reason.\n\n## Managing executive politics (the unspoken job)\n\n- **Triangulate, don't transcribe.** When two executives give conflicting feedback, don't just relay it — synthesize and propose.\n- **Make the audience the third voice in the room.** \"From the audience's perspective…\" is your most powerful phrase.\n- **Bring data, not preferences.** Reference past keynote performance, audience research, competitive positioning.\n- **Pre-wire decisions.** Walk into reviews with the decision already aligned with the senior-most stakeholder. Surprises lose.\n- **Document agreements.** A short recap email after every review prevents whiplash later.\n\n## Escalation map\n\n- **Story-level conflict** → Exec Comms or CMO.\n- **Product claim disputes** → Product Marketing lead, then CPO if unresolved.\n- **Legal / regulatory blockers** → Legal, hard stop.\n- **Executive availability for rehearsal** → Chief of staff, then CEO sponsor.\n- **Budget / scope creep** → Event sponsor + finance.\n- **Crew / vendor failures** → Show producer / Executive producer.\n- **Show-time emergencies** → Producer decides; debrief after.\n\nFile v0.1.0:references/technical-literacy.md\n\n# Technical literacy\n\nLoad when you need to brief technical teams credibly or evaluate technical feasibility of a creative ask. You don't need to operate the gear — you need to ask the right questions and know what's plausible.\n\n## LED walls & screens\n\n**Aspect ratios you'll see:**\n- 16:9 — standard broadcast and most laptops\n- 16:10 — older corporate projectors\n- 21:9 / \"ultrawide\" — common for modern stages\n- 32:9 / 48:9 — cinematic wide-stage LED setups\n- 5K+ canvases for multi-segment LED walls\n\n**Always ask:**\n- Final canvas resolution (px × px)?\n- Pixel pitch (e.g., 1.9mm, 2.6mm, 3.9mm)? Lower = sharper, closer audience.\n- Aspect ratio?\n- Safe area (typically 5–10% inset from edges)?\n- Color profile (Rec.709 most common; check for HDR or Rec.2020 on premium shows)?\n- Native frame rate (24 / 25 / 29.97 / 30 / 59.94 / 60)?\n- Are there bezels or pixel-pitch transitions across panels we need to design around?\n\n**Common mistakes:**\n- Designing 1080p assets for a 5K canvas → upscale artifacts.\n- Placing critical content in the bottom 10% (audience heads block sightlines).\n- Forgetting that camera capture for IMAG / stream may want a different aspect than the LED.\n\n## Playback systems\n\n| System | Use case | Producer note |\n|---|---|---|\n| **Disguise (d3)** | Flagship LED shows, complex pixel mapping, real-time content | Premium budget; needs lead time and a Disguise operator. |\n| **Pixera** | Multi-screen, multi-projector media servers | Common alternative to Disguise. |\n| **QLab** | Theater-style cue stacks (audio + video + lighting) | Affordable, reliable, beloved by stage managers. |\n| **ProPresenter** | Corporate events, church, lower-complexity keynotes | Easy to operate; weaker for complex video. |\n| **Mitti** | Mac-based video playback, simple cue list | Good for single-screen video segments. |\n| **PlaybackPro** | Broadcast-grade video playback | The standard for high-stakes single-channel video. |\n| **vMix / Wirecast / OBS** | Live streaming switcher / encoder | Producer should know which is in use. |\n\n**Always ask:**\n- Which system is operating each screen / output?\n- What format are deliverables (codec, container, bit depth)? Common: ProRes 422 HQ for masters, H.264 for proxies.\n- What's the file naming convention?\n- Who is the operator? Are they in tech rehearsal?\n- What's the redundancy? (Spare machine? Hot backup? B-roll?)\n\n## Teleprompter rigs\n\n**Common rigs:**\n- **Through-the-lens (TTL)** — beam-splitter glass in front of camera; speaker looks at lens.\n- **Presidential / podium prompter** — angled glass panels left/right of podium; speaker glances side to side.\n- **Floor / confidence monitor** — large LED monitor downstage; speaker reads at lower eye line.\n\n**Software:**\n- dataVideo, CueScript, Teleprompter Premium, PromptSmart, Mirror.\n\n**Always ask:**\n- Which rig and which software?\n- Who is the prompter operator? Are they in dress?\n- Font size and line length?\n- Scroll method — manual (operator pacing the speaker) or hands-free (PromptSmart voice-following)?\n- Are there backup paper scripts in the podium / on the wings?\n\n## Audio\n\n**Mic types:**\n- **Lavalier (lav)** — clip-on, hidden; the executive default.\n- **Headset / Madonna** — visible, more reliable, common for active stage work.\n- **Handheld** — for guests, Q&A, ad-hoc.\n\n**Always ask:**\n- Mic type per speaker? Double-mic redundancy?\n- Who is mixing front-of-house vs. broadcast?\n- Are music cues at the right level vs. speech?\n- Is there a click track for any synced moments (timed-to-music demos, video stings)?\n\n## Comms\n\n- **Clear-Com** (or RTS, or Riedel) is the standard intercom.\n- Channels are assigned by role: producer, show caller, lighting, video, audio, stage manager, camera, demo.\n- Discipline matters. Off-topic chatter on production channel during a live show is a fireable offense.\n\n## Stream & broadcast\n\n**Always ask:**\n- Are we streaming? Where (YouTube, X, owned platform, broadcast partner)?\n- What's the encoding chain (vMix → Resi → CDN)?\n- Are stream graphics / lower thirds distinct from in-room graphics?\n- Is there a stream-only host / cutaway content for delays?\n- Captioning method (live ASR, live human captioner, both)?\n- Sign language interpreter (in-room, in-stream, picture-in-picture)?\n\n## Captioning, translation, accessibility\n\n- **Live captioning:** Human captioners (slower, accurate) vs. ASR (faster, error-prone). For high-stakes keynotes, do both.\n- **Translation:** Live interpreter booth feeding alternate audio channels; or AI translation (still error-prone for jargon-heavy tech).\n- **Audio description** for blind/low-vision attendees on a separate channel.\n- **Color contrast** on slides — 4.5:1 minimum for body text per WCAG AA.\n- **Avoid relying on color alone** for chart distinction.\n\n## Redundancy patterns (your job to enforce)\n\n- Two playback machines per critical output, hot-swappable.\n- Two prompter operators or one + paper backup.\n- Two mics per speaker (or a hand-off plan).\n- Pre-rendered backup video for every live demo.\n- Printed run-of-show in the producer pouch.\n- Printed scripts in the podium and stage-left wing.\n- Communications failover (radios as Clear-Com backup).\n\n## Tooling shorthand by phase\n\n- **Writing / collab:** Google Docs, Notion, Confluence, Frame.io, Air.\n- **Slides:** Keynote (Mac-native, smoother animations) > PowerPoint (universal). Figma for storyboarding.\n- **Motion / visuals:** After Effects, Cinema 4D, Unreal Engine (real-time scenic), Disguise Designer.\n- **ROS / cueing:** Shoflo (default modern ROS), Eventric Master Cue, Stage Timer, Rundown Studio.\n- **PM:** Asana, Monday, Smartsheet, Airtable.\n- **AI assists (use with care):** script drafting (Claude/GPT/Gemini), image gen (Midjourney/Sora/Veo), captioning (Whisper / Otter), real-time translation (KUDO / Interprefy).\n\nFile v0.1.0:references/trends-2024-2026.md\n\n# Trends — 2024 to 2026\n\nLoad when modernizing a keynote approach, advising on production choices, or pressure-testing whether a planned show feels current.\n\n## AI in keynote production\n\n**Where it's already standard:**\n- **Script drafting & iteration** — fast V0/V1, hate-it-or-love-it drafts, rewording for the ear. The producer's hand still owns final voice.\n- **Captioning & translation** — ASR (Whisper, Otter, AWS Transcribe) for live + on-demand; AI translation for non-broadcast tier languages.\n- **Image generation** — concept boards, mood frames, B-roll placeholder. Less common as final asset due to brand and IP risk.\n- **Voice cloning / synthetic narration** — common for promo and pre-roll, rare for live executive moments.\n- **Real-time personalization** — segment-specific stream variants, dynamic captions, attendee-personalized cutdowns.\n- **Mood boards, scenic concepts, RFP-stage creative** — AI image and video tools dominate ideation.\n\n**Where it's risky:**\n- Synthetic media of executives without ironclad consent and labeling.\n- AI-generated factual claims unverified by humans.\n- Voice clones used to \"fix\" live audio (deeply ethically questionable).\n- AI-generated customer testimonials (do not do this).\n\n**Producer guardrails:**\n- Label AI-generated visuals on-stage if the audience would assume real footage.\n- Get written consent for any synthetic likeness or voice.\n- Human-in-the-loop on every claim, name, statistic, customer reference.\n- Document AI tool usage for legal review.\n\n## Hybrid is not optional anymore\n\nEvery flagship keynote now has at least four delivery surfaces:\n\n1. The in-room audience\n2. The live stream\n3. The on-demand replay\n4. The social cutdown ecosystem\n\nDesign for all four from the start. Camera capture, ISO recording, caption plan, chapter markers, vertical-aspect cuts — these are Phase 1 decisions, not Phase 8 cleanup.\n\n## Shorter, denser keynotes\n\nAudience tolerance for a 2-hour keynote has collapsed. Even Apple events feel tight at 90 minutes. Pragmatic upper bounds:\n\n- Product launch keynote: 45–75 minutes\n- Customer conference flagship: 60–90 minutes\n- Investor day keynote segment: 20–30 minutes\n- Earnings-adjacent CEO remarks: 8–12 minutes\n- Sales kickoff opener: 20–30 minutes\n\nPlan the **density curve** explicitly: where can the audience exhale? A keynote that is 60 minutes of peaks is more tiring than 90 minutes of variety.\n\n## Sustainability as production constraint\n\n- LED reuse > one-off scenic builds.\n- Modular stage components that travel across multi-city tours.\n- Local crew, local vendors, local fabrication.\n- Carbon reporting requested by enterprise clients in RFPs.\n- Digital swag / no swag for many corporate events.\n- Reduced print, reduced freight.\n\nFor the producer: this affects scenic choices, travel for guest speakers, and whether you're shipping a custom build or designing for venue-native gear.\n\n## In-house vs. agency rebalancing\n\n- Many enterprises have built in-house keynote teams (Salesforce, Microsoft, AWS, ServiceNow, F5).\n- Agencies are taking on more \"experience system\" scope — keynote + expo + sponsor activations + post-event content — rather than just keynote production.\n- Hybrid models common: in-house keynote producer leads strategy + script, agency leads execution + scenic + technical.\n\n## Demo expectations\n\n- Audiences are demo-literate. They can tell scripted from live, real from staged.\n- Multi-modal AI demos (voice, vision, action) are the new bar for tech keynotes.\n- Failure on stage is forgiven if framed as honesty (\"we're working on this\"); cover-ups are punished.\n\n## Investor / analyst keynotes\n\n- Reg FD compliance increasingly producer-visible.\n- Safe-harbor statements at the top of any forward-looking section.\n- More webcast-first formatting (lower thirds, named speakers, chapter markers from go).\n- Investor questions are now routinely AI-translated to global audiences.\n\n## Synthetic media & deepfake risk\n\n- Audiences are wary of AI-generated executives.\n- Brand guidelines increasingly mandate disclosure of synthetic content.\n- Watermarking and provenance metadata (C2PA) emerging as standard.\n\n## What \"modern\" looks like in 2026\n\nA keynote that:\n- Runs ~60 minutes, not 120.\n- Opens with a customer story or a real-world stake, not a corporate sizzle.\n- Uses LED canvases for atmosphere, not feature lists.\n- Includes one engineered S.T.A.R. moment.\n- Demos something real, with a real backup.\n- Captions in 3+ languages by default.\n- Publishes the on-demand cut within 24 hours.\n- Releases at least 10 social cutdowns within 72 hours.\n- Reports message pull-through alongside reach.\n\n## What feels dated in 2026\n\n- 90+ minute pace with no audience exhale.\n- Bullet-list slides with topic headers.\n- \"Vision videos\" with no narrative tie to the show.\n- Demos with no labeled backup.\n- Single-language captions on global streams.\n- Cutdowns delivered weeks later.\n- Stage rebuilt city-by-city without sustainability rationale.","readmeExcerpt":"Skill: keynote-content-producer Owner: brianbmorgan Summary: 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","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"keynote-content-producer/\n├── SKILL.md                        # Skill definition loaded by Claude\n├── assets/                         # Fillable templates — produced as deliverables\n│   ├── accessibility-checklist.md\n│   ├── beat-sheet.md\n│   ├── demo-happy-path.md\n│   ├── executive-intake.md\n│   ├── message-house.md\n│   ├── post-event-report.md\n│   ├── rehearsal-notes.md\n│   ├── risk-register.md\n│   ├── run-of-show.md\n│   ├── script-format.md\n│   ├── slide-design-brief.md\n│   ├── story-arc-sparkline.md\n│   ├── strategy-brief.md\n│   └── video-treatment.md\n└── references/                     # Deep-dive reference material\n    ├── anatomy-of-great-keynotes.md\n    ├── lifecycle.md\n    ├── measurement.md\n    ├── narrative-frameworks.md\n    ├── risks-and-saves.md\n    ├── speaker-development.md\n    ├── stakeholders-and-raci.md\n    ├── technical-literacy.md\n    └── trends-2024-2026.md"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: keynote-content-producer\ndescription: \"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.\"\nlicense: MIT\nmetadata:\n  author: brian-morgan\n  version: '1.0'\n---\n\n# Keynote Content Producer\n\nYou 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).\n\nYou 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.\n\n## When to use this skill\n\nLoad and act under this skill when the user asks you to:\n\n- Develop or critique a keynote, main-stage talk, or executive presentation\n- Draft a script, teleprompter copy, or talk track for a C-suite speaker\n- Build a message house, story arc, sparkline, or beat sheet\n- Brief slides, videos, motion graphics, or live demos for a show\n- Produce a run-of-show (ROS), cue-to-cue, or show flow document\n- Prepare an executive for rehearsals (table read → tech → dress)\n- Plan demo failure-proofing, contingency, or \"save the show\" scenarios\n- Review a draft keynote for narrative drift, message bloat, or production risk\n- Plan post-event content reuse (cutdowns, social clips, on-demand)\n\nIf the request is a generic \"write a presentation\" with no executive, live-event, or main-stage context, this skill is overkill — answer normally.\n\n## Operating principles (read every time)\n\n1. **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.\n2. **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.\n3. **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"},{"path":"README.md","content":"# Keynote Content Producer\n\nA 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.\n\n## What this skill does\n\nThe **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.\n\nIt is not a slide-design tool or a logistics-only event planner. It protects the narrative while keeping every visible and audible element executable.\n\n## When to use it\n\nLoad this skill when you are working on:\n\n- Executive keynotes, main-stage talks, or all-hands presentations\n- Scripts, teleprompter copy, or talk tracks for C-suite speakers\n- Message houses, story arcs, sparklines, or beat sheets\n- Slide, video, motion-graphic, or live-demo briefs\n- Run-of-show (ROS), cue-to-cue, or show flow documents\n- Executive rehearsal preparation (table read → tech → dress)\n- Demo failure-proofing and contingency planning\n- Narrative reviews of draft keynotes\n- Post-event content reuse (cutdowns, social clips, on-demand)\n\n**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.\n\nIf the request is a generic \"write a presentation\" with no executive, live-event, or main-stage context, this skill is overkill.\n\n## Installation\n\nThis skill is distributed as a zip archive. To install it:\n\n1. Download or clone this repository.\n2. Extract `SKILL.zip`.\n3. Copy the `keynote-content-producer/` folder into the `.github/agents/` directory of the repository where you want the skill available.\n\nThe extracted folder contains:\n\n```\nkeynote-content-producer/\n├── SKILL.md                        # Skill definition loaded by Claude\n├── assets/                         # Fillable templates — produced as deliverables\n│   ├── accessibility-checklist.md\n│   ├── beat-sheet.md\n│   ├── demo-happy-path.md\n│   ├── executive-intake.md\n│   ├── message-house.md\n│   ├── post-event-report.md\n│   ├── rehearsal-notes.md\n│   ├── risk-register.md\n│   ├── run-of-show.md\n│   ├── script-format.md\n│   ├── slide-design-brief.md\n│   ├── story-arc-sparkline.md\n│   ├── strategy-brief.md\n│   └── video-treatment.md\n└── references/                     # Deep-dive reference material\n    ├── anatomy-of-great-keynotes.md\n    ├── lifecycle.md\n    ├── measurement.md\n    ├── narrative-frameworks.md\n    ├── risks-and-saves.md\n    ├── speaker-development.md\n    ├── stakeholders-and-raci.md\n    ├── technical-literacy.md\n    └── trends-20"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7fsz90gv8q15hcs7wajjthsd80dd15\",\n  \"slug\": \"keynote-content-producer\",\n  \"version\": \"0.1.0\",\n  \"publishedAt\": 1785090656096\n}"},{"path":"references/anatomy-of-great-keynotes.md","content":"# Anatomy of great keynotes\n\nLoad when you want to reference exemplars, teach by example, or pressure-test a draft against the best.\n\n## Steve Jobs — iPhone, January 2007\n\n**What worked:**\n- One controlling idea (\"three revolutionary products… and they're one device\").\n- The reveal as the central S.T.A.R. moment.\n- Demo-led proof — the product carried the argument.\n- Pacing: long setup, slow tension, explosive release.\n- Repetition of the \"iPod, phone, internet communicator\" trio until the audience said it with him.\n\n**Producer's contribution:**\n- Months of rehearsal to make the demo look effortless (the famous \"golden path\" through unstable software).\n- Single-screen slides with one assertion at a time.\n- Walk-on music, lighting, and rhythm engineered for the reveal.\n\n**Lesson:** Discipline. One idea, one demo, one room.\n\n## Tim Cook — Apple events (ongoing)\n\n**What works:**\n- Multi-presenter handoffs choreographed precisely.\n- Pre-recorded video segments that allow seamless location/timing flexibility.\n- Tight runtime (60–75 min).\n- Product-first visuals — the device is the hero.\n\n**Producer's contribution:**\n- Pre-record discipline. Cook era treats keynotes as broadcast products, not stage shows.\n- Single source of truth for assets across multiple presenters.\n\n**Lesson:** Hybrid recorded + live is a legitimate format. Plan for it.\n\n## Satya Nadella — Microsoft Build / Ignite\n\n**What works:**\n- Plain-language framing of complex platform shifts.\n- \"Tech intensity\" and similar repeatable phrases.\n- Customer stories interlaced with product demos.\n- A genuinely warm executive tone — Microsoft's biggest unlock.\n\n**Producer's contribution:**\n- Long-form messaging architecture aligned with Microsoft's category narrative.\n- Customer story curation (often year-long sourcing).\n\n**Lesson:** Tone matters. Warmth from a CEO is engineered, not accidental.\n\n## Jensen Huang — Nvidia GTC\n\n**What works:**\n- High-information density that respects technical audiences.\n- The \"stack\" framing — full vertical from chips to platforms.\n- Long runtime (90–120 min) that works because the audience is paying.\n- Showmanship — leather jacket, props, oversized chip reveals.\n\n**Producer's contribution:**\n- Permission to be technical because the audience earned it.\n- Engineered visual landmarks (the giant GPU on stage).\n\n**Lesson:** Audience determines acceptable density. GTC is not a marketing event.\n\n## Marc Benioff — Dreamforce\n\n**What works:**\n- Star power — celebrity speakers, surprise guests, philanthropic causes.\n- \"Customer 360\" and similar repeatable category claims.\n- Spectacle scale — tens of thousands in the room.\n\n**Producer's contribution:**\n- Talent booking pipeline (often year-round work).\n- Massive run-of-show across multiple stages and days.\n\n**Lesson:** Spectacle works when it ladders to message. Star power without message is empty calories.\n\n## Andy Jassy → Matt Garman — AWS re:Invent\n\n**What works:**\n- Service-by-service announcement cadence is tedious but t"},{"path":"references/lifecycle.md","content":"# Lifecycle — the 8 phases in depth\n\nLoad this when you need to know what to do in a specific phase, what to deliver, and what to escalate.\n\n## Phase 1: Strategy & discovery\n\n**Goal:** Define the job the keynote must do before anyone writes a word.\n\n**Activities:**\n- Executive intake interviews (use `assets/executive-intake.md`)\n- Audience persona review — who is in the room, on the stream, on social\n- Business-objective extraction: what changes if this keynote succeeds?\n- Competitive / category narrative scan — what is everyone else saying?\n- Previous-keynote teardown — what worked, what didn't, what aged badly\n- Stakeholder map — who has approval rights, who has veto, who has feelings\n- First-pass message hierarchy: must-say / should-prove / parking-lot\n\n**Deliverables:** Strategy brief, message house v0, stakeholder map.\n\n**Failure modes:** Skipping intake. Letting product marketing drive the message house alone. Treating the audience as monolithic.\n\n**Exit criteria:** One controlling idea, 3–5 pillars, named audience belief shift, success metric.\n\n## Phase 2: Narrative & script\n\n**Goal:** Convert the message house into a sequence of audience transformations.\n\n**Activities:**\n- Pick a story frame (sparkline, problem/solution, before-after-bridge, what/so what/now what, hero's journey, category shift, customer transformation)\n- Beat sheet — every beat has a purpose, an owner, an asset, a timing estimate\n- Speaker handoff map — what each speaker inherits, owns, hands off\n- Demo insertion plan — where demos land, what they prove\n- Identify S.T.A.R. moment(s)\n- Draft V1 script in teleprompter format with stage directions and cue callouts\n\n**Deliverables:** Locked outline, V1 script, demo insertion plan.\n\n**Failure modes:** Writing the script before the arc. Letting each speaker write their own section without integration. No tension in the arc.\n\n**Exit criteria:** End-to-end timed read with all transitions written.\n\n## Phase 3: Asset production\n\n**Goal:** Translate the script into every visible and audible asset.\n\n**Activities:**\n- Slide briefs with assertion headlines and acceptance criteria\n- Video treatments with shot lists, music direction, caption plan\n- Motion/LED canvas briefs with technical specs\n- Demo briefs with happy path and failure-proofing\n- Music cues, walk-on stings, lower thirds\n- Version control discipline (filename convention, single source of truth)\n\n**Deliverables:** Brief packets, asset tracker, version log.\n\n**Failure modes:** Skipping briefs and \"letting design figure it out.\" Approving copy-heavy slides. Treating demos as casual.\n\n**Exit criteria:** Every cue in the ROS has a named asset, an owner, and a delivery date.\n\n## Phase 4: Speaker development\n\n**Goal:** Turn the script into credible human delivery.\n\n**Activities:**\n- Format script for teleprompter (see `speaker-development.md`)\n- Rehearsal cadence: table read → standing read → click-through → demo rehearsal → tech rehearsal → cue-to-cue → dress rehearsal → final "}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":2162,"uniquenessScore":43,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T10:42:00.497Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T10:42:00.497Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T05:10:56.684Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}