Scroll Film logo

Scroll Film

Community
Moh4696
scroll-film

Builds scroll-scrubbed film sections, where scrolling plays a pre-rendered camera move, a product turning, a liquid pour or a fly-through one exact frame at a time, from AI-generated or rendered clips. Covers chaining clips into one seamless film with start and end frames, frame sequences versus scrub-ready video, pinned sections with holds for text, phone versions, loading budgets and reduced motion. Use for "scroll-driven animation", "Apple-style scroll video", "fly through the world as you scroll", scroll cinematics, or when a scrubbed video on a page stutters, jumps at a seam or loads too slowly.

Overview

PublisherMoh4696
Repositoryopen-3d-skills
Skill namescroll-film
Stars
193
Forks
30
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Moh4696 on GitHub. Read the source before you install it.

Installation

Install the Scroll Film AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Moh4696/open-3d-skills/tree/main/skills/scroll-film
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Moh4696/open-3d-skills.git /tmp/open-3d-skills
mkdir -p .claude/skills
cp -r /tmp/open-3d-skills/skills/scroll-film .claude/skills/scroll-film
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scroll Film in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Scroll Film on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Scroll Film is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Scroll film

A scroll film pins a canvas while the visitor scrolls through a tall section, and the scroll position picks the frame. The visitor drives the camera, which is why it feels three-dimensional even when every frame was rendered in advance. It is the right tool when the motion is too rich for real-time 3D (generated worlds, liquids, people) and the path is fixed.

Tools

FileWhat it does
assets/scroll-film.jsThe engine: pinned canvas, progress-to-frame keys with holds, frame sequences or video, smoothing, reduced motion
scripts/prep.py framesJoins clips into one numbered WebP sequence and a manifest
scripts/prep.py videoJoins clips into one MP4 encoded for instant seeking
scripts/prep.py seamsScores every join between clips and fails on a visible jump

Needs ffmpeg and ffprobe, Python 3.9+ and pip install pillow numpy. Making the clips is motion-assets; transparent subjects are alpha-cutout; checking the result is site-check and frame-capture.

Plan before generating anything

  1. Write the story as beats. One beat per scene: what the camera sees at the start, where it goes, what the visitor reads there. Four to seven beats fill a landing page. A beat is one generated clip (a "leg").
  2. Make the keyframes first, all of them, in one style. A leg is generated between a start frame and an end frame, and the end frame of one leg is the start frame of the next. Generate every keyframe still with the same model and the same style reference before any video, and lay them out side by side. A style that drifts between stills drifts across the whole film.
  3. Budget it out loud. Cost is roughly stills plus legs times the price of one clip. A phone version in portrait doubles the video cost (see Phones). Calibrate with one still and one clip before committing (motion-assets covers model choice, pricing and rate limits).

