SkillAgentSearch skills...

code-brand-film

用代码生成 15 秒品牌宣传片的 Agent Skill(HyperFrames + GSAP + Python 合成配乐)

Install / Use

npx skills add nutllwhy/code-brand-film

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

73/100

Category

Other

Supported Platforms

Zed

Our assessment of code-brand-film

code-brand-film scores 73/100 on our quality scale, 305th of 329 Other skills we index.

Its SKILL.md is 15 KB long, split into 7 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
30/30
Structure
16/20
Description
12/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 29 days ago, so code-brand-film is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

code-brand-film compared with similar skills

All 4 of these similar skills score higher than code-brand-film; compare them before choosing.

SkillScoreStarsUpdatedFormat
code-brand-film (this skill)by nutllwhy73029d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server
crawl4aiby unclecode10087.4k3d agoMCP Server

Frequently asked questions

How do I install code-brand-film?
Run npx skills add nutllwhy/code-brand-film. The install tabs above show the steps for each supported agent.
Which AI agents does code-brand-film work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is code-brand-film safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is code-brand-film still maintained?
The repository was last updated 29 days ago, so code-brand-film is actively maintained.

name: code-brand-film description: > Produce a short brand film or product promo (10-60s, typically 15s) entirely as code: one static HTML page with a paused GSAP timeline that a renderer seeks frame by frame, plus a music score synthesized in Python. Use when the user wants a 品牌宣传片, 广告片, 宣传动画, 产品短片, 发布会开场视频, brand film, promo video, product teaser, logo animation, or a generated ad spot — especially when they ask for 高级感 / 艺术感 / 电影感 / 别像模板, or when an existing video "looks like AI made it" or "too simple" and needs to be redone properly. Also use when a film already exists and needs a score, a soundtrack, background music, or 配乐, or when a code-generated video needs ghosting, contrast, font, or transition defects fixed. metadata: category: media

Code-generated brand films

Three things decide whether a film ships. Do not skip any of them.

  1. Read all ten files in the reading table below, plus the example's src/index.tpl.html. Reading only creative.md / pipeline.md / scoring.md reproduces the rejected films described here.
  2. Search for the brand's real logo and imagery and record them in assets.md, then write shot-list.md and copy.md — all before the timeline.
  3. Run all three gates and paste their output in your delivery: scripts/film_audit.py film/index.html before rendering, node scripts/layout_audit.mjs film/index.html before rendering, scripts/frame_audit.py film/renders/silent.mp4 after. All three print 0 failed, or the film is not delivered. Lint passing means the page is valid, not that the film is good.

A film is one static HTML page inside film/, driven by a paused GSAP timeline that the renderer (HyperFrames) seeks frame by frame. Every asset is a local file. The score is a separate Python program that writes a WAV, muxed onto the silent picture at the end.

The failure this skill exists to prevent

The usual failure is not a broken film, it's an under-built one: it lints clean, has no bad frames, and still looks like a template. A real example built from an earlier version of this skill had 18 tweens, one entrance mechanic (fade + slide), only crossfades between acts, a logo redrawn as a circle, system fonts, a tagline nobody had written, and no product on screen. The two accepted films it was compared against had ~105 tweens, 9–12 mechanics, 2–4 non-crossfade transitions, and showed the product working in most acts.

So this skill sets floors you can measure and gives you code to copy. There are three gates: scripts/film_audit.py on the HTML (floors), scripts/layout_audit.mjs on the HTML in a real browser (placement), and scripts/frame_audit.py on the rendered MP4 (pixels). All must print 0 failed. A later film passed the first and last and was still rejected for placement: headline under the input bar, logo on the first character, a notification card parked on the corner mark. The layout gate exists for that.

The floors are minimums, not targets. A later film cleared the code gate at exactly 70 tweens and 8 mechanics, padded with breathing headlines, and was still an abstract ink-drop animation covering 3% of the frame with no product in it. The tween count now excludes filler, and the pixel gate exists because pixels cannot be padded. If you find yourself adding tweens to pass a number, stop: the film is missing content, not motion. Aim at the reference example, not the floor.

A third film came from an agent that read only creative.md, pipeline.md and scoring.md, never ran either gate, and "fixed the single worst frame" on a picture that was mostly empty. Metaphor: a stone thrown into a lake, ripples growing six glowing icons on a dark purple void. It linted with 0 errors and had a loudness-matched score. It also had 36 tweens, 3 mechanics, no logo, no shot list, 1.3% of the frame covered and a 4.4s still stretch: 13 failed checks. Everything it needed to avoid that was in the files it didn't open.

A fourth film followed every step, passed all three gates (109 tweens, 10 mechanics) and still lost clearly to a film of the same product that would have failed the old floors. The brand had shipped its own product animations; the losing film used three of them, held two still photos for six seconds under focus brackets and capture rings, put grain over the brand's white sweep, and changed acts with a different trick every time. The winner cut seven official clips on a stage sampled to their exact ground, drew nothing on the product, and used one transition taken from the product's hinge on every act change. When the brand ships motion, read references/footage-led.md — the audit switches to its floors automatically.

Read these — in this order

