# AI use cases for Film Studio Skills (machina-exm/film-studio-skills)

Repo: [machina-exm/film-studio-skills](https://github.com/machina-exm/film-studio-skills) | Use cases: 5 | Page: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/

Film Studio Skills is a set of seven installable agent skills that take a film script or one-paragraph idea through a fixed pipeline to generation-ready shot prompts with consistency gates.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Turn a script into scene tables and shot cards: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/script-to-shot-cards/
- Lock a recurring character before filming their shots: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/lock-recurring-character-passport/
- Write shot prompts only after assets are locked: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/shot-prompts-with-consistency-gates/
- Build a visual bible from approved reference images: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/visual-bible-from-reference-images/
- Scaffold a film project folder with pipeline rules: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/project-folder-with-pipeline-rules/

## How to turn a script into scene tables and shot cards with Film Studio Skills

Repo: [machina-exm/film-studio-skills](https://github.com/machina-exm/film-studio-skills) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README

Break a script or one-paragraph idea into a scene table and one 22-field shot card per scene.

**Who it is for:** An independent filmmaker or AI video creator with a finished script who needs a shot list before any generation starts.

**The problem:** Shot lists for AI video are slow to write by hand, and missing details like wardrobe, lens, or on-screen text cause drift later.

**The outcome:** A project folder with a scene table, one shot-card file per scene with all 22 fields filled, and in-frame text pulled onto its own task list.

### Steps

1. Install the seven skills by copying the folders from `skills/` into `~/.claude/skills/`, or run `npx skills add` for your harness.
2. Run `/setup` and answer one question at a time about the image and video models you use.
3. Run `/studio-init` and give the project name.
4. Run `/film-breakdown` and paste your script, treatment, or idea, then answer its questions scene by scene.

### Prompt to paste into your agent

```text
Using the film-studio-skills repo, run /setup, /studio-init, and /film-breakdown on <script file>. Expected output: a scene table and one shot-card file per scene in the project folder. Verify that every shot card has all 22 fields filled before stopping.
```

### Caveat

The README treats model tables as snapshots, so confirm the current model names during /setup rather than trusting any listed model.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/script-to-shot-cards/

## How to lock a recurring character before filming their shots with Film Studio Skills

Repo: [machina-exm/film-studio-skills](https://github.com/machina-exm/film-studio-skills) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README

Build a character passport and pass the stress test so its registry row reads locked.

**Who it is for:** A creator with a character who appears in many scenes and whose face, clothing, or age could drift between generations.

**The problem:** A passport built from one lucky image looks consistent in one clip but fails across angles, lighting, and co-stars.

**The outcome:** A passport with a verbatim descriptor, separate tagged state variants, and a registry row set to locked after a 10 out of 10 repeatability pass.

### Steps

1. Run `/asset-passport` and name the character, then answer its questions until the descriptor has no gaps.
2. Generate the grey-background reference-sheet images from the prompts the skill writes, using your image model.
3. Run `/stress-test` to build the combat matrix and test prompts for the character.
4. Check that the registry row flips to locked only after the character passes 10 out of 10 repeatability.

### Prompt to paste into your agent

```text
Using the film-studio-skills repo, run /asset-passport and /stress-test for the character <character name>. Expected output: a passport with a full descriptor and a registry row marked locked or draft. Verify that the row is locked only if all test prompts scored 10 out of 10.
```

### Caveat

The stress test uses your own image model outputs, so the lock is only as reliable as the test images you actually generate and score.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/lock-recurring-character-passport/

## How to write shot prompts only after assets are locked with Film Studio Skills

Repo: [machina-exm/film-studio-skills](https://github.com/machina-exm/film-studio-skills) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README

Generate 15-block shot prompts that refuse to run while any in-frame asset is still draft.

**Who it is for:** A video creator who has locked characters and locations and needs prompts for each shot without introducing drift.

**The problem:** Writing prompts by hand per shot invites paraphrased descriptors, reordered blocks, and generations that cannot be compared.

**The outcome:** A generation-ready prompt in the same 15-block order with every descriptor pasted verbatim, plus a generation log with one line changed per attempt.

### Steps

1. Confirm every asset in the shot's scene reads locked in the registry.
2. Run `/shot-prompt` on one shot card and let it check the passports of everything in frame.
3. Paste the generated 15-block prompt into your video model.
4. Log each attempt with its verdict and change one line per retry, as the skill instructs.

### Prompt to paste into your agent

```text
Using the film-studio-skills repo, run /shot-prompt on the shot card <shot card file> with its locked passports. Expected output: a 15-block prompt with no negative prompt section and the descriptors pasted verbatim. Verify that the skill refuses to write the prompt if any in-frame asset is still draft.
```

### Caveat

The skill controls prompt structure, but a video model can still fail a locked shot, and the README says a shot that has not landed by attempt 15 needs a simpler shot.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/shot-prompts-with-consistency-gates/

## How to build a visual bible from approved reference images with Film Studio Skills

Repo: [machina-exm/film-studio-skills](https://github.com/machina-exm/film-studio-skills) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README

Caption reference boards, ban anti-references, and record an approve, revise, or reject decision.

**Who it is for:** A director or art lead who has reference images for a film's look and needs them written down as a specification.

**The problem:** Images picked for mood with no notes become unusable when the look has to be reproduced weeks later.

**The outcome:** A visual bible with a caption on every reference, a ban list of anti-references, and a written decision on each board.

### Steps

1. Collect the existing reference images you want to use, since the skill asks you to find the image before describing it.
2. Run `/reference-board` and supply one board at a time.
3. Answer the caption prompts so each image names exactly what is taken from it.
4. Record a decision of approved, revise, or rejected on every board before calling anything locked.

### Prompt to paste into your agent

```text
Using the film-studio-skills repo, run /reference-board on the reference images in <folder>. Expected output: a visual bible with captioned references, a ban list, and a written decision per board. Verify that no board is treated as locked without an approved decision.
```

### Caveat

The skill only organizes references you supply, so the quality of the visual bible depends on the images you bring to it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/visual-bible-from-reference-images/

## How to scaffold a film project folder with pipeline rules with Film Studio Skills

Repo: [machina-exm/film-studio-skills](https://github.com/machina-exm/film-studio-skills) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README

Create the assets, prompts, generations, and selects folders with the rules written in.

**Who it is for:** A solo creator starting a new AI film who wants the file system to keep track of versions and accepted takes.

**The problem:** Without a fixed folder layout, reference files get renamed, rough takes leak into the edit, and nobody knows which asset version was used.

**The outcome:** A project tree with assets, prompts, generations, selects, and docs folders, plus seeded breakdown, visual bible, registry, and generation log templates.

### Steps

1. Run `/setup` once to write your image and video model choices into your project's instruction files.
2. Run `/studio-init` and answer its one question, the project name.
3. Open the docs folder and read the three laws the skill wrote in.
4. Keep raw attempts in `generations/` and move only accepted takes into `selects/`.

### Prompt to paste into your agent

```text
Using the film-studio-skills repo, run /setup and then /studio-init for a project named <project name>. Expected output: a project tree with assets, prompts, generations, selects, and docs folders. Verify that the docs folder contains the breakdown, visual bible, registry, and generation log templates.
```

### Caveat

The README says API keys are never written to the config, only the name of the environment variable that holds them, so you still need to set that variable yourself.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/machina-exm-film-studio-skills/project-folder-with-pipeline-rules/