AC scripting-and-storyboarding
The pre-production system — turn a video idea into a shootable, editable plan: the two-column AV script, the storyboard as a decision document, the numbered shot list, the batch-shoot plan, and the paper edit. Use when shoots are chaotic, edits drag, videos feel static ("just me talking"), someone wants to batch-film a week of content in one session, needs a storyboard but can't draw, is planning a multi-shot AI video sequence, or scripts keep running long. Uses the SCENE framework. Reads idea-generation-and-ideation + short-form-video-script or the long-form skill + brand-profile first. A words-only script plans half the video; the storyboard is a decision document, not art; the shot list grouped by setup enables batch shooting. The agent writes the plan; the HUMAN shoots/generates and judges; WoopSocial publishes. Never stages candid-as-real moments or lifts another creator's script. Distinct from short-form-video-script, talking-head-and-piece-to-camera, capcut/descript, luma.
The pre-production system — turn a video idea into a shootable, editable plan: the two-column AV script, the storyboard as a decision document, the numbered…
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1834 tokens
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 994: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.