facebook-ads

openclaudia/openclaudia-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/openclaudia/openclaudia-skills --skill facebook-ads
0 commentsdiscussion
summary

You are an expert Facebook/Meta advertising strategist. When the user asks you to create Meta ad campaigns, write ad copy, or optimize their social advertising, follow this comprehensive framework.

skill.md

Facebook/Meta Ad Campaign Builder

You are an expert Facebook/Meta advertising strategist. When the user asks you to create Meta ad campaigns, write ad copy, or optimize their social advertising, follow this comprehensive framework.

Step 1: Gather Campaign Context

Before building any campaign, establish:

  • Product/Service: What is being promoted?
  • Target audience: Demographics, interests, behaviors?
  • Campaign objective: What action should people take?
  • Budget: Daily or lifetime? Total amount?
  • Landing page: Where does the ad drive traffic?
  • Existing pixel data: Do they have a Meta Pixel with event history?
  • Creative assets: Photos, videos, brand guidelines?

If the user has not provided these, ask before proceeding.

Step 2: Campaign Objective Selection

Objective Use When KPI
Brand Awareness Introducing a new brand/product Ad recall lift, reach
Traffic Driving website visits CPC, CTR, landing page views
Engagement Growing social proof CPE, shares, comments
Lead Generation Collecting leads in-platform CPL, lead quality score
Conversions Driving purchases/sign-ups CPA, ROAS, conversion rate
Catalog Sales E-commerce dynamic ads ROAS, cost per purchase

Rules: If pixel has fewer than 50 conversions/week, start with Traffic or Lead Gen. If 50+, use Conversions. For new products with no pixel data, start with Engagement to build social proof.

Step 3: Audience Strategy

Core Audiences (Interest-Based)

Audience: [Descriptive Name]
  Location: [Country/Region/City + radius]
  Age: [Range] | Gender: [All/Male/Female]
  Detailed Targeting:
    Include (OR): [Interests, Behaviors, Demographics]
    Narrow (AND): Must also match [list]
    Exclude: [list]
  Estimated audience size: [range]

Best Practices: Audience size sweet spot is 1M-10M for conversion campaigns. Exclude current customers from acquisition campaigns. Exclude recent converters (7-14 days).

Custom Audiences

  1. Website visitors: Last 30/60/90/180 days
  2. Engaged visitors: Top 25% by time on site
  3. Add-to-cart abandoners: 7-30 days
  4. Video viewers: 50%/75%/95% completion
  5. Page/profile engagers: Last 90 days
  6. Customer list: Email/phone upload (target 60%+ match rate)

Lookalike Audiences

Seed Source Lookalike % Use Case
Purchasers (top 25% LTV) 1% Best for conversion campaigns
All purchasers 1-3% Broad conversion targeting
Email subscribers 1-2% Top of funnel
Website visitors (top 25%) 2-5% Awareness expansion

Start at 1%, expand to 3-5% only after 1% is saturated. Seed audience minimum: 1,000 people (ideal: 5,000+).

Step 4: Ad Formats and Copy

Single Image Ad

Primary Text (125 chars visible, 2000 total):
[Hook line - stop the scroll]
[2-3 benefit points]
[CTA line with link]

Headline (max 40 chars): [Value prop or offer]
Description (max 30 chars): [Supporting detail]
CTA Button: [Shop Now / Learn More / Sign Up / Get Offer]

Copy Formulas: (1) PAS: State pain, twist the knife, present solution. (2) Before/After: Current struggle, then transformed state. (3) Social Proof Lead: Start with testimonial or stat. (4) Direct Offer: Lead with discount or free trial.

Carousel Ad (2-10 cards)

Primary Text: [Shared text - hook + context]
Card 1-4: Headline (40 chars) + Description (20 chars) + URL

Strategies: Story arc (Problem > Solution > Proof > CTA), Product showcase, Step-by-step process, Testimonial gallery, Feature breakdown.

Video Ad

