Skip to main content
skill CX Codex

flux-3-prompt-doctor — Claude Code skill: how to install

flux-3-prompt-doctor evaluates video briefs for FLUX 3 before generation. It resolves conflicting constraints and routes requests to the correct pipeline mode.

MIT 203 installs ★ 138 updated 2026-09-09

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add black-forest-labs/skills --skill flux-3-prompt-doctor -a claude-code
Open on GitHub

What flux-3-prompt-doctor does

The skill audits FLUX 3 video briefs to prevent failed runs. It maps requests to specific routes: t2v for text prompts, i2v when using keyframes, v2v for extending footage, or draft_enhance. It does not construct the final prompt string or call the API.

Feasibility checks enforce strict limits: one subject action and one camera move per brief. It catches contradictory instructions, such as a static camera paired with tracking, or demands for identical faces across separate runs. Elements requiring exact execution—logos, typography, and frame-accurate audio sync—are flagged for deterministic post-production.

Output resolves to one of three verdicts: READY, NEEDS INFO, or REVISE. Non-blocking warnings appear under production risks so generation parameters remain uncluttered.

What it helps with

  • determine the pipeline mode between t2v, i2v, v2v, and draft_enhance
  • catch conflicting camera instructions before generation
  • trim overloaded actions down to a single subject movement per shot
  • isolate typography and logo tasks for deterministic post-production

Example prompts for the agent

  • Diagnose this FLUX 3 brief before I start generation
  • Check if my video storyboard has contradictory camera instructions
  • Evaluate whether this i2v concept is feasible in FLUX 3

How to install flux-3-prompt-doctor

1Skills CLI (Vercel)

npx skills add black-forest-labs/skills --skill flux-3-prompt-doctor -a claude-code

2Manually: put the files in place

~/.claude/skills/flux-3-prompt-doctor/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/flux-3-prompt-doctor/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about flux-3-prompt-doctor

How to install flux-3-prompt-doctor in Claude Code?

Run npx skills add black-forest-labs/skills --skill flux-3-prompt-doctor -a claude-code or place the definition file at ~/.claude/skills/flux-3-prompt-doctor/SKILL.md.

What does flux-3-prompt-doctor do?

It checks FLUX 3 video briefs, identifies contradictory instructions, and assigns the correct media routing mode.

Does this skill call the FLUX API directly?

No, it focuses solely on feasibility diagnosis and outputs a READY, NEEDS INFO, or REVISE verdict without making API calls.

Source text

SKILL.md · MIT
---
name: flux-3-prompt-doctor
description: Use when diagnosing a FLUX 3 brief before generation. Resolve missing, conflicting, or schema-changing requirements.
metadata:
  author: Black Forest Labs
  version: "1.0.0"
  tags: flux, flux-3, bfl, prompt-doctor, validation, routing
---

# FLUX 3 Prompt Doctor

Resolve the decisions that change routing, payload, or production method before a brief
becomes a prompt. Ask only blocking questions; use documented defaults or label
assumptions for everything else. Preserve the user's product names, exact copy, source
roles, and hard constraints verbatim. This skill does not write the final prompt or
call the API.

## Route by what must survive

Every request names its `mode` and carries the matching media field:

| Requirement | Route |
| --- | --- |
| Generate the whole clip from words | `mode: "t2v"`, no media |
| An image must appear on screen exactly as shot | `mode: "i2v"`, `keyframes` |
| Bridge an exact opening and closing frame | `mode: "i2v"`, two keyframes |
| Pass through visual waypoints | `mode: "i2v"`, keyframes as a storyboard |
| Continue from an existing ending | `mode: "v2v"`, `start_video` |
| Render an approved draft without replanning | `mode: "draft_enhance"`, `draft_cache` |

Two questions separate the image routes: must these exact pixels be on screen
(`keyframes`)? Can the source simply be described (then attach nothing)? There is no
field that carries a subject's identity without putting the source on screen; a brief
that needs one either opens each shot from a keyframe containing the subject, or is a
`REVISE`.

## Feasibility

- **Action budget:** one subject action and one camera move per short clip. Revise
  briefs demanding many sequential actions, several locations, exact mechanisms, or
  multiple full dialogue lines.
- **Shot structure:** state one continuous unbroken take, or an explicit sequence:

  ```text
  SHOT ONE: wide aerial of a desert highway at dawn, a single red car speeding through.
  HARD CUT. SHOT TWO: interior close-up, the driver's hands drumming the wheel to the radio.
  HARD CUT. SHOT THREE: from the roadside, the car shrinking into the heat haze.
  Warm engine hum under one continuous music bed across all three shots.
  ```

  Consecutive shots must contrast hard (scale, location, color) or the cut blends into
  a continuous take; each shot needs its own beat; one music bed can run across cuts.
- **Contradictions to catch:** locked-off camera plus tracking; extreme close-up plus
  establishing view; exact frame preservation plus major geometric change; one
  continuous shot plus hard cuts; production-critical generated typography with no
  post fallback; guaranteed speaker identity across separate generations.
- **Reserve for deterministic post** when exactness is a success condition:
  typography, subtitles, logos; frame-accurate sync; final mixing; precise mechanisms;
  cross-generation speaker identity. Generation creates footage and causal intent, not
  a compositor or final mix.

## Verdict

Return exactly one state, with a reason, next action, and a compact handoff
([templates/brief.md](templates/brief.md) when it should be reusable):

- **READY**: route, assumptions, handoff. Recommend a draft first when the concept is
  unproven.
- **NEEDS INFO**: only the blocking questions.
- **REVISE**: name the conflict and the minimum repair.

Non-blocking warnings go under **Production risks**, not a fourth state. Field names
and limits belong to the [API reference](https://docs.bfl.ai); flag intent conflicts
and leave schema validation to `flux-3-generate`.

© Black Forest Labs · MIT · black-forest-labs/skills

Similar skills

All skills for AI and ML →

From the same set8

flux-3-video Routes general FLUX 3 video requests to the exact sub-skills handling prompt repair, visual staging, audio, and generation. CX Codex +1 185installs flux-3-generate flux-3-generate takes a FLUX 3 video API job from submit to a checked MP4, including polling and drafts. Use it when you render video through the API. CX Codex +1 185installs flux-3-cinematic-inserts flux-3-cinematic-inserts structures FLUX 3 text-to-video prompts for standalone insert shots and B-roll. It locks camera movement, physics, and scene continuity around a single visual event. CX Codex +1 185installs flux-3-keyframes-continuation flux-3-keyframes-continuation is a Claude Code skill for building FLUX 3 videos from images or clips with keyframes, storyboards, and continuation planning. CX Codex +1 183installs flux-3-audio-dialogue flux-3-audio-dialogue helps you direct FLUX 3 sound layer by layer: lines, voiceover, ambience, effects and music. Useful when a clip's audio comes out muddled. CX Codex +1 181installs flux-3-product-ads flux-3-product-ads — a Claude Code skill for turning FLUX 3 video and voice into a finished product ad. It guides shot planning, audio-based timing, assembly, and quality checks. CX Codex +1 136installs flux-3-archival-formats flux-3-archival-formats — a skill for Claude Code that configures FLUX 3 video generation for period and archival looks. It defines physical recording formats and specific degradation artifacts instead of moody adjectives. CX Codex +1 136installs

Project sponsors

Companies that keep this analytics open