Website to video
Practical design judgment for AI coding agents: 78 installable skills for craft, research, generation, Figma, and Memoire.
npx -y skills add sarveshsea/design-skills --skill website-to-videoAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Website-to-video capture pack for turning product pages, flows, and browser states into structured video scenes.
SKILL.md
1.1 KB, 192 tokens by cl100k_base, as published. Nobody here has run it
Website To Video
Use this Note when Studio needs to turn a website, app route, or browser flow into a video. The output should be a storyboard plus a runnable Remotion or Hyperframes project, not a pile of screenshots.
Workflow
- Capture the target route state, dimensions, and critical interactions.
- Choose Hyperframes for static/HTML explainers and Remotion for timeline-heavy React composition.
- Create scene beats: first impression, interaction proof, outcome, CTA.
- Store source URLs and captured assets in the video project folder.
- Prepare preview/render commands and a download path for the rendered artifact.
Capture Rules
- Record the exact URL, viewport, and feature state used for every scene.
- Avoid dark blurred atmospheric captures when the product UI needs inspection.
- Crop only after preserving an uncropped source artifact.
- Use local screenshots/assets for render determinism when possible.
Gives 0 of the 12 instructions most video audio skills give in 192 tokens
Counted across 621 of the 795 authors here whose files we hold, read 2026-08-06
- read individual rule files for detailed explanationsin 21 of 621, across 9 files
- Use WAV PCM 16kHz mono audio formatin 13 of 621, across 4 files
- render final videoin 13 of 621, across 6 files
- use this skill when dealing with Remotion codein 11 of 621, across 4 files
- save generated audio to a WAV filein 11 of 621, across 4 files
- handle conversion errors gracefullyin 10 of 621, across 6 files
- add captions to videos alwaysin 10 of 621, across 4 files
- generate music from text descriptions using MusicGenin 9 of 621, across 2 files
- do not skip pipeline layersin 9 of 621, across 3 files
- do not make one tool do everythingin 9 of 621, across 3 files
- never ask the user to paste their full API keyin 9 of 621, across 3 files
- use azure document intelligence for complex pdfsin 9 of 621, across 4 files
Said here and by no other author read
- choose hyperframes for static explainers
- choose remotion for timeline composition
- capture target route state and dimensions
- create scene beats for first impression and outcome
- store source urls and captured assets
- prepare preview and render commands
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.