agentleFS
Infinite-Labs-AIInfinite-Labs-AI/infinite-skills/skills/paid-ads/SKILL.md

paid-ads

Skill43 starsChanged 5 months agoMITView on GitHub

Use when reviewing or planning paid acquisition across Google, Meta, LinkedIn, X, Reddit, TikTok, sponsorships, retargeting, or other paid channels.

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use andreessen, business-investment-advisor and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hussain-ElfalahSkill

    andreessen

    Also in 4 projects that use this

  • Hussain-ElfalahSkill

    business-investment-advisor

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    karpathy-coder

    Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.

    Also in 4 projects that use this

  • ai-vitaSkill

    aso-audit

    When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

    Also in 8 projects that use this

  • +8 more from Hussain-Elfalah

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 2

    Distinctive

    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
  1. Distinctive:

    Use available platform exports, screenshots, campaign structure, UTMs, landing pages, CRM data, or spend summaries.

    line 12
  2. Distinctive:

    Do not infer performance from structure alone when spend and conversion data exist.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Paid Ads

Review paid acquisition to decide what to cut, fix, test, or scale.

Required Context

Use available platform exports, screenshots, campaign structure, UTMs, landing pages, CRM data, or spend summaries. If data is missing, ask for:

  • Channel and objective.
  • Spend, conversions, revenue, CAC, CPA, ROAS, or pipeline.
  • Attribution window and conversion definition.
  • Audience and offer.
  • Creative examples.
  • Landing page.
  • Budget and time period.

Do not infer performance from structure alone when spend and conversion data exist.

Diagnose The System

Inspect:

  • Economics: target CAC/CPA, payback, LTV, gross margin, sales cycle.
  • Signal: conversion tracking quality and event meaning.
  • Structure: campaign objective, segmentation, budget allocation, bidding logic.
  • Audience: targeting, exclusions, intent, saturation.
  • Creative: message variety, proof, format fit, fatigue.
  • Landing path: match between ad promise and page.
  • Learning: what tests have been run and what changed.

Give the data a confidence grade before recommending budget moves. Weak tracking should produce repair or learn recommendations, not scale recommendations.

Classify Issues

  • Tracking issue: data cannot support decisions.
  • Offer issue: click interest does not convert.
  • Message issue: creative attracts wrong or weak intent.
  • Audience issue: targeting is too broad, too narrow, or stale.
  • Economics issue: campaign works mechanically but cannot pay back.
  • Scale issue: winner exists but budget, creative, or funnel cannot absorb more.

Output

Paid acquisition read:
[one paragraph]

Current numbers:
Spend:
Conversions:
CPA/CAC:
Revenue/ROAS:
Confidence in tracking:

Classification:
[stop / repair / learn / scale]

Diagnosis:
| Area | Finding | Evidence | Severity | Next move |

Budget moves:
- Increase:
- Hold:
- Cut:

Tests:
1. [test]
2. [test]
3. [test]

Data needed before scaling:
- [missing signal]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.