Flux 3 Keyframes Continuation logo

Flux 3 Keyframes Continuation

Organization
black-forest-labs
flux-3-keyframes-continuation

Use when a FLUX 3 video must be built from supplied images or video. Covers keyframes (i2v) and continuation (v2v).

Overview

Publisherblack-forest-labs
Repositoryskills
Skill nameflux-3-keyframes-continuation
Stars
135
Forks
11
Bundled files
1
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.

  • 1 bundled files

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

  • Open source

    Published by black-forest-labs on GitHub. Read the source before you install it.

Installation

Install the Flux 3 Keyframes Continuation 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/black-forest-labs/skills/tree/master/skills/flux-3-keyframes-continuation
  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/black-forest-labs/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/flux-3-keyframes-continuation .claude/skills/flux-3-keyframes-continuation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Flux 3 Keyframes Continuation 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 Flux 3 Keyframes Continuation 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 Flux 3 Keyframes Continuation 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.

FLUX 3 Keyframes and Continuation

Every supplied source gets one declared job, or is dropped. Two modes condition on media, and each carries exactly one media field:

Required relationshipRequest
These exact pixels open the clip (the stable path)mode: "i2v", keyframes: one image
Exact opening and closing frames, filled in betweenmode: "i2v", keyframes: two images
An ordered storyboard the model connectsmode: "i2v", keyframes: 3-10 images plus an integer duration
Frames pinned at exact momentsmode: "i2v", keyframes: [seconds, image] pairs, ascending, integer duration
Keep going from where this clip endsmode: "v2v", start_video (input max 15 s / 50 MB; output max 15 s)

Keyframes appear on screen, pixel-exact. There is no field that carries a subject without showing the source image; a source used only as inspiration is described in the prompt instead. Media is a public URL or inline base64; keyframe images are at least 256x256.

Prompting each shape

  • One keyframe: the image opens the clip. Prompt what moves; redescribing visible pixels invites re-imagination.
  • Two keyframes: opening and closing are pinned, so describe the stages of the change in order and hold the camera still. Keep the two ends related enough for a plausible path; large jumps invite drift.
  • Storyboard: frames become ordered waypoints. Keep identity, palette, and viewpoint coherent unless a change is intentional.
  • Timestamped pins: a mid-clip pin is a deadline; say what the remaining seconds are for, or they trail off. Pin only what matters; extra anchors stiffen motion.
  • Continuation: write from the ending. Say what happens next and which momentum, framing, subjects, and sound carry across the boundary; do not recap completed action.
text
The camera continues a slow push-in as the closed flower opens naturally into the final
bloom. The stem remains fixed in place, the same soft morning light holds across the
shot, and a light breeze moves the surrounding leaves without changing the composition.
text
Continue from the rider's existing forward momentum. The camera keeps the same low
trailing angle as the horse crests the hill and enters dense fog; hoofbeats and wind
carry across the boundary without a reset.

Chains

For clips longer than one generation: preserve a clean ending and record the subject's direction, speed, and camera relationship; continue from the actual ending artifact; restate only invariants and the next action; review each seam before extending; change one continuity variable at a time when repairing drift. A video input at higher resolution may cap duration below the general maximum, which changes segment planning.

Return the conditioning plan (which mode and shape, and why), the invariants that must survive, the final prompt, and any pin map or transition risks.

Field limits and current constraints: API reference

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 Flux 3 Keyframes Continuation AI skill do?

Use when a FLUX 3 video must be built from supplied images or video. Covers keyframes (i2v) and continuation (v2v).

Why use Flux 3 Keyframes Continuation on TypingMind?

Because you install it once and use it with any model. Flux 3 Keyframes Continuation 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 Flux 3 Keyframes Continuation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/black-forest-labs/skills/tree/master/skills/flux-3-keyframes-continuation. 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 Flux 3 Keyframes Continuation?

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 Flux 3 Keyframes Continuation?

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

Is the Flux 3 Keyframes Continuation AI skill free?

Yes. It is published on GitHub by black-forest-labs 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 👇