Flick: The Free Claude Code Plugin That Animates Your Video, Scene by Scene
| Step | What happens |
|---|---|
| 1 | You give Flick a video, a public link, or a pasted transcript |
| 2 | It builds a timestamped transcript (Whisper) - your script |
| 3 | It asks only three things: aspect ratio, brand assets, your creative opinion |
| 4 | You approve a compact scene plan (flick-plan.md) |
| 5 | Each approved scene becomes a separately named Remotion animation you preview and revise |
Install commands, first-run requirements, pipeline and license: github.com/Creatorberry/flick (checked Oct 24, 2026)
Project page of the maintainers: creatorberry.com (checked Oct 24, 2026)
The Flick walkthrough this guide unpacks: instagram.com/reel/De1xFonz4Zw (checked Oct 24, 2026)
What Flick Actually Does
Flick is a free, open-source (MIT) plugin from Creatorberry that lives inside Claude Code. You hand it source material - a video file, a public link, or a transcript you paste - and it acts like a motion director for short-form content: it writes a timestamped transcript, plans the video as named scenes (a hook scene, demo scene, steps scene, CTA scene), and builds each scene as its own Remotion animation. You preview every scene in Remotion Studio, ask for changes to only the scene you dislike, and save approved scenes as reusable animation templates for the next video.
Two design choices worth knowing: no background music (Flick adds bundled sound effects only when they match an on-screen action), and the workspace stays local - everything Flick builds lives in a flick-output/ folder on your machine, git-ignored by default.
Install It (2 Commands)
Inside Claude Code:
Then run /flick and follow the prompts. On Codex or other agent CLIs (Grok Build, Gemini CLI, OpenCode, Cursor, Cline), the repo documents the equivalent one-liner: npx skills add Creatorberry/flick --skill flick --global.
The First Run: What It Needs
- Node.js 20+ and Python 3 on your machine, plus network access. If either is missing, Flick tells you how to install it and asks before running any system installer.
- On the first run it creates a local flick-output/ workspace and installs its own tools: Remotion, a bundled FFmpeg binary, Whisper (for transcripts), yt-dlp (for public links), and its sound-effects bundle.
- Each run gives you the plan file (flick-plan.md) to approve, the build files, and one folder per approved scene containing the scene MP4 and a poster image.
Where It Shines - and Where It Does Not
- Best for: adding an original animation pass to scripted short-form content - hooks, demos, step explainers, CTAs - without opening a timeline editor.
- It animates scenes; it is not a full editor. Host footage, captions, pacing and the final cut are still yours to assemble.
- You approve the plan before anything renders. Skipping that review is how you get scenes you did not want.
- Your machine does the work. Rendering many scenes is a real local workload, not an instant cloud job.
- Rights stay with you: only feed it video, fonts, audio and brand assets you have the right to use.
Want the Setup Link in Your DMs?
Comment FLICK on our latest Instagram reel (@amanarya.ai) and the setup link lands in your DMs automatically. Bookmark this guide for the full walkthrough, and follow for daily AI workflows.