Paid ads launch
Plan and prepare a new paid-media campaign or cross-channel test before it can spend.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/paid-ads-launch. - Describe your job in plain words. Claude Code follows the skill from there.
npx degit nowork-studio/notfair-plugin/paid-ads/paid-ads-launch#main ~/.claude/skills/paid-ads-launchFor one project only, change the path to .claude/skills/paid-ads-launch.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Paid ads launch
Show the full text33 lines
| name | description | argument-hint |
|---|---|---|
| paid-ads-launch | Plan and prepare a new paid-media campaign or cross-channel test before it can spend. Use when asked to create, launch, start, set up, or allocate budget to an advertising campaign on any supported platform. | <business goal, budget, and target platform> |
Paid Ads Launch
Read ../shared/operating-contract.md and ../shared/measurement-framework.md.
Gate the launch
Do not build or recommend a spend plan until these are known: primary conversion and verification method, target CPA/ROAS or customer economics, daily and monthly budget, destination URL, geography, approved offer and claims, and the user who can approve spend. Diagnose tracking before optimizing toward it.
Choose the narrowest viable test. Search demand generally merits Google Search; visual discovery can suit Meta; B2B job/company targeting can suit LinkedIn; marketplace product demand can suit Amazon. A small budget split across several channels is usually an underpowered experiment: explain the tradeoff and set a review date if the user chooses it anyway.
Produce a preflight brief
Mark the following artifact ready_for_review:
| Field | Required content |
|---|---|
| Objective and measurement | Conversion, source of truth, attribution window, baseline, target, and review date |
| Channel and structure | Platform, campaign/ad-set or ad-group structure, audience/query intent, and exclusions |
| Budget | Currency, daily cap, implied monthly maximum, allocation, and pacing guardrail |
| Message chain | Audience motivation, approved claim source, ad concept, CTA, and matching landing URL |
| Experiment | Single primary variable, success metric, guardrail, minimum observation window, and stop condition |
| Readiness | Tracking, policy/rights, creative, access, and dependencies marked complete or blocked |
Execute only on verified surfaces
For Google Ads, hand the approved brief to /notfair:google-ads, then create paused and read it back. For Meta, use /notfair:meta-ads for supported operations and route unavailable creation steps to Ads Manager. For X, LinkedIn, Reddit, or TikTok Ads, use the matching live operator skill and create paused or disabled unless activation is explicitly approved. For Amazon and ChatGPT Ads, provide an operator-ready brief unless the current session exposes a verified NotFair connector with the needed capability. Never resume a campaign without a separate explicit approval.
| 1 | |
| 2 | name paid-ads-launch |
| 3 | description Plan and prepare a new paid-media campaign or cross-channel test before it can spend. Use when asked to create, launch, start, set up, or allocate budget to an advertising campaign on any supported platform. |
| 4 | argument-hint "<business goal, budget, and target platform>" |
| 5 | |
| 6 | |
| 7 | # Paid Ads Launch |
| 8 | |
| 9 | Read `../shared/operating-contract.md` and `../shared/measurement-framework.md`. |
| 10 | |
| 11 | ## Gate the launch |
| 12 | |
| 13 | Do not build or recommend a spend plan until these are known: primary conversion and verification method, target CPA/ROAS or customer economics, daily and monthly budget, destination URL, geography, approved offer and claims, and the user who can approve spend. Diagnose tracking before optimizing toward it. |
| 14 | |
| 15 | Choose the narrowest viable test. Search demand generally merits Google Search; visual discovery can suit Meta; B2B job/company targeting can suit LinkedIn; marketplace product demand can suit Amazon. A small budget split across several channels is usually an underpowered experiment: explain the tradeoff and set a review date if the user chooses it anyway. |
| 16 | |
| 17 | ## Produce a preflight brief |
| 18 | |
| 19 | Mark the following artifact `ready_for_review`: |
| 20 | |
| 21 | | Field | Required content | |
| 22 | |---|---| |
| 23 | | Objective and measurement | Conversion, source of truth, attribution window, baseline, target, and review date | |
| 24 | | Channel and structure | Platform, campaign/ad-set or ad-group structure, audience/query intent, and exclusions | |
| 25 | | Budget | Currency, daily cap, implied monthly maximum, allocation, and pacing guardrail | |
| 26 | | Message chain | Audience motivation, approved claim source, ad concept, CTA, and matching landing URL | |
| 27 | | Experiment | Single primary variable, success metric, guardrail, minimum observation window, and stop condition | |
| 28 | | Readiness | Tracking, policy/rights, creative, access, and dependencies marked complete or blocked | |
| 29 | |
| 30 | ## Execute only on verified surfaces |
| 31 | |
| 32 | For Google Ads, hand the approved brief to `/notfair:google-ads`, then create paused and read it back. For Meta, use `/notfair:meta-ads` for supported operations and route unavailable creation steps to Ads Manager. For X, LinkedIn, Reddit, or TikTok Ads, use the matching live operator skill and create paused or disabled unless activation is explicitly approved. For Amazon and ChatGPT Ads, provide an operator-ready brief unless the current session exposes a verified NotFair connector with the needed capability. Never resume a campaign without a separate explicit approval. |
| 33 |
Discussion
Browse more free Claude skills or everything in Product.