| Step | File | Why | | --- | --- | --- | | before anything | references/creative.md | metaphor, five-act timing, motion rules, palettes, the AI-look traps | | before placing anything | references/layout.md | zone map per act, hard placement rules (text never covered, logo never on text, title safe, no half-parked cards) | | before anything | references/assets.md | where to search for the real logo and imagery, the five-point logo check, the assets.md manifest | | before anything | references/quality-bar.md | the numbers, the mechanic list, the transition list, product truth, real assets | | if the brand has product video | references/footage-led.md | footage-led films: harvest the motion, stage = studio ground, no texture, one signature transition from the product's shape, draw nothing on the product, localised copy | | before coding | references/shot-list.md | the table you fill in first; worked example included | | while coding | references/recipes.md | copyable GSAP for 27 mechanics and transitions (24–27: fold on a seam, seam open, anchor match cut, pose burst) | | while coding | examples/office-agent/ | a complete 400-line film that clears every floor — read its timeline | | scaffold / render | references/pipeline.md | layout, template+build, lint warnings, macOS pitfalls, defect checklist | | music | references/scoring.md | beat grid from picture, energy plan, mix graph, verify without ears |

Do read the example's src/index.tpl.html end to end before writing your own. Seeing how much one 15s film contains is worth more than any rule here.

Workflow

  1. Collect sources. Brief or product page: the mandatory selling line, 3–5 concrete product behaviours, required copy and CTA, red lines. Then go searching (references/assets.md): user-supplied files → press / brand kit → official site (header SVG, og:image, screenshots) → app store listing → official social posts. Bring back the current logo and ≥ 2 official images, at least one showing the real product. Run the five-point logo check (right product, current version, right variant, untouched, resolution) and write it all into assets.md with source URLs. Never redraw a logo, never take one from a logo-aggregator site. Start with scripts/harvest_page_images.py <product-page> --video — it pulls every image, SVG and product clip the page uses and makes numbered contact sheets to pick from. Harvest the country page in the audience's language too; copy comes from there. Clips found? The film is footage-led (references/footage-led.md): footage carries acts 2–4, stills only as a burst, stage colour = the clips' sampled ground. Physical product? It appears as its official photo every time it is on screen; acts 2–4 show its output through its own UI, and each feature line gets a proof shot (creative.md example C, recipes.md 20–23).
  2. Find the metaphor — one sentence with a physical verb, ideally taken from the brand's own asset or the selling line's own words (creative.md).
  3. Write shot-list.md and copy.md in the film project (next to film/; the audit fails without them). copy.md lists every on-screen line with its source; see examples/office-agent/copy.md. Shot list from the template. Every act: ≥ 5 timed events, a named camera move, a named exit transition, three depth layers, a product behaviour (except hook/lockup), and a source for each line of copy. Run the self-check at its bottom. If the user is around, show it.
  4. Scaffold. film/hyperframes.json (copy assets/hyperframes.json), film/package.json pinning hyperframes@0.8.78, src/index.tpl.html, src/build.py (copy scripts/build_template.py). Start from the example's texture layer (grain, falloff) — except in a footage-led film, where texture over the brand's studio ground is a fail. Do not add a page counter (02 / 05), a progress bar or corner labels — they make the film look like slides.
  5. Fonts. python3 src/build.py, then scripts/fetch_cjk_fonts.sh src/chars.txt film/assets/fonts for Chinese. Latin fonts: download woff2 files into film/assets/fonts/. Every @font-face uses url() to a local file; local() is not allowed.
  6. Author the timeline act by act from the shot list, pulling mechanics from recipes.md. Run npx --yes hyperframes@0.8.78 lint after each act.
  7. Gate. python3 scripts/film_audit.py film/index.html → must print 0 failed. Fix every FAIL by adding real content, not by gaming the regex. Then node scripts/layout_audit.mjs film/index.html --shots .gates/layout → must print 0 failed. Open the screenshots, move things per references/layout.md, re-run.
  8. Render silent, then python3 scripts/frame_audit.py film/renders/silent.mp4 → must print 0 failed. Make a contact sheet and put it next to examples/office-agent/reference-sheet.jpg; answer the three comparison questions in quality-bar.md. If yours is clearly thinner, go back to step 6 — add product on screen, not decoration. Then fix the single worst frame.
  9. Score it — only now, after all three gates pass. score_lib prints a NOT READY banner if .gates/ is missing any of the three pass stamps. (scripts/score_template.py → audio/score.py), mix SFX, loudnorm to −14 LUFS, mux with -c:v copy.
  10. Deliver one MEDIA:/file line per output. State what you verified (both audits' numbers, lint, loudness, the reference comparison) and what only the user can judge (taste, how the music sounds). Flag any invented copy and any low-res logo.

Commands

python3 src/build.py
python3 <skill>/scripts/film_audit.py film/index.html           # code gate: must be "0 failed"
node <skill>/scripts/layout_audit.mjs film/index.html --shots .gates/layout   # placement gate: "0 failed"
cd film
npx --yes hyperframes@0.8.78 lint                                # target 0 errors; read every warning
PRODUCER_BROWSER_GPU_MODE=hardware \
  npx --yes hyperframes@0.8.78 render . -q high --fps 30 -o ./renders/silent.mp4
python3 <skill>/scripts/frame_audit.py renders/silent.mp4        # pixel gate: must be "0 failed"
<skill>/scripts/review_frames.sh renders/silent.mp4 snapshots 2 "11.0,13.5"

Hard rules (each one came from a rejected or broken film)

  • Floors are floors, not targets. ≥ 90 non-filler tweens, ≥ 8 mechanics, ≥ 2 non-crossfade transitions, ≥ 8 eases, ≥ 8 camera moves, ≥ 5 events in every act (15s film).
  • Show the product working in at least two acts — its interface, its output, a device running it, real-looking data. An abstract metaphor (ink, particles, light, a seed growing) with no product in it could be an ad for anything and is rejected even if every number passes.
  • Fill the frame. A line of text and one s

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars0
CategoryOther
Updated29d ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low