Paid Ads Setup
Connect NotFair paid-ad accounts and establish reusable campaign context. Use when setting up paid media in a new workspace, connecting Google or Meta, refreshing brand context, or preparing an agent to work on ads safely.
Install
$ agentstack add skill-nowork-studio-notfair-plugin-paid-ads-setup ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-nowork-studio-notfair-plugin-paid-ads-setup) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Paid Ads Setup
Read ../shared/operating-contract.md. Do not alter campaigns during setup.
Establish access
- Detect the current NotFair Google Ads and Meta Ads MCP surfaces using their existing shared preambles. If either is missing, give the connection path from the relevant preamble 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 LinkedIn, 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. 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: nowork-studio
- Source: nowork-studio/notfair-plugin
- License: MIT
- Homepage: https://notfair.co/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.