Scripting And Storyboarding logo

Scripting And Storyboarding

Organization
social-media-skills
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.

Overview

Publishersocial-media-skills
Repositoryskills
Skill namescripting-and-storyboarding
Stars
215
Forks
44
Bundled files
5
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.

  • 5 bundled files

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

  • Open source

    Published by social-media-skills on GitHub. Read the source before you install it.

Installation

Install the Scripting And Storyboarding 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/social-media-skills/skills/tree/main/skills/scripting-and-storyboarding
  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/social-media-skills/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/scripting-and-storyboarding .claude/skills/scripting-and-storyboarding
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scripting And Storyboarding 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 Scripting And Storyboarding 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 Scripting And Storyboarding 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.

scripting-and-storyboarding

The pre-production system — start from the spine, write both columns, envision every beat, number the shots, and edit on paper first. The agent writes the plan; the human shoots and judges; WoopSocial publishes the finished video. (Craft skill — no tool file.)

The POV: videos are won in pre-production — the cheapest edit is on paper

Chaotic shoots and endless edits are a pre-production deficit, not a talent deficit: the plan is "where you catch problems before they become expensive fixes on set or in post." Four truths carry this skill. (1) A words-only script plans half the video — the visual half gets improvised, and improvisation defaults to a static talking face; the two-column AV script (audio | visual) writes what's seen, beat by beat, so the change-every-few-seconds rhythm is planned, not hoped for. (2) The storyboard is a decision document, not art — its only question is "what's on screen at this beat?", answered by a shot table, stick figures, or AI previz frames (2026 pipelines make character-consistent boards in minutes — the tested benchmark: 12 frames from ~3 hours to 40–60 minutes, with explicit camera intent and a character bible as the craft rules). (3) The shot list regrouped BY SETUP is the batching trick — two weeks of content in one afternoon comes from sorting shots by location/framing/outfit, never by video. (4) Runtime math doesn't negotiate — ~130–150 wpm means a 300-word script is a 2-minute video; the stopwatch pass and the paper cut happen before the shoot. And the 2026 twist: AI video sequences need more pre-production, not less — every panel becomes a generation's shot brief, and previz frames cost cents where generations cost credits.

Read these first

  1. idea-generation-and-ideation — the idea being productionized.
  2. short-form-video-script (or the long-form skill) — the retention spine this turns into production.
  3. brand-profile + design-and-templates — visual language, end cards.

The framework: SCENE

(Depth: references/the-scene-framework.md.)

  • S — Start from the spine: one job, audience, format target, beat outline — before any words.
  • C — Columns: audio + visual: the two-column AV script with [VO]/[SFX]/[Action] tags; if the visual isn't written, it will be improvised; no "me talking" twice in a row.
  • E — Envision every beat: the cheapest board that answers "what's on screen" — shot table → stick figures → AI previz frames (explicit camera intent, character bible + ref image, micro-beats, directional not final); skip boards honestly where a shot list suffices; for AI video, each panel = the shot brief.
  • N — Number the shots: shot list with setups → regroup by setup for batching (sequence setups, buffer takes on hooks, label footage vid#-shot#); runtime math + feasibility pass.
  • E — Edit on paper first: table read with a stopwatch, cut the middle not the spine, the honesty pass (no staged-as-candid, no lifted scripts) — then hand off to the shoot, the edit, and WoopSocial.

The reality (verify-quarterly)

Stable craft: the two-column AV script (broadcast standard), ~130–150 wpm runtime math, the storyboard-as-decision-document, the by-setup batch regroup. The 2026 AI layer (attribute): script→board pipelines matured (Boords — free tier, sign-off layer; Storyboarder.ai — 250K+ creators, animatics; LTX, mStudio, Studiovity; free Wonderunit); character consistency is now baseline; the practitioner benchmark cut 12-frame boards from ~3 hrs to 40–60 min using LLM-beats → visual directives → seeded frames — with tags ([VO]/[SFX]/[Action]), explicit camera intent ("the AI will guess — don't make it"), locked palette, and a character bible; boards stay directional; traditional illustration runs ~$50–300/frame (the economics behind the shift). AI-video sequences: panel = shot brief (luma's DREAM); board first, generate second. Attribute all; verify-quarterly. Full detail: references/scripting-and-storyboarding-2026-reality.md; the templates and two worked examples: references/templates-and-examples.md.

Honest scope (never violate)

  • The agent writes every planning artifact (beats, AV script, board/briefs, shot list, batch plan, timing pass, footage map); the human shoots/generates, judges every take, and approves — the agent cannot see footage or operate a camera and never fabricates "that take works." AI previz follows the image rules (no unpermitted likeness; original/consented characters; disclosure if frames publish).
  • Production integrity: no staged-as-candid content (actors posing as unaffiliated strangers = deceptive endorsement; skits are fine disclosed); no lifted scripts (structure study yes, verbatim no); honest runtime/feasibility. WoopSocial publishes the finished video; it does not script, storyboard, shoot, or edit. (Full scope: references/scope-and-connections.md.)

Distinct from its siblings (route correctly)

scripting-and-storyboarding (this) = the pre-production system · short-form-video-script = the retention-words craft (WATCH writes the spine; SCENE productionizes it) · talking-head-and-piece-to-camera = the on-camera delivery · capcut / descript = the edit executing the AV script's visual plan · luma / ai-video = the generations whose shot briefs the panels become · flux / image-prompt = previz frames + reference stills · storytelling-and-narrative = the narrative angle/WHAT this schedules into shots · idea-generation-and-ideation = supplies the idea.

Where this connects

Reads first: idea-generation-and-ideation + short-form-video-script/long-form + brand-profile + design-and-templates. Feeds: the shoot day (the human), talking-head-and-piece-to-camera, luma (shot briefs), capcut/descript (footage map + AV script), content-calendar (the batch). Publishes via: the finished video → scheduling-and-queue → WoopSocial. Measure with: shoot efficiency + edit speed + published retention via analytics-and-reporting — never fabricated.

Definition of done

A shootable, editable plan: the spine confirmed (one job, beat outline from the script skill), the two-column AV script written with every visual beat specified ([VO]/[SFX]/[Action] tags; no "me talking" twice in a row), the storyboard produced at the cheapest sufficient fidelity (shot table, stick figures, or AI previz frames with explicit camera intent + a character bible — directional, never final art; skipped honestly where a shot list suffices), a numbered shot list regrouped by setup with the batch plan, buffer takes, and a labeled footage map, the runtime verified by stopwatch math (~130–150 wpm) and cut on paper before the shoot, and the honesty pass held (no staged-as-candid, no lifted scripts, feasibility stated straight); AI-video panels written as generation shot briefs with previz-before-credits economics; the human shooting and judging, the edit receiving a clean handoff, and the finished video publishing via WoopSocial; nothing staged as real, nothing plagiarized, no fabricated production claims; and correctly distinguished from short-form-video-script, talking-head-and-piece-to-camera, capcut/descript, and luma.

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 Scripting And Storyboarding AI skill do?

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...

Why use Scripting And Storyboarding on TypingMind?

Because you install it once and use it with any model. Scripting And Storyboarding 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 Scripting And Storyboarding in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/social-media-skills/skills/tree/main/skills/scripting-and-storyboarding. 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 Scripting And Storyboarding?

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 Scripting And Storyboarding?

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

Is the Scripting And Storyboarding AI skill free?

Yes. It is published on GitHub by social-media-skills 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 👇