AI Skills Catalog
Skills pack Tools

Video Animatic

Turn a scene JSON into a seekable HTML animatic, lint its timing and render review frames or video. Requires a browser-rendering environment and ffmpeg; it does not generate footage.
SKILL SCORE85How it is scored
VerifiedFreeMIT

Works with

Packaged from the source skill for Claude, Codex and 4 more.

About this skill

Video Animatic treats a short film as timed scene data. A scene definition describes shots and layers; the compiler creates a seekable HTML timeline, and the renderer captures requested frames. This makes timing and framing review possible before replacing placeholders with final media.

Use this skill when

  • A short explainer needs a reviewable motion-and-text cut before final artwork or footage is commissioned.
  • One shot changed and you want to inspect or rerender that portion of a data-defined timeline.
  • The same scene needs checks at a second aspect ratio without assuming every layer will still fit.

What it can do

The package contains scene-model support, a motion linter, an HTML compiler, a frame renderer and a shot-manifest utility. It supports text, shapes, image or footage slots and selected data-driven layers. The upgrade manifest can describe candidate generated shots without contacting a generation provider.

Rendering needs separately installed Playwright with Chromium, or the supported Node equivalent, and ffmpeg for video output. Render only HTML compiled from material you trust: a local browser page is executable content, and remote media access needs careful review. Lint findings cover selected timing, contrast and motion conditions, not every accessibility or creative issue. Final audio and delivery work belong to a separate workflow.

Typical workflows

  1. Preview a scene: supply the scene JSON, lint it and inspect the seekable timeline or a low-frame-rate review cut.
  2. Revise a shot: edit the scene data, check the affected timing and recapture the selected shot for comparison.
  3. Prepare final media handoffs: render approved framing and export the shot manifest, then review any later media generation and final delivery separately.

What is inside the skill

Section headings from the original SKILL.md (about 459 words of instructions). Read the full text in the source repository before installing.

  1. Workflow
  2. scene.v1 in one screen
  3. Linter (exit 4 blocks)
  4. Keyframes and the upgrade manifest
  5. Design rules

Bundled files

  • references/motion_craft.md
  • scripts/frame_renderer.py
  • scripts/motion_linter.py
  • scripts/scene_model.py
  • scripts/shot_manifest.py
  • scripts/timeline_compiler.py
  • LICENSE

Example prompts

  • Build a greybox animatic from this 20-second scene JSON. Check narration and on-screen reading time, produce a reviewable HTML timeline and list any blocking motion findings before rendering.
  • Adapt this approved scene from 16:9 to 9:16. Recheck safe areas and text timing, then render the changed shots so I can inspect the framing before replacing placeholders.
  • Prepare first and last keyframes plus a shot-upgrade manifest for these approved scene entries. Keep titles and figures as code overlays and do not call a footage-generation provider.

How to install Video Animatic

Claude Packaged
  1. Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
  2. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
  3. For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
  4. Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
More about skills for Claude
Codex Packaged
  1. Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
  2. Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
  3. Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
  4. AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
More about skills for Codex
GPT Packaged
  1. Download the GPT package from the skill page.
  2. Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
  3. Upload the bundled reference files as knowledge so the GPT can consult them.
  4. Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
More about skills for GPT
Gemini Packaged
  1. Download the Gemini package from the skill page.
  2. For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
  3. Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
  4. Test a matching task and verify the referenced tools and files are available.
More about skills for Gemini
Cursor Packaged
  1. Download the Cursor package from the skill page.
  2. Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
  3. Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
  4. Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
More about skills for Cursor
OpenCode Packaged
  1. Download the OpenCode package from the skill page.
  2. Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
  3. Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
  4. Start OpenCode in the project and test a matching task with the model and permissions you use.
More about skills for OpenCode

Permissions & security

Low risk

Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method

Read project files
Write generated skill files

Video Animatic FAQ

What does the Video Animatic skill do?

Turn a scene JSON into a seekable HTML animatic, lint its timing and render review frames or video. Requires a browser-rendering environment and ffmpeg; it does not generate footage.

Which AI agents can use Video Animatic?

Packages for Claude, Codex and 4 more are built from the same source instructions.

How do I install Video Animatic in Claude?

Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.

Who made Video Animatic and what is the license?

Video Animatic is published by Alireza Rezvani under the MIT license. The source is https://github.com/alirezarezvani/claude-skills/tree/main/video/skills/video-animatic. The catalog keeps the original attribution.

What permissions does Video Animatic need?

Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.

Video Animatic Skill — Alireza Rezvani | AI Skills Catalog