Build

  1. Generate the legs with start and end frames from step 2. Check every join:

    bash
    python3 scripts/prep.py seams legs/01.mp4 legs/02.mp4 legs/03.mp4

    Under 4 is invisible; over 10 is a jump. Fix a bad seam by regenerating that leg anchored on the exact last frame of the previous one (extract it with ffmpeg rather than reusing the still: models shift colour and framing slightly).

  2. Choose frames or video.

    Frame sequence (default)Scrub video
    AccuracyExact frame for every scroll positionSeeks land a little late, worst on Safari and low-end phones
    Size20 to 60 kB a frame at 1280 to 1600 pxAbout a third of that
    Good forUp to roughly 300 framesLong films where size matters more than precision
    bash
    python3 scripts/prep.py frames legs/*.mp4 site/film/lg --width 1600 --fps 24
    python3 scripts/prep.py frames legs/*.mp4 site/film/sm --width 900 --fps 24 --quality 72
    python3 scripts/prep.py video legs/*.mp4 site/film.mp4 --width 1920 --gop 4

    frames drops each later leg's first frame, which duplicates the previous leg's last. video uses a 4-frame GOP and no B-frames: a normal export with a 250-frame GOP makes every seek decode hundreds of frames, and scrubbing stutters.

  3. Mark up the section. Height sets how much scrolling the film takes. Roughly one viewport of scroll per second of film feels deliberate; less feels rushed.

    html
    <section id="film" style="height: 600vh">
      <div class="pin" style="position: sticky; top: 0; height: 100vh">
        <canvas style="width: 100%; height: 100%; display: block"></canvas>
        <div class="captions">...</div>
      </div>
    </section>
  4. Wire the engine.

    js
    import { ScrollFilm } from "./scroll-film.js";
    const small = matchMedia("(max-width: 760px)").matches;
    const film = new ScrollFilm({
      section: document.querySelector("#film"),
      canvas: document.querySelector("#film canvas"),
      frames: { count: 247, src: (i) => `film/${small ? "sm" : "lg"}/${String(i).padStart(3, "0")}.webp` },
      keys: [[0, 0], [0.18, 60], [0.3, 60], [0.62, 160], [0.72, 160], [1, 246]],
      onUpdate: ({ progress }) => captions(progress),
      onReady: () => document.body.classList.add("film-ready"),
    });

    keys are [progress, frame] pairs. Two keys with the same frame make a hold: the film waits at a beat while its caption scrolls in and out. Put a hold at every beat that carries words. Without holds, text slides over a moving picture and nobody reads it.

    smooth (default 0.18) eases the film toward the scroll position, frame-rate independently, so mouse-wheel steps become motion instead of jumps. If the page already smooths scrolling (Lenis), set smooth: 1.

    Captions and layers read progress in onUpdate. Fade a caption in over a short range at the start of its hold and out at the end; keep it off the busiest part of the frame, with a soft scrim behind if needed.

Phones

A 16:9 film centre-cropped to a portrait phone usually loses the subject. Check the crop on every beat. If it fails, generate portrait (9:16) legs from portrait keyframes and ship them as a separate set, switched by a media query, and say up front that this doubles the video budget. A centre crop is acceptable only when every beat keeps its subject in the middle third.

Phones also get the small frame set and should stay under about 8 MB for the whole film.

Loading

  • Put frame 0 in the HTML as an <img> (or as the canvas background) so the first paint is the film, not a blank box.
  • The engine loads frame 0, then the last frame, then a coarse-to-fine spread (every 64th, every 32nd, and so on), six at a time. A visitor who scrolls fast always lands near a decoded frame and sees it sharpen.
  • Video mode fetches the whole file into a blob before playing, so seeks never wait on the network.
  • Serve from a host that answers Range requests. python3 -m http.server does not, and videos it serves cannot seek; locally, use the frame-capture skill's serve.py.

Reduced motion

With prefers-reduced-motion: reduce, the engine steps between the key frames (reducedMotion: "steps", the default) instead of playing, so every beat still shows its picture. "still" shows only the last key frame.

Check

  • Record a scroll-through at low frame rate to judge pacing in seconds, with the frame-capture skill: record.py URL check.mp4 --fps 8 --seconds 20 --scroll "0:0 18:100%".
  • Scrub fast up and down: nothing blank, no flash at a seam, the pin releases cleanly at the end.
  • Load on a throttled connection: first paint shows frame 0.
  • Check a phone viewport and a short laptop viewport (1280x720): captions must not cover the subject.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Scroll Film AI skill do?

Builds scroll-scrubbed film sections, where scrolling plays a pre-rendered camera move, a product turning, a liquid pour or a fly-through one exact frame at a time, from AI-generated or rendered clips. Covers chaining clips into one seamless film with start and end frames, frame sequences versus scrub-ready video, pinned sections with holds for text, phone versions, loading budgets and reduced motion. Use for "scroll-driven animation", "Apple-style scroll video", "fly through the world as you scroll", scroll cinematics, or when a scrubbed video on a page stutters, jumps at a seam or loads t...

Why use Scroll Film on TypingMind?

Because you install it once and use it with any model. Scroll Film is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Scroll Film in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Moh4696/open-3d-skills/tree/main/skills/scroll-film. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Scroll Film?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Scroll Film?

As many as you like. As long as a model supports skills, you can use Scroll Film with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Scroll Film AI skill free?

Yes. It is published on GitHub by Moh4696 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