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
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/paid-ads-launch.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit nowork-studio/notfair-plugin/paid-ads/paid-ads-launch#main ~/.claude/skills/paid-ads-launch

For one project only, change the path to .claude/skills/paid-ads-launch.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. 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.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Paid ads launch

Show the full text33 lines
namedescriptionargument-hint
paid-ads-launchPlan 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---
2name: paid-ads-launch
3description: 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.
4argument-hint: "<business goal, budget, and target platform>"
5---
6 
7# Paid Ads Launch
8 
9Read `../shared/operating-contract.md` and `../shared/measurement-framework.md`.
10 
11## Gate the launch
12 
13Do 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 
15Choose 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 
19Mark 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 
32For 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

Alternatives

Also in Launch planningSee all 277 in Product →
AI Product Launch PlaybookLaunch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.Business & ops · MITShipping and launchPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Business & ops · MITLaunch StrategyWhen the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.Marketing · MITPacsomaticOperator toolkit for nf-core/pacsomatic matched tumor-normal workflows from BAM inputs. Use this skill when the user needs to validate run inputs, generate pacsomatic-compliant samplesheets, prepare reproducible Nextflow launch artifacts, run locally or submit to schedulers (LSF/Slurm/PBS/SGE), and triage execution failures. Triggers on requests to run pacsomatic, prepare launch commands/scripts, perform dry-run checks, or troubleshoot pipeline startup and scheduler submission errors.Science · MIT