paidads
Skill1 starsChanged 17 days agoMITView on GitHub
Full paid advertising department: builds and manages campaigns across Google, Meta (Facebook/Instagram), LinkedIn, Reddit, TikTok, Snapchat, YouTube, and programmatic — plus cross-channel retargeting, ROAS attribution and blended CAC pacing, and account audits — routed through twelve modes. Use when asked to create or optimize ad campaigns, write ad copy, plan budgets or bids, set up tracking pixels and conversion events, build retargeting funnels, or audit ad account performance. Not for organic social strategy (smm), SEO, or analytics dashboards (analytics).
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
Every invocation resolves to exactly one mode.
- Distinctive: line 55
Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.
- Distinctive: line 142
No kill criteria — a loser without a target CPA/ROAS floor runs forever.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
📣 paidads — Paid Advertising Department
One head skill for the whole paid advertising department. Channel modes share one campaign doctrine — objective before budget, audience before creative, tracking before launch, and data before opinion. Each channel mode applies the doctrine to that platform's native objects.
Modes
Every invocation resolves to exactly one mode. Match the request, then load only the matched reference:
| Mode | Trigger phrases | Behavior | Reference |
| "google ads campaign", "search ads", "performance max", "shopping" | Search/PMax/Shopping/Display on Google Ads structure | references/google.md | |
| meta | "meta ads", "facebook ads", "instagram ads", "advantage+" | Facebook/Instagram feed, stories, reels via Meta Ads Manager | references/meta.md |
| "linkedin ads", "b2b campaign", "sponsored content" | Sponsored content, lead gen forms, message ads for B2B | references/linkedin.md | |
| "reddit ads", "promoted post", "subreddit targeting" | Promoted posts in communities, anti-promo culture rules | references/reddit.md | |
| tiktok | "tiktok ads", "spark ads", "spark ads" | In-feed, Spark ads, creative-first structure | references/tiktok.md |
| snapchat | "snapchat ads", "ar lens", "snap ads" | Snap Ads, story ads, AR lenses for younger demos | references/snapchat.md |
| youtube | "youtube ads", "video campaign", "skippable in-stream" | Skippable in-stream, shorts, discovery video campaigns | references/youtube.md |
| programmatic | "programmatic", "dsp", "display at scale" | DSP-based display/video buying with brand safety | references/programmatic.md |
| retargeting | "retargeting", "remarketing", "bring back visitors" | Cross-channel remarketing from audience pools | references/retargeting.md |
| roas | "roas", "blended cac", "mer", "ad attribution", "spend pacing" | Omnichannel MER triangulation, blended CAC, in-platform haircuts, and 4-tier pacing gates | references/roas.md |
| audit | "audit the ad account", "why is CPA up", "account health check" | Structured account audit: structure → tracking → creative → budget | references/audit.md |
| extra-platforms | microsoft ads, pinterest ads, retail media, audio ads, ctv | Secondary platforms: Microsoft, Pinterest, X, Apple Search, retail, native, audio, CTV, Local Services | references/extra-platforms.md |
Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.
When to Use
- Building or restructuring a paid campaign on any major ad platform.
- Planning budgets, bids, or pacing across channels.
- Writing platform-native ad copy and creative briefs.
- Setting up conversion tracking, pixels, and events before launch.
- Building retargeting/remarketing funnels from audiences.
- Triangulating blended MER and CAC across channels or enforcing 4-tier spend pacing gates.
- Auditing an underperforming ad account or scaling a working one.
Anti-Triggers
- Organic social strategy, calendars, community →
smm. - SEO / AEO / organic search visibility →
seo. - Building the measurement layer itself (GA4, dashboards, attribution) →
analytics. - Ad copy as part of broader site copywriting →
content.
Quick Reference
Universal campaign doctrine (applies to every channel mode)
- Objective first. Name the business objective in one word (awareness/traffic/leads/sales/retention). No objective, no campaign.
- Audience before creative. Define who sees it before deciding what they see.
- Tracking before launch. Pixel installed, conversion events verified, UTM convention applied — or the campaign does not launch.
- Creative volume. 3–5 variants per ad set at launch (test messaging, not colors).
- Data before opinion. Decisions after the data window (typically 7 days or 50 conversions per variant), never before.
- Budget floor. Per-ad-set daily budget ≥ 10× target CPA, or the algorithm can't exit learning.
Intake gate
| Missing at intake | Consequence |
| Objective | Wrong campaign type and KPI |
| Target CPA/ROAS | No kill criteria for losers |
| Audience definition | Spray and pray |
| Verified tracking | Unmeasurable spend |
UTM convention (suite standard)
utm_source={platform}&utm_medium=paid&utm_campaign={campaign_slug} — derive utm_term/utm_content per variant. Apply on every ad; analytics reads this contract.
Message-to-market foundation (run before any channel mode; source: kim-barrett advertising-skills MIT — copy-chief/schwartz-awareness-mapper, copy-chief/mechanism-builder, copy-chief/headline-matrix, orchestrators/full-funnel-campaign-orchestrator)
- Diagnose awareness first. Place the audience on the 5-stage ladder (unaware → problem-aware → solution-aware → product-aware → most-aware) by asking: do they know the problem, do they know solutions exist, do they know us? Then set messaging rules (what you can say / must not say) and pick the angle type: education, agitation, comparison, or offer. Wrong stage = dead ad; match message to awareness, not product.
- Build the mechanism. Name what the audience tried before and why it failed, then define the new mechanism (what is different, why it works now) under a simple, memorable, ownable name. Believable and distinct beats generic.
- Vary headlines structurally. Generate ~25 headlines across 7 types (curiosity, specificity, proof, urgency, contrarian, mechanism, identity) — each structurally distinct, specific over vague.
- Chain the campaign in order. avatar → offer → awareness → mechanism → angles → creative → path → objection → language-kill; one consistent strategy/ads/funnel output, never a skipped step.
Platform table (verify current specs against platform docs before launch)
| Channel | Bid engine heart | Native strength | Watch out |
| Google Search | Intent capture | People already searching | Broad match burn |
| Meta | Learner | Rich targeting + formats | Learning phase resets |
| Firmographics | B2B job title/company | Expensive CPC | |
| Context/interest | High-intent communities | Anti-promotional culture | |
| TikTok | Spark + creative | Reach + engagement | Rapid creative fatigue |
| Snapchat | Reach younger demos | AR lenses | Narrower placement set |
| YouTube | Skippable/views | Awareness + consideration | Needs strong hooks |
| Programmatic | DSP reach | Scale across open web | Brand safety + fraud |
Procedure
- Intake. confirm the campaign objective (one of awareness / traffic / leads / sales / retention) — every downstream choice (channel, audience, bid, creative, KPI) is derived from it.
- Resolve the mode. Match the request against the mode table; exactly one mode. Ambiguous → ask one question, then proceed.
- Execute the mode playbook. Load
references/<mode>.mdand follow its Intake → Deliverable → Procedure → Quality gate in order. - Gate and deliver. Pass this file's Verification checklist plus the mode's quality gate, then deliver the artifact where the client expects it.
Pitfalls
- Launching before tracking is verified — unmeasurable spend; tracking gate comes first.
- Structuring by gut instead of the platform's native objects (ad sets, groups, lines).
- Editing budgets/creatives mid-learning-phase — resets the algorithm.
- One creative per ad set — nothing to learn from; 3–5 variants minimum.
- Broad match with no negatives (Google) — burning budget on irrelevant queries.
- Treating all channels the same — Reddit punishes promo-speak; LinkedIn needs firmographic copy.
- Optimizing to clicks when the objective is leads/sales — optimize to the business event.
- No kill criteria — a loser without a target CPA/ROAS floor runs forever.
Verification
- Objective named in one word before any platform object was created.
- Awareness stage diagnosed and angle type chosen before creative; mechanism named before headlines.
- Tracking verified (pixel fires, events test-fire, UTM applied) before launch.
- 3–5 creative variants per ad set, differing on message not color.
- Budget floor respected: ≥ 10× target CPA per ad set.
- Kill criteria stated upfront (target CPA/ROAS, data window).
- Findings and optimizations cite the platform metric they came from.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- accountsSkill
- analyticsSkill
- automationSkill
- brandSkill
- client-commsSkill
- contentSkill
- crmSkill
- databaseSkill
- designSkill
- devopsSkill
- growthSkill
- gtmSkill
- incident-responseSkill
- mobileSkill
- opsSkill
- qa-launchSkill
- researchSkill
- retainSkill
- sales-enablementSkill
- seoSkill
- smmSkill
- telegramSkill
- webdevSkill
- context-anchorSkill
- coupling-routerSkill
- evidence-ledgerSkill
- relaySkill
- secretarySkill
- gitSkill
- new-projectSkill
- updateagentsSkill
- updatedocsSkill
- animateSkill
- designscopeSkill
- refactorSkill
- auditSkill
- code-reviewSkill
- dead-letterSkill
- gauntlet-loopSkill
- humanizeSkill
- muse-securitySkill
- puaSkill
- clean-system-cacheSkill
- coachSkill
- periodic-retreatSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

