website-to-video
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
Capture a general website/URL and turn it into a HyperFrames video (site tour, showcase, or social clip from the site's own visuals). Uses headless Chrome screenshots + brand assets. Use when intent is general — portfolio/blog/landing-page showcase or social clip from the site. NOT for: product/SaaS launch or promo (→ /product-launch-video, even from a URL); topic explainer with no site (→ /faceless-explainer); GitHub PR (→ /pr-to-video); adding captions to existing video (→ /embedded-captions); short unnarrated page-highlight motion graphic (→ /motion-graphics). Unclear launch-vs-general-site? Ask one question or start at /hyperframes-read-first.
10 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- calesthio/OpenMontageedited, first seen Nov 9, 2026
- memi-design/design-skillstheir own version, first seen Nov 8, 2026
- OpenMontageInc/OpenMontageedited, first seen Nov 8, 2026
- Rajveerx11/skillsedited, first seen Oct 25, 2026
- sthuthillc/kenectaiedited, first seen Oct 11, 2026
- Gopyr/gopyr-skills-hubedited, first seen Oct 11, 2026
Used with
Projects with it also use pose-library-design, video-toolkit and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LinHao-citySkillpose-library-design
Design reusable 2D character pose libraries, action cycles, and expression states for data-driven animation.
Also in 4 projects that use this
LinHao-citySkillvideo-toolkit
Create professional videos autonomously using claude-code-video-toolkit — AI voiceovers, image generation, music, talking heads, and Remotion rendering.
Also in 4 projects that use this
GopyrSkillazure-speech-to-text
Also in 3 projects that use this
GopyrSkilldashscope
Also in 3 projects that use this
dAAAbSkillheygen
Also in 4 projects that use this
MoizIbnYousafSkillvisual-style
Build a persistent visual brand identity for image generation. Defines how the brand looks visually — aesthetic, lighting, composition, mood — and writes it to brand/creative-kit.md so /image-gen and other creative skills produce consistent on-brand visuals. Three modes: Extract (from website/URL), Build (interview), Reference (mood board/examples). Use when starting any project that needs images, when the user says "visual style", "brand aesthetic", "image style", "visual identity", "how should our images look", "build visual brand", "define our look", or when /image-gen outputs feel generic because no visual style exists yet.
Also in 4 projects that use this
- +5 more from LinHao-city
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 9
- calesthio/OpenMontage★ 81k88% same
- OpenMontageInc/OpenMontage★ 81k88% same
- duyet/clickhouse-monitoring★ 30389% same
- LinHao-city/StoryMind★ 1089% same
- Rajveerx11/skills★ 180% same
- Gopyr/gopyr-skills-hub★ 081% same
- jaron-goh-centr/claude-skills★ 083% same
- Nankov-ai/anthropics-skills★ 089% same
- sthuthillc/kenectai★ 072% same
Wrote their own version · 1
- memi-design/design-skills★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- embedded-captionsSkill
- faceless-explainerSkill
- general-videoSkill
- graphic-overlaysSkill
- hyperframes-animationSkill
- hyperframes-cliSkill
- hyperframes-coreSkill
- hyperframes-creativeSkill
- hyperframes-mediaSkill
- hyperframes-registrySkill
- hyperframesSkill
- mediabunnySkill
- motion-graphicsSkill
- product-launch-videoSkill
- pr-to-videoSkill
- remotion-best-practicesSkill
- remotion-captionsSkill
- remotion-createSkill
- remotion-docsSkill
- remotion-interactivitySkill
- remotion-markupSkill
- remotion-renderSkill
- remotion-saasSkill
- remotion-to-hyperframesSkill
- remotion-upgradeSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
The file
We split this skill into the rules it gives an agent
6 rules. 4 are common, 0 are distinctive, and 2 are very specific to this project.
4
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 27
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 …
- Very specific: line 45
Write DESIGN.md — a brand cheat sheet covering the visual identity: colors, typography, component styles, layout principles.
- Common: line 67
Write the storyboard concept-first: message → narrative arc → beats that serve the arc → techniques per beat → brand accents pass at the …
- Common: line 77
If Step 2 said no narration — ask about background music, then skip to Step 5.
- Very specific: line 90
Gate: Every compositions/beat-N.html has been read top-to-bottom by the main agent against DESIGN.md and STORYBOARD.md.
- Common: line 100
Deliver something you're proud of: Before handing off, ask yourself: would I post this on social media with my name on it?
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Website to HyperFrames
Capture a website, then produce a professional video from it.
Confirm the route before Step 0. This skill makes a video of / from a general site. If the user is really marketing / launching / promoting a product (even from this URL, even "promo for our site") →
/product-launch-video. A topic explainer with no site →/faceless-explainer; a GitHub PR →/pr-to-video; re-cutting / recoloring / reordering an existing video file → out of scope. Routed here on a vague "make a video", or unsure launch-vs-general-site? Read/hyperframes-read-firstfirst (full routing table + § What HyperFrames cannot do).
Users say things like:
- "Turn this website into a 15-second social clip for Instagram"
- "Make a 30-second site tour / showcase from https://..."
- "Capture our homepage and build a video from its own visuals"
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.
Step 0: Capture & Understand the Brand
Read: references/step-0-capture.md
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.
Step 1: Brand Identity
Read: references/step-1-design.md
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.
Step 2: Strategy & Messaging
Read: references/step-2-brief.md, references/capabilities.md (scan the Table of Contents — deep-dive sections only as needed)
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.
Step 3: Storyboard + Script 💬
Read: references/step-3-storyboard.md
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.
Step 4: VO, Timing + Captions 💬
Read: references/step-4-vo.md
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.
Step 5: Build Compositions
Read: The hyperframes skill (load it — every rule matters)
Read: references/step-5-build.md
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.
Step 6: Validate & Deliver
Read: references/step-6-validate.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. Surface that Studio URL only at handoff — it is the final, stable preview; the build-phase snapshots are headless, so do not pop a preview mid-build.
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.
Format
- Landscape: 1920x1080 (default)
- Portrait: 1080x1920 (Instagram Stories, TikTok)
- Square: 1080x1080 (Instagram feed)
Reference Files
| File | When to read |
| step-0-capture.md | Step 0 — capture, understand the brand and product, write strategy-first site summary |
| step-1-design.md | Step 1 — write DESIGN.md brand cheat sheet (5 sections, 250-350 lines; 50-line fast-path for billboard-style social ads) |
| step-2-brief.md | Step 2 — align on message, narrative arc, audience with user |
| capabilities.md | Steps 2 & 5 — full inventory of what HyperFrames can do (24 sections). Scan the TOC during the brief, deep-dive specific sections during build |
| step-3-storyboard.md | Step 3 — storyboard + script (combined) with user review gate |
| step-4-vo.md | Step 4 — TTS provider choice, generation, timing |
| step-5-build.md | Step 5 — build index.html + compositions |
| step-6-validate.md | Step 6 — lint, validate, snapshots (scaled to video length), preview |
| techniques.md | Steps 3 & 5 — 13 primitive animation techniques with code patterns (adapt, don't copy-paste) |
| html-in-canvas-patterns.md | Step 5 — complete code patterns for HTML-in-Canvas effects (lives in the hyperframes skill) |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

