← ClaudeAtlas

ugc-video-adslisted

UGC-style video ads for TikTok, Instagram Reels, YouTube Shorts and Meta ads, made by Claude Code, Codex or Cursor without a video model. The agent writes 3-5 hooks and a direct-response body (problem, demo, proof, CTA) from a product page; the script voices every line in the creator's or founder's own cloned voice, renders every hook x body combination as a captioned 1080x1920 MP4 (plus 4:5, 1:1 or 16:9), keeps captions, price overlays and the end card inside the platform safe zones, trims dead air, hits -14 LUFS, measures each hook against a 3-second budget, lints risky ad claims (guarantees, health, income, personal attributes, "free"), and writes a manifest for Ads Manager naming. Lines are cached, so a new hook re-bills only that hook. Use when the user asks for a UGC ad, a TikTok/Reels/Meta video ad, product video ad, ad creative variations, creative testing, a faceless or founder-voice product ad, or "make ads from my product photos". Voice and speech recognition by Miragea; stdlib Python + ffmpeg.
yyert123/miragea-skills · ★ 0 · AI & Automation · score 78
Install: claude install-skill yyert123/miragea-skills
# UGC video ads (voice-first, no video model) Product photos, clips or screen recordings in; a matrix of ready-to-upload ad videos out. You (the agent) are the copywriter and creative strategist; the script is the editor: voice, timing, captions, safe zones, loudness, export and naming. ## When to use - "Make a TikTok / Reels / Meta ad for my product" or "UGC-style ad from these photos". - "Give me 3 hook variations of this ad to test." - "Turn this product page into a 20-second video ad in my voice." - "Export the ad in 9:16 and 4:5 for Instagram feed." ## Steps 1. Check `MIRAGEA_API_KEY` is set (never print it), `ffmpeg -version` works, and a voice is chosen: `MIRAGEA_VOICE_ID`, or `MIRAGEA_REF_URL` + `MIRAGEA_REF_TEXT`. Only a voice the user owns or may use; founder-voice ads are the honest default. 2. Gather the facts: product name, price, offer, who it is for, the one problem it solves, real proof (reviews, numbers the user can back up). Never invent a testimonial, statistic or result. 3. Write `ad.json` next to the media (see `examples/brewly.ad.json`): - `hooks`: 3-5, each under ~3 s spoken (7-8 words). Mix angles: price shock, POV, call-out ("Stop paying..."), demo-first, curiosity. Optional `overlay` (on-screen text, <= 28 chars) and `media`. - `bodies`: one or more `{id, lines}`; 2-4 lines: problem or setup -> demo -> proof/benefit. Short spoken sentences; write numbers the way they should be heard if it matters. - `cta`: one spoken li