CtrlK
BlogDocsLog inGet started
Tessl Logo

paid-ads-optimize

Diagnose wasted paid-ad spend, pacing, and allocation, then propose safe evidence-backed optimizations. Use for waste, negatives, budgets, bid changes, poor CPA or ROAS, underpacing, overspend, or scaling decisions.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 the specialized Google, Meta, X, LinkedIn, Reddit, or TikTok skill 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.

Repository
nowork-studio/notfair-plugin
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.