Brag Video
Use this skill to turn a product, feature, or release into a short video concept that is useful for launch, social proof, product marketing, or internal demos.
This is a planning and production-guidance skill. It does not assume a specific video generator, editor, SaaS, MCP server, or CLI. Use whatever the user has installed and approved.
Safety And Scope
- Do not copy raw
latent-spaces/brag files or prompts. The idea is credited, but this skill is Overdrive-authored.
- Do not auto-install Hyperframes, Remotion, ffmpeg, browser automation, image/video generators, or editing tools.
- Do not upload private code, customer data, credentials, unreleased product details, analytics dashboards, or user content to third-party tools without explicit approval.
- Do not make unsupported product claims. If a metric, testimonial, or customer logo is not verified and approved, omit it or mark it as placeholder copy.
- For client or competitor material, avoid impersonation and trademark misuse.
When To Use
Use brag-video when the user asks for:
- a launch video
- a product demo clip
- a feature teaser
- a before/after transformation video
- a social clip for X, LinkedIn, TikTok, YouTube Shorts, or Product Hunt
- a founder/product update video
- a short investor/customer demo sequence
Pair with:
launch for launch strategy and channelsclaude-video when the user needs to analyze source footage firstmedia-download only for authorized media retrievalcopywriting or humanizer for captions and narration polishdesign-taste-frontend, impeccable, or high-end-visual-design when the captured UI needs visual cleanup first
Output Contract
For most requests, produce:
- Angle: one sentence naming the core payoff.
- Audience: who the clip is for and what they should feel/understand.
- Format: aspect ratio, duration, platform, and whether it is screen capture, motion graphics, talking head, or hybrid.
- Storyboard: 5-9 beats with timestamps.
- Capture List: exact screens, interactions, assets, or shots needed.
- Script/Copy: voiceover, captions, overlays, and CTA.
- Production Notes: tool options, animation/motion notes, music/SFX guidance, and fallback path.
- Verification: claims/assets that need approval before publishing.
Practical Defaults
- Default length: 20-45 seconds.
- Default aspect: 16:9 for product demos, 9:16 for social vertical, 1:1 only when the platform requires it.
- Default pacing: hook in first 2 seconds, one clear product moment by second 8, CTA at the end.
- Prefer real UI/product footage over abstract stock visuals.
- Show the product doing the work, not a long explanation of the product.
- If the product is not visually ready, recommend improving the UI first rather than hiding it with effects.
Brag Video Pattern
Use this structure unless the user gives a stronger one:
- Problem flash: show the painful old way or outcome.
- Switch moment: introduce the product/feature in one clean sentence.
- Proof by motion: show the actual flow working.
- Payoff: show the result, saved time, better output, or before/after.
- Credibility: optional verified metric, customer, workflow detail, or technical proof.
- CTA: try it, read the release, join waitlist, book demo, or install.
Production Paths
Choose the lightest path that can hit the quality bar:
- Storyboard only: when the user needs planning before capture.
- Screen-capture plan: when the UI exists and can be recorded.
- Motion spec: when a designer/video tool will execute it.
- Remotion/web video: when the repo already uses video-as-code or the user asks for programmable video.
- Image/video generator prompt pack: when generated visuals are explicitly wanted and legally safe.
Always ask before running long render jobs, paid APIs, uploads, or third-party generators.
Checklist Before Final
- Does the first 2 seconds communicate why to care?
- Is the product actually visible?
- Are claims verified?
- Is the CTA specific?
- Are captions readable on mobile?
- Does the clip work muted?
- Are logos, customer names, screenshots, and music rights cleared?
1---2name: brag-video3description: Plan and produce concise product brag/demo videos, launch clips, or social cutdowns from an app, feature, workflow, or release. Use when the user wants a shareable product video, feature teaser, before/after demo, founder update, or launch asset. Inspired by latent-spaces/brag, but rewritten for Overdrive with no raw upstream redistribution.4---56# Brag Video78Use this skill to turn a product, feature, or release into a short video concept that is useful for launch, social proof, product marketing, or internal demos.910This is a planning and production-guidance skill. It does not assume a specific video generator, editor, SaaS, MCP server, or CLI. Use whatever the user has installed and approved.1112## Safety And Scope1314- Do not copy raw `latent-spaces/brag` files or prompts. The idea is credited, but this skill is Overdrive-authored.15- Do not auto-install Hyperframes, Remotion, ffmpeg, browser automation, image/video generators, or editing tools.16- Do not upload private code, customer data, credentials, unreleased product details, analytics dashboards, or user content to third-party tools without explicit approval.17- Do not make unsupported product claims. If a metric, testimonial, or customer logo is not verified and approved, omit it or mark it as placeholder copy.18- For client or competitor material, avoid impersonation and trademark misuse.1920## When To Use2122Use `brag-video` when the user asks for:2324- a launch video25- a product demo clip26- a feature teaser27- a before/after transformation video28- a social clip for X, LinkedIn, TikTok, YouTube Shorts, or Product Hunt29- a founder/product update video30- a short investor/customer demo sequence3132Pair with:3334- `launch` for launch strategy and channels35- `claude-video` when the user needs to analyze source footage first36- `media-download` only for authorized media retrieval37- `copywriting` or `humanizer` for captions and narration polish38- `design-taste-frontend`, `impeccable`, or `high-end-visual-design` when the captured UI needs visual cleanup first3940## Output Contract4142For most requests, produce:43441. **Angle**: one sentence naming the core payoff.452. **Audience**: who the clip is for and what they should feel/understand.463. **Format**: aspect ratio, duration, platform, and whether it is screen capture, motion graphics, talking head, or hybrid.474. **Storyboard**: 5-9 beats with timestamps.485. **Capture List**: exact screens, interactions, assets, or shots needed.496. **Script/Copy**: voiceover, captions, overlays, and CTA.507. **Production Notes**: tool options, animation/motion notes, music/SFX guidance, and fallback path.518. **Verification**: claims/assets that need approval before publishing.5253## Practical Defaults5455- Default length: 20-45 seconds.56- Default aspect: 16:9 for product demos, 9:16 for social vertical, 1:1 only when the platform requires it.57- Default pacing: hook in first 2 seconds, one clear product moment by second 8, CTA at the end.58- Prefer real UI/product footage over abstract stock visuals.59- Show the product doing the work, not a long explanation of the product.60- If the product is not visually ready, recommend improving the UI first rather than hiding it with effects.6162## Brag Video Pattern6364Use this structure unless the user gives a stronger one:65661. **Problem flash**: show the painful old way or outcome.672. **Switch moment**: introduce the product/feature in one clean sentence.683. **Proof by motion**: show the actual flow working.694. **Payoff**: show the result, saved time, better output, or before/after.705. **Credibility**: optional verified metric, customer, workflow detail, or technical proof.716. **CTA**: try it, read the release, join waitlist, book demo, or install.7273## Production Paths7475Choose the lightest path that can hit the quality bar:7677- **Storyboard only**: when the user needs planning before capture.78- **Screen-capture plan**: when the UI exists and can be recorded.79- **Motion spec**: when a designer/video tool will execute it.80- **Remotion/web video**: when the repo already uses video-as-code or the user asks for programmable video.81- **Image/video generator prompt pack**: when generated visuals are explicitly wanted and legally safe.8283Always ask before running long render jobs, paid APIs, uploads, or third-party generators.8485## Checklist Before Final8687- Does the first 2 seconds communicate why to care?88- Is the product actually visible?89- Are claims verified?90- Is the CTA specific?91- Are captions readable on mobile?92- Does the clip work muted?93- Are logos, customer names, screenshots, and music rights cleared?
radustefandumitru