agentleFS
Synter-Media-AISynter-Media-AI/free-skills/skills/chatgpt-ads-launch/SKILL.md

chatgpt-ads-launch

Skill4 starsChanged 6 months agoMITView on GitHub

Build, review, and scale a ChatGPT Ads campaign from your existing Google/Meta/Microsoft text ads and website. Use when launching ChatGPT Ads, building a ChatGPT Ads campaign workbook, repurposing existing search/social ads for ChatGPT, writing context hints (not keywords), or scaling to 100+ upload-ready ads. Covers the full 9-step golden-path workflow with copy-paste prompts.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the website and old ads disagree, use the more current source or flag for review.

    line 35
  2. Distinctive:

    If the assistant cannot browse the site, paste the relevant website/landing-page copy into the chat before generating ads.

    line 36
  3. Distinctive:

    If a claim is regulated, time-sensitive, or unclear, mark it for review instead of using it freely.

    line 37
  4. Very specific:

    Run the prompts in order. The full copy-paste text for every prompt is in references/prompts.md.

    line 52
  5. Distinctive:

    Treat conversion tracking as a scale-phase next step, not a launch blocker.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ChatGPT Ads Launch & Scale

Turn existing text ads and website content into an upload-ready ChatGPT Ads campaign workbook - a clean campaign structure, distinct ad groups, conversational context hints, and at least 100 reviewed ads.

You are not just rewriting Google or Meta ads. You are building an upload-ready campaign supported by existing ads and the website, with enough creative variety to match the many ways people ask about the same need in ChatGPT and the way the relevancy algorithm looks to match.

Synter MCP (live accounts)

For live OpenAI Ads reporting and gated ops after workbook upload, complete synter-mcp-setup, then use openai-ads-operator (pull_openai_ads_performance). Hosted path: syntermedia.ai — Solo / Scale / Crucible Managed (never a Free cloud tier).

Before anything launches

This workflow drafts assets. A qualified human on the team must review every ad, context hint, URL, and image for accuracy, completeness, brand fit, policy compliance, and any required legal/commercial approval before upload. Chat-generated drafts can contain errors, miss qualifiers, or overstate claims. Passing formatting checks is not launch approval.

The main idea: build clean, launch with scale

A successful launch is both clean and scaled. Plan for at least 100 reviewed, workbook-ready ads because people describe the same need in many ways: problems, goals, tradeoffs, constraints, comparisons, occasions, budgets, and questions.

Scaling well is not hundreds of tiny rewrites. It means covering meaningfully different customer intents, each tied to the right landing page and supported by real source material.

StandardGoalMinimum bar
Golden pathA thoughtful, well-defined campaign ready to deliver≥100 reviewed, workbook-ready ads across focused ad groups and intent clusters
Quality barKeep the campaign logical, reviewed, and source-supportedDistinct creative angles, balanced ad groups, duplicate removal, workbook validation, final human review

The single hard rule: use only supported claims

Do not use a claim, offer, price, ranking, certification, guarantee, comparison, product capability, or proof point unless it is supported by the exported ads or the website/landing pages.

  • If the website and old ads disagree, use the more current source or flag for review.
  • If the assistant cannot browse the site, paste the relevant website/landing-page copy into the chat before generating ads.
  • If a claim is regulated, time-sensitive, or unclear, mark it for review instead of using it freely.

What you need before you start

Collect these inputs first - they are the source of truth for everything generated. See references/inputs-and-export.md for the full input table and platform-by-platform export guidance.

  • Exported ad files (CSV/XLSX from Google Ads, Meta, Microsoft Ads, etc.) - brand voice, existing offers/claims, landing pages.
  • Website domain + priority landing pages - maps ads to real destinations, prevents unsupported claims.
  • Approved claims and offers + brand guardrails (pulled from ads/website, can be supplemented).
  • Image assets - public square image URLs or a folder of approved, publicly hosted images.
  • Measurement setup - static UTM approach; pixel or CAPI recommended as a fast follow (see the chatgpt-ads-conversion-tracking skill).
  • Campaign Schema Template (.xlsx) from Ads Manager - required for Prompt 3.

The 9-step workflow

Run the prompts in order. The full copy-paste text for every prompt is in references/prompts.md. Before submitting prompts #1, #2, #3, and #6, fill in the dynamic fields (advertiser name, domain, landing pages, objective, target countries, claims to remove, batch number).

StepPromptOutputMove on when…
1Build approved claims listApproved / risky / unsupported claims tableUnsupported claims are removed or clearly flagged
2Build the intent mapProducts & landing pages mapped to user needsEach priority URL has clear intent clusters
3Create campaign & ad group planCampaign + ad group structure in the workbookAd groups are focused and names match the template
4Generate context hintsContext hints in the adgroups tabHints are specific, distinct, not exact-match keywords
5Create clean launch adsFirst reviewed draft ad setRows meet copy, URL, image, and claim rules
6Scale ads (2 batches of ≤50)100+ workbook-ready adsAds tab has ≥100 valid rows, ready for dedup
7Remove duplicates & scoreCleaner draft set (Keep/Fix/Remove + 1-5 scores)Weak, repetitive, or unsupported rows removed
8Validate the workbookPass/fix checklistSchema, URLs, images, names checked
9Final reviewFinal approval checklist + downloadable .xlsxA qualified reviewer approves the file

Key concepts that make this work

  • Context hints are NOT keywords. They are broad, conversational, natural-language phrases (~4-5 words) describing a real user need, topic, situation, or conversation theme. They must be a valid JSON array, e.g. ["hint one", "hint two"]. Avoid vague hints ("software", "AI"), brand-only/competitor-only hints, and minor reworded duplicates.
  • The workbook is the source of truth. Always refer to fields by header name, not column letter (templates change). Preserve tab names, headers, formatting, formulas, and validation. Populated cells must be normal (non-italic) text. The final workbook contains exactly three tabs: Campaigns, adgroups, ads - no ads_review, summary, QA, temp, or working tabs.
  • Ad copy limits: Title 16-24 chars where possible (≤24 max). Copy 32-48 chars where possible (≤48 max). Use exact landing-page URLs from the approved source list and only approved public square image links; leave image_link blank and flag if none.
  • Scale in two batches of up to 50 new ads each, distributed as evenly as possible across approved ad groups and intent clusters. No minor rewrites; no invented claims/URLs/images.

Validation & launch gate

After assembling rows, run the manual validation checklist and common-breakpoint fixes in references/validation-checklist.md. The chat can help validate, but the team must manually open every landing page and image URL in a browser, confirm character limits and JSON arrays, and confirm a qualified reviewer has signed off on accuracy, completeness, policy fit, and brand fit before upload.

After launch: add conversion tracking

Treat conversion tracking as a scale-phase next step, not a launch blocker. Launch first with clean structure, enough distinct ads, validated context hints, and approved landing pages - then add measurement. Use the chatgpt-ads-conversion-tracking skill for the Conversions API vs JavaScript Pixel decision and rollout.

Public resources

Use the latest Ads Manager template and current Help Center guidance if requirements differ from this skill: Ads in ChatGPT basics, Create Campaigns / Ad Groups / Ads for ChatGPT, Launch Campaigns, Bulk Upload Campaign Schema Checklist, Measure Results, Troubleshooting, Billing, Conversions API & JavaScript Pixel implementation guides, and OpenAI Ad Policies.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.