SkillAgentSearch skills...

scenario-video-ads

Use when producing a video ad with Scenario from a product shot or brand assets: a mobile 9:16 or landscape 16:9 commercial, a TikTok, Reels, Shorts, YouTube, or CTV spot, or campaign creative needing a creative brief, storyboard, cinematic camera work, brand-faithful product footage, music and voic…

Install / Use

npx skills add scenario-labs/skills --skill scenario-video-ads

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Category

Marketing

Supported Platforms

Universal

Our assessment of scenario-video-ads

scenario-video-ads scores 82/100 on our quality scale, 567th of 642 Marketing skills we index.

Its SKILL.md is 6.9 KB long, split into 5 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
11/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 29 days ago, so scenario-video-ads is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. 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-09. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-video-ads compared with similar skills

All 4 of these similar skills score higher than scenario-video-ads; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-video-ads (this skill)by scenario-labs821.0k29d agoSKILL.md
LocalAIby mudler10050.4ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install scenario-video-ads?
Run npx skills add scenario-labs/skills --skill scenario-video-ads. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-video-ads work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scenario-video-ads 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 is MIT-licensed and scores 100/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 scenario-video-ads still maintained?
The repository was last updated 29 days ago, so scenario-video-ads is actively maintained.

name: scenario-video-ads description: "Use when producing a video ad with Scenario from a product shot or brand assets: a mobile 9:16 or landscape 16:9 commercial, a TikTok, Reels, Shorts, YouTube, or CTV spot, or campaign creative needing a creative brief, storyboard, cinematic camera work, brand-faithful product footage, music and voiceover, captions, ad variants, budget planning, or platform delivery specs. Keywords: video ad, commercial, product video, advert, hook, CTA, end card, campaign, ad creative." license: MIT

Scenario Video Ads

Overview

For ordered independent edits of an existing clip, use scenario-ad-variants; this skill starts new creative.

This skill is the director layer: it turns one product shot and a brief into a finished ad, delegating mechanics to the sibling skills it names per stage. Connection and the core loop: see the scenario skill in this repo. If a sibling skill named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag the gap. The full sibling map and how to load a missing one: references/dependencies.md.

Two rules bind every stage, because they carry the ad's credibility. The product is never generated: every product shot starts from the uploaded photo, as a first frame or composited into an approved still. Text is never generated: logos, taglines, prices, and legal lines are overlaid in assembly on text-free plates.

Ask the brief once, then run without stopping. The one approval that matters sits between the priced storyboard and generation: video is the expensive stage, so the user signs off on the budget table first. The concept page and the stills are cheaper checkpoints: show them when someone can answer. In a run where nobody can, continue: the brief's spend ceiling stands in for the sign-off, so generate video only while the priced board fits it, and the fidelity gate stands in for still approval.

Quick reference

| Stage | What happens | Detail | | ---------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | 1. Brief | One objective, audience, proposition, creativity and length dials, platforms, mandatories, spend ceiling | references/brief.md | | 2. Concept | One page, anchored to a named famous-ad pattern, shown to the user | references/storyboard.md | | 3. Storyboard | Beats and panels per the objective's rulebook, priced shot by shot with dry_run, approved | storyboard.md, brief.md | | 4. Stills | Composed natively per delivery ratio, product composited from the real photo, approved before animating | scenario-image, scenario-consistency | | 5. Animate | Image-to-video per approved still, one camera move, generateAudio: false where the schema has it, wait=false | scenario-video, scenario-seedance | | 6. Fidelity gate | Extract frames from every product or character clip, spot-the-difference against the approved reference | storyboard.md, scenario-asset-analysis | | 7. Audio | Music generated on the cut's beat grid, voiceover to a word budget, sonic logo | scenario-audio, references/delivery.md | | 8. Assemble | Timeline, text cards from scenario-text-overlay as image layers, captions in safe zones | scenario-video-assembly, delivery.md | | 9. Pre-flight | Policy, flashes, sound-off pass, loudness, spend report | delivery.md |

Worked example: a perfume ad, 9:16, 20 seconds

  1. Brief once: awareness, twist creativity, 20s for Reels and TikTok, ceiling in CU. Upload the product shot, then build the fidelity checklist from it with asset_analyze, instructing it to inventory label text, cap geometry, and glass tint: every later check reuses it (asset_describe returns a style line, not this inventory).
  2. Concept names its anchor: open inside the gala-and-gown cliche, break it on beat three. Show the page to the user.
  3. Storyboard 7 panels at 2 to 4 seconds each, hero shot designed first, 3 hook variants, 2 inserts as cut cover. dry_run every planned run, multiply by retry floors, present the budget table.
  4. Stills at 9:16: composite the real bottle into styled plates with an image-edit model, baseline-plus-delta prompts. Each still is approved before animating, by the user or by the fidelity checklist when nobody can answer: image money is cheap, video money is not.
  5. Animate each approved still: model_schema_get first, prompt movement first ("slow push-in over 4 seconds, the bottle rests fixed in place"), generateAudio: false when the schema lists it.
  6. Gate every clip: frame-extract, then one asset_analyze call against the checklist. Label drift fails the clip; regenerate from the same still, never from the drifted output.
  7. Music at a stated BPM so cuts land on bars; compose the timeline, scenario-text-overlay renders the tagline card into the safe zone; caption the master.
  8. Pre-flight per delivery.md, then report spend from usage against the approved board.

Common mistakes

  • Reaching for local ffmpeg or a desktop editor for the cut: assembly is model_run on Scenario tool models (see scenario-video-assembly).
  • Letting the video model render a label, logo, tagline, or price: generated type drifts frame to frame; composite text in post.
  • One long clip at the schema's maximum duration: generate 3 to 5 second product shots and 5 to 10 second coverage, then cut to rhythm in assembly.
  • Judging fidelity by watching a clip once: drift hides between glances; run the frame-extract gate.
  • Leaving the schema's audio toggle (generateAudio, where offered) at its default: the soundtrack is built in assembly, so clips with baked-in audio fight the bed.
  • Cropping a 16:9 master to 9:16: each ratio is its own composition, decided at the storyboard.
  • Two objectives in one brief: brand and performance in the same asset serves neither; make two cuts from one board instead.
  • Shipping without the pre-flight: a sensual perfume cut or a wrong-length CTV file dies in ad review, not in generation.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryMarketing
Updated29d ago
Forks129

Languages

Python

Trust signals

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

No cautions
scenario-video-ads — Universal Skill: Install & Safety Check | SkillAgent