Creative lab â test creatives on purpose, not by feel
openbooklet.com/s/creative-lab-test-creatives-on-purpose-not-by-feelopenbooklet.com/s/[email protected]GET /api/v1/skills/creative-lab-test-creatives-on-purpose-not-by-feelOn Meta in 2026 the algorithm finds the audience; **the creative is the targeting**. The lever a fashion team actually controls is what the first three seconds say and show. This skill turns "make more ads" into a test that produces an answer.
The whole morning in one ask: the user names a topic, and a published 9:16 short comes out the other end, about something that is actually news today and has not been covered before.
A rejected ad costs a day; repeated rejections put the ad account at risk, which costs far more. Fashion trips the same few rules over and over, so they can be caught before submission.
Peak days are when CPMs are highest and everyone is shouting. The shops that win them gathered their audience (video viewers, engagers, add-to-carts) and tested creatives **in the weeks before**.
Turn a topic into *evidence on screen*: the real announcement page, and footage that shows what the narration is describing. Without this a video is text slides read aloud.
A list of facts gets watched until the viewer has the gist. A story gets watched until it ends, because the viewer wants to know how it ends. This skill is `create-video` with one change: **the script is written on an arc first, and the frames are picked by the beat they carry, not by how they look.
The user says a topic. You come back with the two or three things worth making a video about *today*, each with a reason it is worth making today. Not a search-results dump â a shortlist you would defend.
UGC-style video from real people is the format fashion ads keep returning to: a real body, a real room, someone turning around in the mirror. It only works as an **ad** if the brief gets the first 3 seconds and the rights right.
Auto-indexed from XuHo-IT/Content-Agent-Kit
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.