Install
$ agentstack add skill-nowork-studio-notfair-plugin-paid-ads-optimize ✓ 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.
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 Optimization
Read ../shared/operating-contract.md and ../shared/measurement-framework.md. Review before changing anything.
Diagnose before cutting
Verify the conversion signal, period completeness, spend volume, attribution model, and recent account changes. Spend with no recorded conversion can indicate broken tracking or immature data; treat it as a hypothesis until the signal and volume support an intervention. Check landing-page or operational failures before blaming targeting.
Classify the bottleneck as query/audience quality, creative fatigue, delivery/rank, budget constraint, landing-page mismatch, tracking, or economics. Use Google and Meta's specialized skills for live diagnosis. For other platforms, analyze only the supplied or verified data.
Rank reversible moves
Prefer this order: exclude an irrelevant query, placement, or audience; pause the narrowest losing unit; adjust budget or bid in a measured step; then consider structural change. For a reallocation, show the current and proposed allocations, the same total budget unless the user approves an increase, and the observable hypothesis.
Do not declare a loser from a few clicks. Set a threshold appropriate to the named target CPA, conversion lag, and channel role. Preserve upper-funnel and assisted-conversion context rather than judging all campaigns on last-click CPA alone.
Approval and follow-up
Present each exact mutation with scope, current value, proposed value, currency exposure, rationale, and review date. After approval, execute only through the verified platform skill or connector, read back the result, and record the intervention's expected effect and guardrail. Revisit after the declared observation window instead of promising a generic ongoing watch.
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.