hyperframes-sales-demo-builder
Build a personalized product-demo or sales-walkthrough video in HyperFrames for a specific prospect or account — narrated screen-by-screen, branded to them, ending in a clear next step. Turns a generic demo into a "this was made for me" asset for outbound, follow-up, or deal acceleration. Use when you want to send a tailored video instead of booking another live call.
What this skill does
# HyperFrames Sales Demo Builder
The best-converting sales video isn't a generic product tour — it's a two-minute walkthrough that names the prospect's company, shows the exact workflow they care about, and ends with one obvious next step. This skill builds that, repeatably, in HyperFrames.
Use it for: warm follow-up after a discovery call, breaking into a target account, re-engaging a stalled deal, or replacing a live demo with something the buyer can forward internally to the people who weren't on the call.
For composition/caption/TTS/render mechanics, invoke the `hyperframes`, `hyperframes-cli`, and `hyperframes-media` skills. This skill owns the personalization and the sales narrative.
## Step 1 — Gather the account context
- **Who** — the prospect/account, the persona of the viewer (champion vs. economic buyer — load from `icp-deep-scanner` personas if available). The same product gets a different demo for each.
- **Their problem** — the specific pain from discovery notes / CRM (read-only) / their public site. Personalize to *their* job, not a feature list.
- **The workflow to show** — the 2–3 moments that prove value for them, not the full product.
- **Proof** — the metric, customer, or before/after most relevant to their situation.
- **Next step** — book a call, start a trial, loop in a stakeholder.
**Security:** read CRM/notes read-only; never write to the CRM or send anything automatically. Don't put another customer's confidential data into this prospect's video. Secrets via env vars.
## Step 2 — Script the walkthrough
Structure that converts:
1. **Personalized open** — name them and their problem in the first 10 seconds ("{Name}, you mentioned {pain} — here's exactly how we'd handle that").
2. **The relevant workflow** — show the 2–3 moments that matter to *them*, narrated as their use case.
3. **Proof** — the most relevant result, briefly.
4. **One clear CTA** — a single next step, with urgency that's real, not manufactured.
Keep it under ~2–3 minutes. A demo they finish beats a thorough one they abandon.
## Step 3 — Build & brand the composition
- Author scene blocks per script beat (`hyperframes`).
- **Brand to the prospect where tasteful** — their logo on the open/close, their use-case language on screen. Reuse a `claude-design-system-architect` kit for your own brand consistency. No purple, no emoji unless branded.
- **Screen content** — use real product screens/recordings or clean mockups; annotate with motion to direct the eye to the value moment.
- **Captions** synced to VO (forwarded internally and watched muted).
- **Voiceover** — warm, conversational, first-name; generate via the HyperFrames media pipeline (or `edge-tts` neural voice). Consider a recorded human VO for high-value accounts.
- Lint + preview before delivery; render the final.
## Step 4 — Deliver
```markdown
# Sales demo: {Account} — {viewer persona}
- Personalized cold-open line
- Walkthrough script (beats)
- Composition path + render command
- Suggested send copy (email/LinkedIn) to accompany the video
- The single CTA
```
Offer to write the accompanying send copy via `cold-email-sequence-generator`, test the open line in `prospect-panel-simulator`, and produce a short 30s teaser cut via `hyperframes-ad-director`.
## Guardrails recap
Personalize to their problem, not your feature list · show only the 2–3 value moments · one CTA · never expose another customer's confidential data · read-only CRM, no auto-send · captions + brand always · lint/preview/render before claiming done.
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.