agentleFS
adamperlisadamperlis/video-skills/skills/brand-film/SKILL.md

brand-film

Skill45 starsChanged 3 days agoMITView on GitHub

Plan and make a narrative product brand film that moves from a human problem to a product reveal. Use for launch films, cinematic teasers, and campaign videos where story matters more than a step-by-step demo.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write one claim per beat. The proof beat should show the outcome in the real product or a faithful rendering of its UI.

    line 14
  2. Distinctive:

    Do not redraw a logo or end tag from memory if the actual asset exists.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Brand film

A brand film earns the reveal. It makes the audience recognize a problem, turns that problem into a visual idea, then shows the real product as a credible answer.

Shape the story

Plan a small number of beats: problem, escalation, turn, reveal, proof, and landing. The opening should give the viewer a human reason to care before showing the product. Let a physical or visual metaphor carry the problem, but do not let it replace evidence of what the product actually does.

Write one claim per beat. The proof beat should show the outcome in the real product or a faithful rendering of its UI. Check every capability and privacy statement against current product behavior.

Keep one visual language

Read the brand's source materials: colors, typography, mark, materials, motion, sound, and examples. Use a limited set of recurring shapes and transitions so the film feels like one world. Change from the problem world to the product world with a motivated visual transition when possible. Keep text short enough to read in its allotted time.

Do not redraw a logo or end tag from memory if the actual asset exists. Use owned or licensed footage, music, and graphics. A metaphor may be invented; the product UI and claimed outcome must be accurate.

Review before delivery

Storyboard the major frames and transitions. Watch a rough cut for story clarity before polishing. Then check final exports for timing, readable claims, audio mix, brand consistency, and aspect-ratio composition. The film should still make sense when viewed muted, unless the user specifically wants an audio-led piece.

Adding a voice

If the user wants a voiceover, write the narration against the beats, one line per beat, and settle the words before recording. When the user has Walkie connected to their assistant, use the walkie-voiceover skill to turn the script into an audio file, then cut the picture to the voice. The muted check still applies: the voice should deepen the story, not carry facts the picture leaves out.

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.