Skip to content
Back to skills

Shooting Script

ASecurity

Compile screenplay lines, performance blocking, shot briefs, scene state, and dialogue timing into a portable machine-readable shooting script with positions, moves, actions, camera coverage, exact dialogue, and timing sources.

  • 2 stars
  • 0 votes
  • 0 copies
  • 7 views
  • Added September 9, 2026
ai-agentsperformance

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add badgids/Story-Film-Skills --skill shooting-script --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Shooting Script?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Shooting Script
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/badgids-shooting-script/badge)](https://www.skillsdirectory.com/skills/badgids-shooting-script)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: shooting-script
description: Compile screenplay lines, performance blocking, shot briefs, scene state, and dialogue timing into a portable machine-readable shooting script with positions, moves, actions, camera coverage, exact dialogue, and timing sources.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---

# Shooting Script

## Workflow

1. Read core contract, `HIERARCHICAL_PRODUCTION_PLANNING.md`, `VISIBLE_DIALOGUE_SYNC.md`, `SHOOTING_SCRIPT.md`, screenplay, line manifest, blocking, shot briefs, voice cues when present, continuity, and production capabilities.
2. Work one approved scene or sequence at a time.
3. Write `03_preproduction/shooting_script.json`. Preserve exact dialogue and stable IDs.
4. For every unit, record current positions, moves, actions, covering shot IDs, constraints, and timing source.
5. For visibly spoken dialogue, compile the matching `lip_sync` record and ensure at least one covering shot carries the same exact line and speaker requirement.
6. Keep movement separate from non-locomotion actions.
7. If measured voice duration exists, propagate it into visible-dialogue timing and use it instead of an estimate where it controls shot/action/subtitle timing.
8. Never rewrite dialogue or choose a new story beat to fit a technical limit. Route the conflict upstream or split the production unit.
9. Run `production-coverage` after compiling the requested scope.

## Done

The approved scope can be executed or translated into generation tasks without reconstructing performer state, dialogue, camera coverage, or timing from chat.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.