paid-ad-copy-writer
Write paid ad copy for affiliate offers across ad platforms. Triggers on: "write ad copy", "Facebook ad for affiliate", "Google Ads copy", "TikTok ad script", "Pinterest ad", "paid traffic to affiliate", "create ad campaign", "ad headlines", "ad descriptions", "scale with paid ads", "run ads for my affiliate link", "write Facebook ad", "Google Search ad copy".
What this skill does
# Paid Ad Copy Writer
Write paid ad copy for affiliate offers — Facebook Ads, Google Search Ads, Google Display Ads, TikTok Ads, and Pinterest Ads. Each output includes multiple ad variants, targeting suggestions, compliance notes, and campaign setup guidance. Output is platform-formatted ad copy ready to deploy.
## Stage
S7: Automation — When organic content proves profitable, paid ads let you scale 10x faster. But affiliate ad copy has unique constraints: platform policies around affiliate links, FTC disclosure requirements, and the need to drive clicks to a landing page (not direct-link). This skill writes compliant, high-converting ad copy for each platform.
## When to Use
- User wants to run paid traffic to affiliate offers
- User says "write ad copy", "Facebook ad", "Google Ads", "TikTok ad"
- User wants to scale a profitable organic campaign with paid media
- User has a landing page (from S4) and wants ads driving traffic to it
- User wants multiple ad variants for testing
- Chaining from S4 (landing page) → write ads pointing to the landing page
## Input Schema
```yaml
product:
name: string # REQUIRED — product name
description: string # OPTIONAL — one-line product description
reward_value: string # OPTIONAL — commission info
url: string # OPTIONAL — product URL (for research)
key_benefits: string[] # OPTIONAL — top 3 benefits
platform: string # REQUIRED — "facebook" | "google_search" | "google_display"
# | "tiktok" | "pinterest"
audience:
description: string # REQUIRED — target audience
pain_points: string[] # OPTIONAL — problems the audience has
demographics: string # OPTIONAL — age, gender, interests
budget: string # OPTIONAL — daily/monthly budget (e.g., "$20/day")
landing_url: string # OPTIONAL — destination URL (from S4 or a bridge page)
# Note: most platforms don't allow direct affiliate links
```
**Chaining context**: If S1 product data exists, pull name, benefits, commission. If S4 landing page was created, use its URL as `landing_url`.
## Workflow
### Step 1: Analyze Product and Audience
Gather product info and audience details. If `key_benefits` is not provided, infer from product name and description using training knowledge.
Identify:
- Primary value proposition
- Emotional triggers for the audience
- Competitive angle (what makes this product different)
### Step 2: Select Ad Format
Each platform has specific formats:
**Facebook Ads**:
- Primary text (125 chars above fold, 500+ total)
- Headline (40 chars)
- Description (30 chars)
- CTA button (from predefined list)
**Google Search Ads**:
- Headlines (3 × 30 chars)
- Descriptions (2 × 90 chars)
- Sitelink extensions (4 × 25 chars + 35 char descriptions)
**Google Display Ads**:
- Short headline (30 chars)
- Long headline (90 chars)
- Description (90 chars)
- Business name
**TikTok Ads**:
- Video script (15-30 seconds)
- Hook (first 3 seconds)
- CTA overlay text
- Ad text (100 chars)
**Pinterest Ads**:
- Pin title (100 chars)
- Pin description (500 chars)
- Image text suggestions
### Step 3: Write Ad Variants
Create 3-5 variants per platform, each testing a different angle:
- **Pain Point**: Lead with the problem
- **Benefit**: Lead with the outcome
- **Social Proof**: Lead with results/numbers
- **Curiosity**: Lead with an intriguing question or statement
- **Urgency**: Lead with a time-sensitive offer (only if real)
### Step 4: Add Compliance Notes
Per platform:
- **Facebook**: "Paid Partnership" label if required. No misleading claims. Landing page must match ad claims. Affiliate links may be flagged — use a bridge/landing page.
- **Google**: Ad must match landing page content. No superlative claims without proof. Affiliate disclaimer on landing page required. Follow Google Ads affiliate policies.
- **TikTok**: #ad or Paid Partnership toggle. No medical/financial advice. Must feel native to platform.
- **Pinterest**: Disclosures in pin description. Must link to content page, not direct affiliate link.
### Step 5: Suggest Targeting
Recommend targeting parameters:
- Interest-based audiences
- Lookalike audiences (if pixel data exists)
- Keyword targeting (Google)
- Demographic filters
### Step 6: Budget Allocation
If budget is provided, suggest:
- Daily spend per variant (for A/B testing phase)
- When to kill underperformers (after 500+ impressions with <0.5% CTR)
- When to scale winners (after 3+ days of profitable ROAS)
### Step 7: Self-Validation
Before presenting output, verify:
- [ ] 3-5 ad variants generated per platform
- [ ] Character counts within platform limits (Google: 30/90 headline/description, Facebook: 40/125/27000)
- [ ] No prohibited claims (income guarantees, before/after without evidence)
- [ ] CTA uses platform-native action verbs
- [ ] Test budget recommendation is realistic ($5-20/day per variant)
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
## Output Schema
```yaml
output_schema_version: "1.0.0" # Semver — bump major on breaking changes
campaign:
product: string
platform: string
num_variants: number
landing_url: string
variants:
- label: string # "Variant A: Pain Point", etc.
angle: string # the approach used
copy:
headline: string # or headlines[] for Google
description: string # or descriptions[] for Google
primary_text: string # Facebook only
cta: string
video_script: string # TikTok only
character_counts: object # per field
compliance:
notes: string[] # platform-specific requirements
warnings: string[] # things that might get the ad rejected
targeting:
interests: string[]
demographics: string
keywords: string[] # Google only
budget_suggestion:
test_phase: string # e.g., "$10/day per variant for 5 days"
scale_phase: string # e.g., "Increase winning variant to $50/day"
kill_criteria: string # when to stop a variant
```
## Output Format
1. **Campaign Overview** — product, platform, landing URL
2. **Ad Variants** — each variant with full copy in platform format
3. **Compliance Checklist** — platform-specific requirements and warnings
4. **Targeting Suggestions** — interests, demographics, keywords
5. **Budget Guide** — test and scale strategy
## Error Handling
- **No landing URL**: "Most ad platforms don't allow direct affiliate links. I recommend creating a landing page first with S4 (landing-page-creator) and using that as your ad destination."
- **Unknown platform**: "I support Facebook, Google Search, Google Display, TikTok, and Pinterest ads. Which platform would you like ad copy for?"
- **Product with strict ad policies (supplements, finance)**: "This product category has strict advertising policies on [platform]. I'll write compliant copy, but review your ad account's specific restrictions before publishing. Avoid health/income claims."
## Examples
### Example 1: Facebook ad for SaaS product
**User**: "Write Facebook ads for HeyGen targeting content creators. My landing page is example.com/heygen-review"
**Action**: 3 variants. Variant A (pain point): "Spending hours editing videos? HeyGen creates professional AI videos in minutes." Variant B (benefit): "Create studio-quality videos without a camera. 50+ AI avatars, any language." Variant C (social proof): "10,000+ creators switched to HeyGen. Here's why." Each with headline, description, CTA. Include Facebook compliance notes.
### Example 2: Google Search ads
**User**: "Google Search ads for Semrush targeting 'best SEO tools'"
**Action**: 5 headline + 2 description combinations. H1: "Best SEO Tool for 2026" (30 chars). H2: "Try Semrush Free Today" (22 chars). H3: "Trusted by 10M+ Marketers" (25 charsRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".