mardab96

Paid Ads Claude Skills — Development skill for Claude Code

Development community

A pack of 20 practical Claude Skills for paid ads operators, founders, and lean growth teams working across Google Ads, Meta Ads, landing pages, tracking, and weekly performance decisions.

How to install Paid Ads Claude Skills

This entry records only its repository, not the path inside it, so there is no exact command to give. Open mardab96/paid-ads-claude-skills and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Paid Ads Claude Skills does

A pack of 20 practical Claude Skills for paid ads operators, founders, and lean growth teams working across Google Ads, Meta Ads, landing pages, tracking, and weekly performance decisions.

Alternatives in Development

Bypass 403 — Probe a 403/401 endpoint with the most-paid bypass tricks (header injection, path encoding, method swap, WAF f 4.5k ★
L Docs Plugin — Document a Lowdefy plugin package (blocks, connections, operators, actions) 3k ★
Cashclaw — An autonomous agent that takes work, does work, gets paid, and gets better at it 973 ★

README

20 Claude Skills for Paid Ads

A pack of 20 practical Claude Skills for paid ads operators, founders, and lean growth teams working across Google Ads, Meta Ads, landing pages, tracking, and weekly performance decisions.

Every skill carries a `Decision rules` section with unit-carrying thresholds (each labeled as a starting heuristic to recalibrate per account), and every output ends with `Missing data` and `Approval gates` sections using the shared output standard. Four number-heavy jobs ship deterministic helpers in `scripts/` (anomaly baselines, experiment significance, wasted-spend ranking, search-term n-grams), so the arithmetic on long exports is computed, not eyeballed. `examples/copy-paste-prompts.md` has a ready starting prompt for all 20 skills.

This package builds on the earlier Google Ads and Meta Ads skill packs, but the job is different. Those packs are platform-specific. This one is built for the recurring cross-platform questions that usually decide whether paid traffic is working:

where the budget is leaking
whether the account has enough clean signal
whether the issue is campaign, creative, offer, landing page, tracking, or lead quality
what to change, hold, test, or escalate
what a human needs to approve before anything touches spend

Every skill is a self-contained `SKILL.md` with triggers, required inputs, analysis workflow, output format, and guardrails. They work from exports, screenshots, URLs, reports, notes, and pasted customer or sales feedback. Live platform access is optional.

What's inside

#	Skill	Folder	Purpose
1	Paid Ads Account Triage	`paid-ads-account-triage`	Find the biggest performance issue before going deep into one platform
2	Cross-Channel Budget Reallocation	`cross-channel-budget-reallocation-paid-ads`	Decide where to add, hold, reduce, or pause spend across Google and Meta
3	Campaign Structure Debt Audit	`campaign-structure-debt-audit-paid-ads`	Spot fr