agentleFS
TakeOff-TeamTakeOff-Team/claude-shortform-video-editor/.claude/skills/storyboard/SKILL.md

storyboard

Skill11 starsChanged 22 days agoMITView on GitHub

Plans the whole edit of a video and shows it as a storyboard (one real frame per beat, what's said, what's on screen) without rendering anything, so the creator can see and change the plan first. Give it an already-edited reference video too and it plans the edit in that video's style. Triggers on "/storyboard", "storyboard this", "plan the edit", "show me how you'd edit this".

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use acquisition-channel-advisor, altitude-horizon-framework and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nandanosqlSkill

    acquisition-channel-advisor

    Evaluate and recommend customer acquisition channels based on product type, target audience, budget, and stage — covering organic, paid, referral, partnerships, and product-led growth.

    Also in 3 projects that use this

  • nandanosqlSkill

    altitude-horizon-framework

    Navigate between strategic (30,000 ft) and tactical (ground level) thinking using the Altitude-Horizon framework — knowing when to zoom in vs. out and adjusting communication to the right level.

    Also in 3 projects that use this

  • +10 more from nandanosql

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No style yet → onboard first (/build-style).

    line 10

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/storyboard

This is /edit-video stopped at the storyboard. Follow .claude/skills/edit-video/SKILL.md steps 0 to 7 exactly (setup + style + memory, project, clip if raw, captions, face, real assets, beats, ./edit storyboard <slug>), then stop.

  • No style yet → onboard first (/build-style). A storyboard in a made-up style teaches them nothing.
  • They gave you an already-edited video to copy ("/storyboard like this one", a link or a file next to their own video): break it down first with ./edit study <url or file> and read the breakdown (layouts, captions, colours, pace, how it opens, how often the screen changes). Plan this storyboard in that video's style for this one edit, without changing my-style/. Say at the top which choices came from the reference. If they love it, offer /inspiration to keep those choices for good. Only their own video gets edited: the reference is for style, never footage.
  • Tell them how to use it: open projects/<slug>/out/storyboard.html, leave a note on any beat, press "Copy all notes" and paste them back, or say it's approved.
  • Apply notes beat by beat and rebuild the storyboard until they approve. Log every note in my-style/feedback.md (lasting ones go into the style).
  • On approval: "Want me to render it?" Then continue from /edit-video step 8.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.