Ad Creative

Ad Creative

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/ad-creative from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Ad Creative 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.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Before Starting, How This Skill Works, Platform Specs, Generating Ad Visuals, Generating Ad Copy, Iterating from Performance Data.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when generating or iterating paid ad copy at scale.
• Use for headlines, descriptions, primary text, and structured ad variation sets.
• Use when performance data should inform the next round of creative.
• Use when the request clearly matches the imported source intent: 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....
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Headline generation — Focused on click-through
2. Description generation — Focused on conversion
3. Primary text generation — Focused on engagement (Meta/LinkedIn)
4. Wave 1: Core angles (3-5 angles, 5 variations each)
5. Wave 2: Extended variations on top 2 angles
6. Wave 3: Wild card angles (contrarian, emotional, specific)
7. Remove anything over character limit

Imported Workflow Notes

Imported: Batch Generation Workflow

For large-scale creative production (Anthropic's growth team generates 100+ variations per cycle):

1. Break into sub-tasks

• Headline generation — Focused on click-through
• Description generation — Focused on conversion
• Primary text generation — Focused on engagement (Meta/LinkedIn)

2. Generate in waves

• Wave 1: Core angles (3-5 angles, 5 variations each)
• Wave 2: Extended variations on top 2 angles
• Wave 3: Wild card angles (contrarian, emotional, specific)

3. Quality filter

• Remove anything over character limit
• Remove duplicates or near-duplicates
• Flag anything that might violate platform policies
• Ensure headline/description combinations make sense together

Imported: Before Starting

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):

1. Platform & Format

• What platform? (Google Ads, Meta, LinkedIn, TikTok, Twitter/X)
• What ad format? (Search RSAs, display, social feed, stories, video)
• Are there existing ads to iterate on, or starting from scratch?

2. Product & Offer

• What are you promoting? (Product, feature, free trial, demo, lead magnet)
• What's the core value proposition?
• What makes this different from competitors?

3. Audience & Intent

• Who is the target audience?
• What stage of awareness? (Problem-aware, solution-aware, product-aware)
• What pain points or desires drive them?

4. Performance Data (if iterating)

• What creative is currently running?
• Which headlines/descriptions are performing best? (CTR, conversion rate, ROAS)
• Which are underperforming?
• What angles or themes have been tested?

5. Constraints

• Brand voice guidelines or words to avoid?
• Compliance requirements? (Industry regulations, platform policies)
• Any mandatory elements? (Brand name, trademark symbols, disclaimers)

Examples

Example 1: Ask for the upstream workflow directly

Use @ad-creative to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @ad-creative against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @ad-creative for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @ad-creative using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/ad-creative, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Imported Troubleshooting Notes

Imported: Common Mistakes

• Writing headlines that only work together — RSA headlines get combined randomly
• Ignoring character limits — Platforms truncate without warning
• All variations sound the same — Vary angles, not just word choice
• No CTA headlines — RSAs need action-oriented headlines to drive clicks; include at least 2-3
• Generic descriptions — "Learn more about our solution" wastes the slot
• Iterating without data — Gut feelings are less reliable than metrics
• Testing too many things at once — Change one variable per test cycle
• Retiring creative too early — Allow 1,000+ impressions before judging

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

• generative-tools.md
• platform-specs.md
• evals.json
• generative-tools.md
• platform-specs.md

Imported Reference Notes

Imported: How This Skill Works

This skill supports two modes:

Mode 1: Generate from Scratch

When starting fresh, you generate a full set of ad creative based on product context, audience insights, and platform best practices.

Mode 2: Iterate from Performance Data

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

Imported: Platform Specs

Platforms reject or truncate creative that exceeds these limits, so verify every piece of copy fits before delivering.

Google Ads (Responsive Search Ads)

RSA rules:

• Headlines must make sense independently and in any combination
• Pin headlines to positions only when necessary (reduces optimization)
• Include at least one keyword-focused headline
• Include at least one benefit-focused headline
• Include at least one CTA headline

Meta Ads (Facebook/Instagram)

