ads

Plan, structure, and optimize paid advertising campaigns across Google, Meta, LinkedIn, and TikTok.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill ads-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ads
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/claude-code/skills/ads
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill ads-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running paid ads without a clear strategy wastes budget on wrong platforms, poor targeting, and untracked conversions. This Skill provides a complete performance marketing framework for planning, launching, and optimizing paid campaigns across major ad platforms. ## Core Features & Use Cases - Platform Selection & Campaign Structure: Choose between Google Ads, Meta, LinkedIn, Twitter/X, and TikTok based on audience and objective, with naming conventions, budget allocation, and account organization templates. - Targeting, Creative & Retargeting Guidance: Apply audience targeting strategies per platform, ad copy frameworks (PAS, BAB, social proof), creative testing hierarchies, and funnel-based retargeting windows. - Google RSA Generation with Compliance: Generate Responsive Search Ads that strictly enforce Google's limits (15 headlines ≤30 chars, 4 descriptions ≤90 chars), with negative keywords, sitelinks, callouts, and CFM-compliant rules for Brazilian medical advertising. - Use Case: A B2B SaaS team with $15k/month asks where to advertise. The Skill recommends LinkedIn and Google Ads, structures campaigns by intent theme, defines retargeting segments, and provides a pre-launch tracking checklist. ## Quick Start Ask the assistant to plan a paid advertising strategy for your product, including platform selection, budget allocation, audience targeting, and conversion tracking setup.

Frequently Asked Questions about ads

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Google Ads, Meta, and LinkedIn for my campaign?

Choose Google Ads for high-intent search traffic, Meta for demand generation with visual products, and LinkedIn for B2B targeting by job title or company. The Skill provides a platform selection guide matching your objective, audience, and price point to the right channel.

How do I structure Google Ads campaigns with many keywords?

Organize campaigns by theme or intent such as brand, competitor, features, and pain points, with tightly themed ad groups of 5-15 keywords. Use consistent naming conventions, define match type strategy, and maintain negative keyword lists at campaign and ad group levels.

What are the character limits for Google Responsive Search Ads?

Each RSA requires exactly 15 headlines of 30 characters or fewer and 4 descriptions of 90 characters or fewer, plus up to 2 path fields of 15 characters. Google also enforces a maximum of 3 RSAs per ad group, so larger requests must be grouped accordingly.

How should I set up retargeting for website visitors who didn't convert?

Segment audiences by funnel stage: blog readers get educational content, pricing page visitors get case studies and demos, and cart abandoners get urgency messaging. Apply frequency caps and duration windows per segment, and exclude existing customers and recent converters.

Why is my cost per lead high and how do I reduce it?

High CPL usually stems from landing page issues, loose targeting, weak creative, or low quality scores. Check post-click conversion rate first, then tighten audiences, test new creative angles, and adjust bid strategy after gathering at least 50 conversions.

When should I use server-side conversion tracking like Meta CAPI?

Use server-side tracking when running Meta or TikTok ads, spending over $5K monthly, or targeting tech-savvy audiences with high ad blocker usage. Send the same events from browser pixel and server with a shared event_id to avoid double-counting conversions.