The page this skill built from examples/starlot, working in your browser. Opens in a new tab.
5-second example rendered by this skill from examples/starlot · 1280×720
What you get
- A one-page hero and a paste-in embed with your name, words and links
- Your title card projected on the drive-in screen after a 3-2-1 film countdown, tracked to the camera so it stays on the screen
- Words laid over the film (in this one nothing is cut out: the screen is the place for words)
- The intro animation tied to the film's own clock, so words and picture stay in step
- A phone layout: the headline, screen card and ticket stay in the frame, the introduction and buttons move into a block underneath
- A still of the last frame for reduced motion, blocked autoplay or a slow connection, so it is never blank
- A 1080p MP4 with the film's sound and a poster, rendered frame by frame
- Checks at 390, 768, 1280 and 1920 px for overflow, overlaps, links and script errors
- Open-source licenses for every part it builds on
Good fit
- Cinemas, film clubs, festivals and outdoor screenings can open on a desert drive-in at dusk, with their own film or event on the glowing screen.
- Ticketing and events brands get a 3-2-1 film countdown that flashes into a NOW SHOWING card, plus an admission ticket with a price stamp and a serial number.
- Brands with a short, punchy line can set it as a neon script word over two giant block words, such as Tonight / Double / Feature.
Not for
- Swapping in your own video: the title card is placed and moved for this film, and the scene (a 1950s drive-in at dusk) is the design
- Changing the colors, fonts or layout through settings (every word and link is yours; the look is fixed)
- Long headlines: each field has a length limit the build enforces, and the screen title takes up to 10 characters
- Sound on the live page (browsers only autoplay muted video; the MP4 keeps the sound)
- Full landing pages below the hero (see the Landing Pages series)
About this skill
A website hero on five seconds of generated footage: a 1950s drive-in in the desert at dusk, rows of pink and cream classic cars facing a huge glowing screen while the stars come out and the camera slowly pushes in. A 3-2-1 film leader counts down on the screen, it flashes, and your own title card flickers on and moves with the camera. In the sky beside it: a turquoise neon script word and a giant cream block headline with a stacked sunset shadow. Around it: an atomic-star wordmark and links, an admission ticket, sparkles, two buttons and film grain. Your agent writes one hero.json with your words and links; the build checks every length and writes a page and an embed, and a recorder makes a 1080p MP4 with sound.
Example request
Make a Drive-In hero for our outdoor cinema club: script word 'Friday', big words 'Movie' and 'Night', this week's film on the screen, our links and buttons, and record the video for our launch post.
How it works
Your agent
- 1
Collect the words
Every number, price and claim must come from the person.
- 2
Write hero.json
Copy
<skill>/examples/starlot/hero.json(Starlot, an app for reserving a spot at drive-in theaters) and replace every value. - 3
Build
It lists every problem at once (a missing field, a word too long for its place, a bad link) and writes nothing until they're fixed.
- 4
Check
It serves the page on localhost and opens it at 390, 768, 1280 and 1920 px wide and with reduced motion.
- 5
Look at it
Open the address it prints.
- 6
Record the video (optional)
Writes
out/preview.mp4(1920×1080, 30 fps, five seconds, with the film's sound) andout/poster.png(the last moment). - 7
Put it on the site
Either use
out/index.htmlas the page, or pasteout/embed.htmlinto an existing page and copyout/assets/next to it (or change theassets/paths to where you host them).
- 1
You get
- out/preview.mp4
- out/poster.png
- out/index.html
- out/embed.html


What you need
- Node.js 18 or newer. Nothing to install.
- Chrome, Chromium or Edge, for the checks and the video (the scripts find it; set
CHROME_PATHif they don't). - ffmpeg for the video (
brew install ffmpeg,winget install ffmpeg,apt install ffmpeg; or setFFMPEG_PATH). - A web server for the page. Opened straight from disk (
file://) browsers won't let the page draw the film, and it shows the still;node scripts/serve.mjs outserves it on localhost. - Internet access when the page is opened: GSAP and the fonts load from jsDelivr (pinned, with an integrity hash) and Google Fonts. Without GSAP the hero shows its still with every word in place.
Last checked Oct 27, 2026: the package’s own build and render commands ran and passed.
If something goes wrong
The page shows a still picture instead of the film
It was opened from disk; run
node scripts/serve.mjs outand open the address. If it still shows the still, the section'sdata-fh-stillattribute says why (reduced-motion,autoplay-blocked,film-failed,film-slow,no-timeline).The film doesn't play on the live site but did locally
The film is on another domain without CORS headers. Serve
assets/from the same site as the page, or addAccess-Control-Allow-Originon the CDN.The build says a field is too long
Shorten the words. The block words are sized for up to 7 characters and the screen title for 10.
What’s in the download
- SKILL.md12.7 KBthese instructions.
- examples/
- examples/starlot/1.04 KB1 file
- scripts/
- scripts/kit/the Footage Heroes kit the four scripts run (
build.mjs,runtime.jsfor the browser,frame.css,check.mjs,serve.mjs,record.mjs,cdp.mjs);scripts/kit/KIT.mdsays how it fits together. - scripts/kit/build.mjs13.6 KB
- scripts/kit/cdp.mjs4.90 KB
- scripts/kit/check.mjs5.48 KB
- scripts/kit/frame.css2.24 KB
- scripts/kit/KIT.md4.52 KB
- scripts/kit/record.mjs7.23 KB
- scripts/kit/runtime.js7.94 KB
- scripts/kit/serve.mjs2.55 KB
- scripts/build.mjs146 Bchecks
hero.jsonagainsttemplate/fields.jsonand writes the page, the embed and the assets. - scripts/check.mjs146 Bserves the page and checks it at four widths and with reduced motion.
- scripts/chrome.mjs3.63 KBfinds Chrome, Chromium or Edge.
- scripts/record.mjs148 Brenders the words frame by frame and lays them on the film with ffmpeg:
preview.mp4with sound andposter.png, or one still. - scripts/serve.mjs146 Bserves a built hero on localhost to look at.
- template/
- template/fields.json3.32 KBevery field of
hero.jsonwith its limit, plus the film's length and the hero's colours and fonts. - template/hero.html14.7 KBthe design: its CSS, the headline layer with the screen card, the layer in front, and the GSAP timeline (including the tween that keeps the card on the screen as the camera pushes in).
- NOTICE.md1.13 KB
- TESTED.json407 B
19 files · 85.9 KB · installs to ~/.claude/skills/drive-in-hero for Claude Code and ~/.agents/skills/drive-in-hero for other agents
Credits and licenses: NOTICE.md plus any LICENSE files inside the ZIP.
Similar Skills
View allDetails
- Output
- Retro hero on generated footage · your title card on the drive-in screen · page + embed · 1080p MP4 with sound
- Needs
- Node.js 18+, Chrome, and ffmpeg for the video; the page needs a web server (a local one is included)
- Series
- Footage Heroes · 17 skills
- Updated
- Oct 27, 2026
- Checked
- Oct 27, 2026: its own commands ran and passed. That is a working check, not a security audit.
Written for
See all 31 agents that read skill folders.
Install guides
For your agent
Generates with
Installed it? Tell others how it went. Reviews come from people who installed this skill.
Write a reviewFAQ
Can I put my own video behind the headline?
No. The title card is placed on this film's screen and moved with its camera, so the footage is part of the design. Every word and link is yours through hero.json; the footage, colors, fonts and layout stay as they are.
How long can the words be?
The script word takes up to 8 letters, each giant block word up to 7, the screen title up to 10 and the wordmark up to 10. The build lists every field that is too long and writes nothing until they are fixed. Words made mostly of wide letters such as M and W can still be too wide, so look at the page before you ship it.
What do visitors see if the film cannot play?
The last frame as a picture, with every word and the title card in place. That covers reduced motion, no GSAP, blocked autoplay, a film that takes more than 8 seconds to start, or a page opened from disk instead of a web server.
Which agents is Drive-In Hero written for?
Any agent that reads SKILL.md folders, including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode.
Do I own what I make with it?
Yes. Everything your agent makes with this skill is yours, including for client and commercial work.
What if it doesn’t work for me?
Email support@lookbk.dev within 7 days of buying and we’ll fix it or refund you.
Credits and licensesBuilt on greensock/GSAP
What Lookbk adds on top of greensock/GSAP (Standard License): the footage, which was generated for Lookbk (a still image animated into film), and the layout, template and Footage Heroes kit, all written for Lookbk. GSAP (free under its Standard License) loads from a pinned CDN with SRI; the fonts are from Google Fonts.
Credits and licenses for the open-source software and fonts it uses are in NOTICE.md inside the download.