LinkedIn Ads

TikTok Ads

Twitter/X Ads

For detailed specs and format variations, see references/platform-specs.md.

Imported: Generating Ad Visuals

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:

• Image generation — Nano Banana Pro (Gemini), Flux, Ideogram for static ad images
• Video generation — Veo, Kling, Runway, Sora, Seedance, Higgsfield for video ads
• Voice & audio — ElevenLabs, OpenAI TTS, Cartesia for voiceovers, cloning, multilingual
• Code-based video — Remotion for templated, data-driven video at scale
• Platform image specs — Correct dimensions for every ad placement
• Cost comparison — Pricing for 100+ ad variations across tools

Recommended workflow for scaled production:

1. Generate hero creative with AI tools (exploratory, high-quality)
2. Build Remotion templates based on winning patterns
3. Batch produce variations with Remotion using data feeds
4. Iterate — AI for new angles, Remotion for scale

Imported: Generating Ad Copy

Step 1: Define Your Angles

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:

Step 2: Generate Variations per Angle

For each angle, generate multiple variations. Vary:

• Word choice — synonyms, active vs. passive
• Specificity — numbers vs. general claims
• Tone — direct vs. question vs. command
• Structure — short punch vs. full benefit statement

Step 3: Validate Against Specs

Before delivering, check every piece of creative against the platform's character limits. Flag anything that's over and provide a trimmed alternative.

Step 4: Organize for Upload

Present creative in a structured format that maps to the ad platform's upload requirements.

Imported: Iterating from Performance Data

When the user provides performance data, follow this process:

Step 1: Analyze Winners

Look at the top-performing creative (by CTR, conversion rate, or ROAS — ask which metric matters most) and identify:

• Winning themes — What topics or pain points appear in top performers?
• Winning structures — Questions? Statements? Commands? Numbers?
• Winning word patterns — Specific words or phrases that recur?
• Character utilization — Are top performers shorter or longer?

Step 2: Analyze Losers

Look at the worst performers and identify:

• Themes that fall flat — What angles aren't resonating?
• Common patterns in low performers — Too generic? Too long? Wrong tone?

Step 3: Generate New Variations

Create new creative that:

• Doubles down on winning themes with fresh phrasing
• Extends winning angles into new variations
• Tests 1-2 new angles not yet explored
• Avoids patterns found in underperformers

Step 4: Document the Iteration

Track what was learned and what's being tested:

#### Imported: 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]

Imported: Writing Quality Standards

Headlines That Click

Strong headlines:

• Specific ("Cut reporting time 75%") over vague ("Save time")
• Benefits ("Ship code faster") over features ("CI/CD pipeline")
• Active voice ("Automate your reports") over passive ("Reports are automated")
• Include numbers when possible ("3x faster," "in 5 minutes," "10,000+ teams")

Avoid:

• Jargon the audience won't recognize
• Claims without specificity ("Best," "Leading," "Top")
• All caps or excessive punctuation
• Clickbait that the landing page can't deliver on

Descriptions That Convert

Descriptions should complement headlines, not repeat them. Use descriptions to:

• Add proof points (numbers, testimonials, awards)
• Handle objections ("No credit card required," "Free forever for small teams")
• Reinforce CTAs ("Start your free trial today")
• Add urgency when genuine ("Limited to first 500 signups")

Imported: Output Formats

Standard Output

Organize by angle, with character counts:

#### Imported: 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)

Bulk CSV Output

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"

Iteration Report

When iterating, include a summary:

#### Imported: Performance Summary

- Analyzed: [X] headlines, [Y] descriptions
- Top performer: "[headline]" — [metric]: [value]
- Worst performer: "[headline]" — [metric]: [value]
- Pattern: [observation]

#### Imported: New Creative

[organized variations]

#### Imported: Recommendations

- [What to pause, what to scale, what to test next]

Imported: Tool Integrations

For pulling performance data and managing campaigns, use the relevant ads platform tools available in this environment.

Workflow: Pull Data, Analyze, Generate

# 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

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.