Write ad variants that each test one idea, within platform limits and supported claims.
Instructions your experts follow when using this skill.
Use this for one campaign or ad group at a time.
Read the landing page, the offer, and what the audience is searching for or scrolling past. Choose two to four ideas to test, such as price, speed, a named pain, or proof. Each variant tests one idea, so a result can be read. Note which ideas have run before and what happened.
For each variant give the idea, the headlines, descriptions or primary text, and the call to action. Keep within the platform's character limits and show the count. Match the words on the landing page so the promise carries through. Use the customer's language, not internal product names.
For every claim list its source: the product page, a published price, a review with a link, or the owner's confirmation. Strike any claim with no source, including ratings, rankings, and results. Flag wording an ad platform is likely to reject, such as health, finance, or personal attributes, and anything about a competitor.
Do not upload, launch, or edit ads yourself; draft for approval. Never invent a testimonial, rating, statistic, or result, and never promise a return.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.