Canonical NotFair workflow
Quick answer
- 01What is it?
- 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. Its edge is a particular angle on paid media, giving the agent tighter constraints than a plain canonical NotFair workflow request.
- 02Inputs
- Context for paid media: your goals, audience, constraints, and any source material the skill asks for.
- 03Output
- A ready-to-use result for paid media: the analysis, copy, or recommendations the agent produces.
Add this skill
Install as a package
Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.
$ npx skills add nowork-studio/notfair-plugin --skill paid-ads-launchSkill instructions
The instruction file for this skill. The skill also includes other files you need to install to use it.
Canonical NotFair workflow
Read ../../paid-ads/paid-ads-launch/SKILL.md completely, then follow it as the active workflow. Resolve every relative reference from that file against ../../paid-ads/paid-ads-launch/.
Supporting file: paid-ads/paid-ads-launch/SKILL.md
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 all other platforms, 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.
Common questions
How do I install Canonical NotFair workflow in Cursor, Claude Code, or Codex?
Run npx skills add nowork-studio/notfair-plugin --skill paid-ads-launch in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Canonical NotFair workflow, not every skill in the repository.
Where does Canonical NotFair workflow come from and what license is it under?
Canonical NotFair workflow comes from the nowork-studio/notfair-plugin repository on GitHub. That repository has 3.4K GitHub stars. The skill is published under the MIT license.
Prefer plain text? Read the Canonical NotFair workflow guide as markdown.
Related skills
More from nowork-studio
More Growth skills
More Paid Ads skills