agentleFS
clairelily2020clairelily2020/workflow-skills/skills/b2b-motion-ad-creative/SKILL.md

b2b-motion-ad-creative

Skill1 starsChanged 3 months agoMITView on GitHub

Create high-impact but credible B2B motion ad briefs for short-form paid social, SaaS product demos, display/video ads, founder-led creative, retargeting clips, and product-led storyboards. Use when the user asks for TikTok ads, YouTube Shorts, LinkedIn video ads, Reddit ads, Meta ads, SaaS demo videos, punchy hooks, Remotion compositions, GSAP/HTML motion, or short-form B2B creative direction. Outputs platform, aspect ratio, audience, hook, visual mechanism, scene-by-scene script, CTA, muted-view check, mobile legibility check, and risk notes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use this skill for paid acquisition and short-form assets where the first seconds need attention without losing product clarity.

    line 10
  2. Distinctive:

    Use high contrast and fast cuts only when they clarify the message.

    line 41
  3. Distinctive:

    Do not use fake metrics, fake customers, or generic AI visuals.

    line 42
  4. Distinctive:

    Keep product states readable on mobile.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

B2B Motion Ad Creative

Use this skill for paid acquisition and short-form assets where the first seconds need attention without losing product clarity.

Inputs

  • Product or offer
  • Target audience
  • Pain point
  • Proof point or product state
  • Platform and aspect ratio
  • CTA

Workflow

  1. Define the ad job
    • Cold awareness, retargeting, founder POV, product demo, competitor pain, or event-specific offer.
  2. Write the hook first
    • The first frame should work as a thumbnail.
    • The viewer should understand the problem within 2 seconds.
  3. Choose one visual mechanism
    • Crush, sort, spotlight, compare, pipeline, timer, receipt, or before/after.
  4. Build scenes
    • Hook
    • Problem
    • Mechanism
    • Proof
    • CTA
  5. Keep it credible
    • Use high contrast and fast cuts only when they clarify the message.
    • Do not use fake metrics, fake customers, or generic AI visuals.
    • Keep product states readable on mobile.

Timing Rules

  • Hook: first 0.3-0.8 seconds.
  • Problem: clear by 2 seconds.
  • Product or mechanism proof: visible by 4-6 seconds.
  • CTA: final 2 seconds, or persistent in a small lockup.
  • Motion beats: 3-6 per asset.

Output Format

Platform:
Aspect ratio:
Audience:
Ad job:
Hook:
Visual mechanism:

Scene 1:
Scene 2:
Scene 3:
Scene 4:
CTA:

Muted-view check:
Mobile legibility check:
Risk notes:

Quality Gates

  • The ad works without sound.
  • One claim per scene.
  • Text fits at mobile size.
  • The first frame has a clear hook.
  • Product/process proof appears before the midpoint.

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.