Skip to content

davepoon/buildwithclaude / plugins/all-skills/skills/ugc-ad-remix

ugc-ad-remix

Verified

Turn a proven UGC video ad into a shot-by-shot script for your own product. Use when the user shares a TikTok, Reels or Shorts ad (link or transcript) and wants a version for their product, asks to "remix", "rewrite" or "copy the structure of" an ad, or needs a UGC script that is ready to film. Uses the free UGCfy AI MCP when it is connected; works from pasted ad text without it.

FileKindSize
LICENSEother1.0 KB
SKILL.mdskill md3.8 KB
references/breakdown.mdmarkdown2.3 KB
references/remix-rules.mdmarkdown2.4 KB
references/script-template.mdmarkdown1.2 KB
references/ugcfy-mcp.mdmarkdown1.8 KB

references/remix-rules.md

View on GitHub
# Rebuilding the ad for the user's product

## Keep

- **The hook type.** A problem hook stays a problem hook, about the user's product's problem.
- **The segment order.** If the reference goes hook → problem → proof → offer → cta, so does the remix.
- **The transferable moves** you listed in the breakdown.
- **The pace.** Roughly the same number of shots and total length.

## Change

Every line. The remix is about the user's product, its buyer and its use case. Do not reuse the reference ad's sentences, even with the product name swapped in.

## Facts: only what you were given

Use a product fact only if it appears on the user's product page or the user told you. That includes features, materials, sizes, prices, shipping, guarantees and results.

Never carry over from the reference ad:

- its price, discount, bundle, coupon or "this week only";
- its numbers ("6 hours", "40,000 customers", "3x faster");
- its brand or product names, or its creator's name;
- its claims about what its own product does.

**When a shot needs proof you do not have**, write what the camera shows instead of a number: "Pours hot coffee, waits, sips on camera and nods" rather than "Still hot after 6 hours". If a number would make the shot much stronger, add it to the user's checklist as something to measure.

**When the user has no offer**, end with a plain call to action ("link in bio", "tap the link") instead of inventing one.

Mark every assumption in the output, for example `[assumed: ships in 2 days — confirm]`.

## Claims you never write

- Medical or health outcomes ("cures", "treats", "heals", "clinically proven" without a source from the user).
- Financial results ("make $500 a day").
- Guarantees the user did not state ("works for everyone", "or your money back").
- Comparisons that name a competitor.

## Shot rules

- 4–6 shots, each 4–15 seconds, total 15–30 seconds.
- Each shot has one job that matches its segment role.
- On-screen text is short (under eight words) and readable with sound off.
- The voiceover is something a real person would say: first person, plain words, no slogans.
- The first shot must work in the first two seconds without sound.

## Two versions

Make the two versions differ in something that is worth testing, not just wording. Good pairs: same structure with a different hook type; same hook with a different proof shot; talking-to-camera versus voiceover over product shots.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall