Canonical NotFair workflow
Quick answer
- 01What is it?
- Discover, connect, and verify NotFair paid-ad integrations and their actual capabilities. Use when asked to connect an ad account, configure an ads MCP, check available tools, troubleshoot access, or determine whether. 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-integrationsSkill 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-integrations/SKILL.md completely, then follow it as the active workflow. Resolve every relative reference from that file against ../../paid-ads/paid-ads-integrations/.
Supporting file: paid-ads/paid-ads-integrations/SKILL.md
Paid Ads Integrations
Read ../shared/operating-contract.md. Treat tool discovery as the source of truth; product documentation describes intent, not the current session's authorization.
Verify before promising
- Inspect the available tool list. On the universal NotFair MCP, call
listConnectedPlatformsfirst. Use the Google or Meta shared preamble when that surface is requested; for X Ads and LinkedIn Ads, resolve the platform-prefixed tools and require a harmless account/setup read before claiming access. - Confirm OAuth/account access with a harmless account-list or read operation when the connector exposes one.
- Record the exact platform, selected account, accessible date range, and whether the surface is read-only or mutation-capable.
- If authorization fails, state the error and give the documented connection path. Do not retry a destructive operation or fall back to another account.
Capability map
| Platform | NotFair path | Safe response when unavailable |
|---|---|---|
| Google Ads | Universal NotFair MCP google_ads_ tools; use the Google shared preamble | Connect/re-authenticate, then use the Google skills |
| Meta Ads | Universal NotFair MCP meta_ads_ tools; use the Meta shared preamble | Connect/re-authenticate, then use the Meta skills |
| X Ads | Universal NotFair MCP x_ads_ tools; resolve ~~x-ads | Connect/re-authenticate, then use /notfair:paid-ads-x |
| LinkedIn Ads | Universal NotFair MCP linkedin_ads_ tools; resolve ~~linkedin-ads | Connect/re-authenticate, then use /notfair:paid-ads-linkedin |
| TikTok, Amazon, ChatGPT Ads | No first-party NotFair surface declared by this plugin | Request a verified connector or export; stay plan/review-only |
Never invent a router, endpoint, tool name, account ID, or platform capability. Quote prices, quotas, and platform eligibility only from current official documentation when a user asks; do not infer them from a plan or another connector.
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-integrations 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