Capture a website and create a HyperFrames video from it. Use when: (1) a user provides a URL and wants a video, (2) someone says "capture this site", "turn this into a video", "make a promo from my site", (3) the user wants a social ad, product tour, or any video based on an existing website, (4) the user shares a link and asks for any kind of video content. Even if the user just pastes a URL โ this is the skill to use.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Capture a website and create a HyperFrames video from it. Use when: (1) a user provides a URL and wants a video, (2) someone says "capture this site", "turn this into a video", "make a promo from my site", (3) the user wants a social ad, product tour, or any video based on an existing website, (4) the user shares a link and asks for any kind of video content. Even if the user just pastes a URL โ this is the skill to use.
Website to HyperFrames
Capture a website, then produce a professional video from it.
Users say things like:
"Capture https://... and make me a 25-second product launch video"
"Turn this website into a 15-second social ad for Instagram"
"Create a 30-second product tour from https://..."
The workflow has 7 steps. Each produces an artifact that gates the next. By default it's collaborative โ gates marked ๐ฌ stop and ask the user. If the user signals autonomous mode ("decide for me", "surprise me"), ๐ฌ user-preference gates are skipped; see step-2-brief.md for how that propagates.
Autonomous mode is NOT "skip all gates." Auto mode covers user-preference questions (TTS provider, voice, color emphasis, beat count, music yes/no, captions yes/no โ where the agent decides on the user's behalf). It does NOT cover quality-verification gates. The following remain non-skippable in auto mode:
Asset Audit (Step 3) โ viewing contact sheets and justifying USE/SKIP for each asset
Per-beat HTML read (Step 5) โ structured evidence block per beat
DoD checklist (Step 6) โ including animation-map, per-warning WCAG verification, audio/motion playback
Honest disclosure section (Step 6) โ "What I did NOT verify" must appear in your final summary
If you find yourself reasoning "auto mode says bias toward action, so I'll skip X" โ and X is a verification gate, not a preference question โ that reasoning is wrong. Bias toward action applies to deciding what to build, not to deciding whether to verify.
Capture the site, then read the extracted data to understand the brand and product โ what it does, who it's for, what voice it speaks in, what mood it lives in. The captured assets are a brand toolkit for later, not the building blocks the video is made from.
Gate: Site summary printed โ strategy-first (what the product does, who it's for, brand voice) before the asset / color / font inventory.
Write DESIGN.md โ a brand cheat sheet covering the visual identity: colors, typography, component styles, layout principles. Use design-styles.json for exact computed values.
Speed option: For fast-pacing videos (billboard-per-beat), DESIGN.md can be a 50-line summary of colors + fonts + do's/don'ts โ not a 300-line document. The sub-agent prompt in Step 5 pastes brand values directly, so DESIGN.md depth only matters for complex compositions.
Gate:DESIGN.md exists (any length) with at minimum: color palette, font choices, and do's/don'ts.
Align with the user on what the video must communicate before talking visuals or assets. Parse the user's prompt โ they probably already gave you the video type and style. Ask only what's missing: the ONE thing this video must say, the narrative arc, and the audience.
Gate: Video type, duration, format, and โ critically โ the message and narrative arc are locked. Without those, Step 3 can't write a concept-first storyboard.
Write the storyboard concept-first: message โ narrative arc โ beats that serve the arc โ techniques per beat โ brand accents pass at the end. Then write the narration script to match. Present both to the user with a beat-by-beat summary. Iterate until they approve.
Gate:STORYBOARD.md + SCRIPT.md exist AND the user has approved the plan.
If Step 2 said no narration โ ask about background music, then skip to Step 5. Otherwise: ask the user which TTS provider (HeyGen TTS, ElevenLabs, or Kokoro), generate audio, transcribe, map timestamps to beats. Then ask about captions.
Gate: Either (a) no narration was requested and storyboard has manual beat timings, or (b) narration.wav + transcript.json exist and beat timings updated with real durations.
Build index.html and compositions following the architecture and pacing chosen in the storyboard (Step 3). Sub-agents run hyperframes lint and hyperframes snapshot on each beat before reporting back.
Gate: Every compositions/beat-N.html has been read top-to-bottom by the main agent against DESIGN.md and STORYBOARD.md. The per-beat checklist lives in step-5-build.md.
Lint, validate, take snapshots scaled to video length (formula: max(beats ร 3, ceil(duration_seconds / 2))), and review each one. Fix issues before delivering. Deliver the localhost Studio project URL โ only render to MP4 on explicit user request.
Deliver something you're proud of. Before handing off, ask yourself: would I post this on social media with my name on it? If not, fix what's wrong.
Gate:npx hyperframes lint and npx hyperframes validate pass with zero errors, and the final response includes the active Studio project URL.
Quick Reference
Video Types
Typical constraints by video type โ use as a starting point, not a formula. Beat count should follow from the content and the narration, not from a target range.
Type
Typical duration
Duration driver
Narration
Social ad (IG/TikTok)
10โ15s
Platform limit
Optional
Product demo
30โ60s
Script length
Full narration
Feature announcement
15โ30s
Feature complexity
Full narration
Brand reel
20โ45s
Music track
Optional, music focus
Launch teaser
10โ20s
Hook energy
Minimal
Beat count is not in this table intentionally โ it should come from the storyboard, not from "social ad = 3-4 beats." A social ad for a complex product might need 5 well-timed beats. A brand reel with one strong visual thesis might need 3.
Special thanks to HeyGen for their generous open-source contributions, which helped shape this skill collection.
Adapted by webconsulting.at for this skill collection
