Canonical NotFair workflow
Quick answer
- 01What is it?
- Connect NotFair paid-ad accounts and establish reusable campaign context. Use when setting up paid media in a new workspace, connecting Google, Meta, X, or LinkedIn Ads, refreshing brand context, or preparing an agent. The value is a focused slice of paid media judgment, useful when several similar skills cover the same ground.
- 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-setupSkill 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-setup/SKILL.md completely, then follow it as the active workflow. Resolve every relative reference from that file against ../../paid-ads/paid-ads-setup/.
Supporting file: paid-ads/paid-ads-setup/SKILL.md
Paid Ads Setup
Read ../shared/operating-contract.md. Do not alter campaigns during setup.
Establish access
- Detect the requested platform on the universal NotFair MCP. Call
listConnectedPlatforms, then use the existing shared preambles for Google Ads and Meta Ads or thex_ads_andlinkedin_ads_tool surfaces. If the requested platform is missing, direct the user to connect it in NotFair and stop before claiming access. - List only accounts actually returned by the connected surface. Let the user select the intended account when more than one is available; never infer it from an account name.
- For TikTok, Amazon, and ChatGPT Ads, check the available tools before proposing a connection. If no verified connector exists, request a current export or describe the plan-only boundary.
Capture decision-quality context
Read project documents that are clearly marketing-relevant, then ask only for gaps that data cannot establish:
- product, offer, geography, and primary conversion;
- unit economics: target CPA or break-even ROAS, margin, and customer value;
- approved claims, differentiators, exclusions, and brand voice;
- monthly budget, launch constraints, seasonality, and competitors;
- landing-page URLs and analytics/tracking owner.
Use the Google and Meta audit skills to persist account-specific business context where supported. For X and LinkedIn, report the selected account and context without inventing a persistence surface. Do not overwrite an existing AGENTS.md, CLAUDE.md, or project instructions as a side effect of setup. Offer a clearly marked paid-media context file only after the user approves the exact location and content.
Finish with a gap register
Report connected platforms, selected accounts, verified conversion signals, available date range, and the smallest next action. State missing tracking, economics, claim proof, or platform access explicitly. Hand off to /notfair:paid-ads-review for a baseline, /notfair:paid-ads-launch for a new campaign, or the platform audit for a deeper diagnosis.
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-setup 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 Paid Ads skills