A skill that makes Claude write the brief you send to user-generated content creators before they film your product on a phone. It turns your notes into a one-screen brief sheet with one thing the videos must land, then writes two or three angles with three hooks each, every hook set out as a first frame, a first line and a few words of on-screen text. It times the body to the second, gives the creator talking points instead of a script, lists the shots the product needs and sets up light, sound and 9:16 framing with safe zones in pixels. It finishes with the #ad disclosure, the usage rights to propose, a counted deliverables table and a review of the drafts.
Inside are five reference files. One holds twelve hook patterns, each with the fact it depends on, plus timings and word budgets for 15, 30, 45 and 60 second videos. One is a phone filming kit with settings, light, sound and a setup card a creator reads on one screen. One covers the FTC Endorsement Guides, the reviews rule, platform labels, Spark and partnership ads, a usage rights menu and New York's law on AI performers, each sourced and checked on 17 October 2026. There is a review checklist and a worked example for a fictional shampoo bar brand. It never invents a claim, a result, a fee or a customer comment; it leaves a marked gap and asks.
Claude cannot watch a video or hear audio, so for the review you paste transcripts and screenshots at set moments and answer two questions about the sound. The rules file covers the US only, and it flags where a lawyer should look rather than giving legal advice; the contract, not the brief, settles rights and fees. To get the brief as a DOCX or PDF you need code execution on, and it reads links only when web search is on. You get the most from it by attaching the product photos, the label, any test results and real customer questions, and by deciding early whether creators will post or you will run the ads.
Claude skill · version 1.0
UGC creator brief
Checking your access.
In the download · 7 files
- SKILL.mdThe method Claude follows: intake, hooks, talking points and product moments, filming setup, rules and rights, then the review of drafts, one stage at a time.
- README.mdHow to install it in claude.ai or Claude Code, how to start, and the licence.
- references/worked-example.mdA full brief for a fictional shampoo bar brand: the founder's message, the brief sheet, hooks, timed body, claims list, filming notes, rights, deliverables and a review of one draft.
- references/hooks-and-structure.mdTwelve hook patterns with the fact each one needs, timings and word budgets for 15 to 60 second videos, a test plan, body structures and the default must-show product moments.
- references/phone-filming-kit.mdPhone settings for iPhone and Android, window light, sound, 9:16 framing with safe zones in pixels, file and caption specs, and a creator setup card that fits one phone screen.
- references/disclosure-and-rights.mdFTC endorsement and review rules, disclosure lines for each situation, platform labels, claims that need care, a usage rights menu, Spark and partnership ads, likeness and AI performers, sourced and checked on 17 October 2026.
Install it and begin
01Install it in Claude CodeTerminal mkdir -p ~/.claude/skillsunzip ~/Downloads/ugc-creator-brief.zip -d ~/.claude/skills/# Start it with /ugc-creator-brief. If this is your first skill, type /reload-skills once.On claude.ai there is nothing to unzip: upload the zip as it is. Every step is on Install and use a Claude skill.
02Your first message to ClaudeText Use the ugc creator brief skill. I am hiring [NUMBER] creators to film [PRODUCT] for [WHERE IT RUNS, FOR EXAMPLE OUR TIKTOK ADS] in [COUNTRY]. The videos will run from [THE CREATORS' ACCOUNTS, OURS OR BOTH]. The one thing I want viewers to get is [ONE SENTENCE]. Here is what I have: [PASTE NOTES, CLAIMS AND PROOF]. Start with the brief sheet and tell me what is missing.Attach product photos that show every word on the pack, plus any test results or approved claim wording. Real customer questions help with hooks.
Worked example
How a brief becomes creator videos you can test
- 01Write the one thing the videos must land, in one sentence with no "and".Three messages in 30 seconds means none lands, and hooks cannot be compared if each video argues something different.
- 02Decide who posts and who runs the ads before writing a word of the disclosure.A creator's own post, an ad from the brand's account and a Spark or partnership ad each need different wording, labels and rights.
- 03Write two or three angles with three hooks each: a first frame, a first line and 3 to 7 words of on-screen text.Angles differ most, so test them first; changing only the first 3 seconds between variants shows which hook did the work.
- 04Give talking points with one example line each, and allow at most two lines said word for word.A script makes a creator sound read. The two fixed lines are the disclosure and one approved claim.
- 05List the must-show moments with timings: product in frame by second 3, label to the lens for 2 seconds, the demo filmed wide and close.These are the shots an editor builds every cut around, and a missing one means a reshoot.
- 06Set the phone once: 4K at 30 fps, HDR video off, facing a window, nothing important in the bottom 35% of the frame.Light and sound cannot be rescued from a phone file, and the bottom of a Reels ad sits under the caption and the button.
- 07Put #ad on screen and say it aloud in the first 3 seconds, and send the product early enough that every line about use is true.The FTC holds the brand liable for a creator's claims and missing disclosures, and "two weeks in" needs two weeks.
- 08Review drafts by gates first, then craft, then spec, with five notes at most per video.A failed gate makes craft notes pointless, and more than five notes is a reshoot conversation.
What to do it with
- ClaudeFree tier, paid above it
A language model that writes, edits, reads long documents and runs tools, including agents that work inside a codebase.
Bad at It is agreeable by default, so it will improve a bad idea instead of telling you it is bad. Ask it to argue against you and the quality of the answer changes.
- Claude CodeSubscription
An agent that reads a whole repository, edits files, runs the tests and explains what it changed.
Bad at It is fast enough to make a large mistake quickly. Work on a branch, read the diff, and never let it push. Watch the starting mode: on Pro, Max and Team plans it opens in auto mode, which Anthropic's own list says may read a .env file and send the key in it to the API that key belongs to. Switch it off.
Why it matters
A brief written in a hurry gets back videos that open on a greeting, show the label for half a second, claim things nobody can prove and carry #ad only in the caption. Some of those cannot be fixed in the edit. This skill makes Claude start from one thing to land, write hooks that can be tested against each other, keep every claim on an approved list and put the disclosure where the FTC expects it, so round one notes are about craft instead of reshoots.
- Type
- technique
- Period
- ongoing