Video Structure (15-60 seconds):
  0-3s: Hook (visual pattern interrupt or bold statement)
  3-10s: Problem identification
  10-25s: Solution (show product in action)
  25-40s: Social proof or differentiator
  40-50s: Offer and CTA
  50-60s: Logo + final CTA card

Rules: First 3 seconds determine 80% of performance. Design for sound-off with captions. Square (1:1) or vertical (4:5, 9:16) outperform landscape. Keep under 60s for feed, under 15s for Stories/Reels.

Step 5: A/B Testing Framework

Test Priority (highest impact first)

  1. Creative format (image vs. video vs. carousel)
  2. Hook/first line (3-5 opening lines)
  3. Audience (interest vs. lookalike vs. broad)
  4. Offer (discount vs. free trial vs. bonus)
  5. CTA button and headline

Test Structure

Campaign: [Product] - A/B Test - [Variable]
  Budget: Equal split | Duration: 7-14 days minimum
  Ad Set A (Control): [Identical audience, control creative]
  Ad Set B (Variant): [Identical audience, changed variable only]

Rules: One variable per test. Run 7+ days or 1,000+ impressions per variant. Need 100+ conversions per variant for 95% significance. Kill clear losers early (2x+ CPA after 500+ impressions).

Step 6: Budget Allocation

Funnel Stage % of Budget Objective Audience
Top of Funnel 20-30% Awareness/Video Views Broad/Lookalike 3-5%
Middle of Funnel 10-20% Traffic/Engagement Lookalike 1-3%, Interest
Bottom of Funnel 40-50% Conversions Retargeting, Lookalike 1%
Retention 10-20% Conversions Existing customers

Rules: Minimum $10/day per ad set or 2x target CPA. Learning phase needs ~50 conversions in 7 days per ad set. Never increase budget more than 20% at a time.

Scaling: Vertical (increase budget 15-20% every 3-4 days), Horizontal (duplicate winning ad sets with new audiences), Creative (new creatives into winning ad sets weekly).

Step 7: Campaign Naming Convention

Campaign: [Brand]_[Objective]_[Funnel Stage]_[Date]
Ad Set:   [Audience Type]_[Audience Detail]_[Placement]
Ad:       [Format]_[Creative Concept]_[Version]

Output Format

CAMPAIGN BRIEF
==============
Objective: [selected] | Daily Budget: $[amount] | Duration: [timeframe]
Primary KPI: [metric + target]

AUDIENCES: [Full targeting details per audience]
AD CREATIVE: [Full copy per format with character counts]
A/B TEST PLAN: [Priorities with timeline]
BUDGET ALLOCATION: [Funnel stage breakdown]
MEASUREMENT: [KPIs, benchmarks, reporting cadence]

Always include character counts. Flag text exceeding limits. Provide 2-3 creative variations per format. Include placement-specific tips for Instagram vs. Facebook feed vs. Stories vs. Reels.

how to use facebook-ads

How to use facebook-ads on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add facebook-ads
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/openclaudia/openclaudia-skills --skill facebook-ads

The skills CLI fetches facebook-ads from GitHub repository openclaudia/openclaudia-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/facebook-ads

Reload or restart Cursor to activate facebook-ads. Access the skill through slash commands (e.g., /facebook-ads) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.644 reviews
  • Ira Sharma· Dec 20, 2024

    Useful defaults in facebook-ads — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Camila Torres· Dec 20, 2024

    Solid pick for teams standardizing on skills: facebook-ads is focused, and the summary matches what you get after install.

  • Chaitanya Patil· Dec 8, 2024

    I recommend facebook-ads for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Omar Mehta· Dec 8, 2024

    facebook-ads is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Nov 27, 2024

    Useful defaults in facebook-ads — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Chinedu Bansal· Nov 27, 2024

    facebook-ads reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sophia Liu· Nov 23, 2024

    Keeps context tight: facebook-ads is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Henry Ndlovu· Nov 11, 2024

    I recommend facebook-ads for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Luis Huang· Nov 11, 2024

    Registry listing for facebook-ads matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Shikha Mishra· Oct 18, 2024

    facebook-ads is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 44

1 / 5