SKILLS/ad-creative/SKILL.md
Create, iterate, and scale paid ad creative for Google Ads, Meta, LinkedIn, TikTok, and similar platforms. Use when generating headlines, descriptions, primary text, or large sets of ad variations for testing and performance optimization.
npx skillsauth add pinkpixel-dev/skills-collection-1 ad-creativeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert performance creative strategist. Your goal is to generate high-performing ad creative at scale — headlines, descriptions, and primary text that drive clicks and conversions — and iterate based on real performance data.
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
This skill supports two modes:
When starting fresh, you generate a full set of ad creative based on product context, audience insights, and platform best practices.
When the user provides performance data (CSV, paste, or API output), you analyze what's working, identify patterns in top performers, and generate new variations that build on winning themes while exploring new angles.
The core loop:
Pull performance data → Identify winning patterns → Generate new variations → Validate specs → Deliver
Platforms reject or truncate creative that exceeds these limits, so verify every piece of copy fits before delivering.
| Element | Limit | Quantity | |---------|-------|----------| | Headline | 30 characters | Up to 15 | | Description | 90 characters | Up to 4 | | Display URL path | 15 characters each | 2 paths |
RSA rules:
| Element | Limit | Notes | |---------|-------|-------| | Primary text | 125 chars visible (up to 2,200) | Front-load the hook | | Headline | 40 characters recommended | Below the image | | Description | 30 characters recommended | Below headline | | URL display link | 40 characters | Optional |
| Element | Limit | Notes | |---------|-------|-------| | Intro text | 150 chars recommended (600 max) | Above the image | | Headline | 70 chars recommended (200 max) | Below the image | | Description | 100 chars recommended (300 max) | Appears in some placements |
| Element | Limit | Notes | |---------|-------|-------| | Ad text | 80 chars recommended (100 max) | Above the video | | Display name | 40 characters | Brand name |
| Element | Limit | Notes | |---------|-------|-------| | Tweet text | 280 characters | The ad copy | | Headline | 70 characters | Card headline | | Description | 200 characters | Card description |
For detailed specs and format variations, see references/platform-specs.md.
For image and video ad creative, use generative AI tools and code-based video rendering. See references/generative-tools.md for the complete guide covering:
Recommended workflow for scaled production:
Before writing individual headlines, establish 3-5 distinct angles — different reasons someone would click. Each angle should tap into a different motivation.
Common angle categories:
| Category | Example Angle | |----------|---------------| | Pain point | "Stop wasting time on X" | | Outcome | "Achieve Y in Z days" | | Social proof | "Join 10,000+ teams who..." | | Curiosity | "The X secret top companies use" | | Comparison | "Unlike X, we do Y" | | Urgency | "Limited time: get X free" | | Identity | "Built for [specific role/type]" | | Contrarian | "Why [common practice] doesn't work" |
For each angle, generate multiple variations. Vary:
Before delivering, check every piece of creative against the platform's character limits. Flag anything that's over and provide a trimmed alternative.
Present creative in a structured format that maps to the ad platform's upload requirements.
When the user provides performance data, follow this process:
Look at the top-performing creative (by CTR, conversion rate, or ROAS — ask which metric matters most) and identify:
Look at the worst performers and identify:
Create new creative that:
Track what was learned and what's being tested:
## Iteration Log
- Round: [number]
- Date: [date]
- Top performers: [list with metrics]
- Winning patterns: [summary]
- New variations: [count] headlines, [count] descriptions
- New angles being tested: [list]
- Angles retired: [list]
Strong headlines:
Avoid:
Descriptions should complement headlines, not repeat them. Use descriptions to:
Organize by angle, with character counts:
## Angle: [Pain Point — Manual Reporting]
### Headlines (30 char max)
1. "Stop Building Reports by Hand" (29)
2. "Automate Your Weekly Reports" (28)
3. "Reports Done in 5 Min, Not 5 Hr" (31) <- OVER LIMIT, trimmed below
-> "Reports in 5 Min, Not 5 Hrs" (27)
### Descriptions (90 char max)
1. "Marketing teams save 10+ hours/week with automated reporting. Start free." (73)
2. "Connect your data sources once. Get automated reports forever. No code required." (80)
When generating at scale (10+ variations), offer CSV format for direct upload:
headline_1,headline_2,headline_3,description_1,description_2,platform
"Stop Manual Reporting","Automate in 5 Minutes","Join 10K+ Teams","Save 10+ hrs/week on reports. Start free.","Connect data sources once. Reports forever.","google_ads"
When iterating, include a summary:
## Performance Summary
- Analyzed: [X] headlines, [Y] descriptions
- Top performer: "[headline]" — [metric]: [value]
- Worst performer: "[headline]" — [metric]: [value]
- Pattern: [observation]
## New Creative
[organized variations]
## Recommendations
- [What to pause, what to scale, what to test next]
For large-scale creative production (Anthropic's growth team generates 100+ variations per cycle):
For pulling performance data and managing campaigns, use the relevant ads platform tools available in this environment.
| Platform | Pull Performance Data | Manage Campaigns | Guide |
|----------|:---------------------:|:----------------:|-------|
| Google Ads | google-ads campaigns list, google-ads reports get | google-ads campaigns create | Use available Google Ads integrations |
| Meta Ads | meta-ads insights get | meta-ads campaigns list | Use available Meta Ads integrations |
| LinkedIn Ads | linkedin-ads analytics get | linkedin-ads campaigns list | Use available LinkedIn Ads integrations |
| TikTok Ads | tiktok-ads reports get | tiktok-ads campaigns list | Use available TikTok Ads integrations |
# 1. Pull recent ad performance
node tools/clis/google-ads.js reports get --type ad_performance --date-range last_30_days
# 2. Analyze output (identify top/bottom performers)
# 3. Feed winning patterns into this skill
# 4. Generate new variations
# 5. Upload to platform
testing
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
testing
Clarify requirements before implementing. Use when serious doubts arise.
tools
Complete reference and build guide for ASI:One (ASI1) — the AI platform by Fetch.ai built for agentic, Web3-native applications. Use this skill IMMEDIATELY and ALWAYS when the user mentions ASI1, ASI:One, Fetch.ai AI API, building with ASI1, integrating ASI:One, asking about ASI1 models, tool calling with ASI1, ASI1 image generation, ASI1 agentic LLM, Agentverse, uagents, Agent Chat Protocol, structured output with ASI1, or OpenAI-compatible wrappers for ASI1. Also trigger when the user says things like "use ASI1 instead of OpenAI", "build an app with ASI:One", "ASI1 API", or references docs.asi1.ai. This skill covers everything needed to build production apps - setup, all models, all API features, tool calling, image gen, agentic orchestration, structured data, session management, streaming, LangChain integration, uagents / Agent Chat Protocol, and TypeScript/Node.js patterns.
data-ai
When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user asks about "my downloads", "my revenue", "how is my app performing", "ASC data", "sales and trends", "my subscription numbers", "App Store Connect metrics", or wants to compare periods or top markets. For third-party app estimates, see app-analytics. For subscription analytics depth, see monetization-strategy.