lanbow-claw-skill

End-to-end Meta (Facebook/Instagram) advertising system orchestrator covering the full ad lifecycle: strategy research, creative generation, campaign delivery, and post-campaign optimization. Use when: (1) Planning and executing a complete Meta Ads campaign from scratch (2) Running the full ads lifecycle: research → create → launch → review → optimize (3) User says "run ads", "launch campaign", "full ads system", "ads pipeline", "广告投放全流程" (4) User needs guidance on which ads skill to use for their current task (5) Coordinating between strategy, creative, delivery, and review phases This skill orchestrates 4 sub-skills: ads-strategy-researcher (insights), creative_gen (creatives), lanbow-ads (delivery), and post-campaign-review (optimization). Each can also be used independently.

## 概述（中文）

End-to-end Meta (Facebook/Instagram) advertising system orchestrator covering the full ad lifecycle:
strategy research, creative generation, campaign delivery, and post-campaign optimization.
Use when:
(1) Planning and executing a complete Meta Ads campaign from scratch
(2) Running the full ads lifecycle: research → create → launch → review → optimize
(3) User says "run ads", "launch campaign", "full ads system", "ads pipeline", "广告投放全流程"
(4) User needs guidance on which ads skill to use for their current task
(5) Coordinating between strategy, creative, delivery, and review phases
This skill orchestrates 4 sub-skills: ads-strategy-researcher (insights), creative_gen (creatives),
lanbow-ads (delivery), and post-campaign-review (optimization). Each can also be used independently.

## 原文

# Lanbow Ads Skills

End-to-end Meta Ads lifecycle management across 4 features: **Strategy → Creative → Delivery → Review**, forming a continuous optimization loop. Built by [Lanbow](https://lanbow.com/) — see the [detailed guide](https://lanbow.com/blog/lanbow-claw-skill) for more information.

## Feature Map

| #   | Feature              | Skill                     | What It Does                                                  | Key Dependency           |
| --- | -------------------- | ------------------------- | ------------------------------------------------------------- | ------------------------ |
| 1   | Strategy Research    | `ads-strategy-researcher` | Market analysis, competitive intelligence, messaging strategy | WebSearch / WebFetch     |
| 2   | Creative Generation  | `creative_gen`            | AI-generated ad images from strategy inputs                   | User's Gemini API Key    |
| 3   | Ad Delivery          | `lanbow-ads`              | Campaign creation and management via Meta Ads CLI             | User's Meta Access Token |
| 4   | Post-Campaign Review | `post-campaign-review`    | Performance diagnosis and optimization plan                   | Campaign delivery data   |

## System Decision Tree

**Starting a new campaign from scratch?**
→ Start at Feature 1 (Strategy) → Feature 2 (Creative) → Feature 3 (Delivery)

**Have strategy, need creatives?**
→ Start at Feature 2 (Creative) → Feature 3 (Delivery)

**Have creatives, need to launch?**
→ Start at Feature 3 (Delivery)

**Campaign already running, need to optimize?**
→ Start at Feature 4 (Review) → loop back to Features 1-3 as needed

**Quick ad hoc task?** (list campaigns, check performance, upload image, etc.)
→ Use Feature 3 (Delivery / lanbow-ads CLI) directly

## Full Lifecycle Loop

```
┌─────────────────────────────────────────────────────────┐
│                                                         │
│  Feature 1: Strategy Research                           │
│  ┌──────────────────────────────────┐                   │
│  │ Input: URL, objectives, audience │                   │
│  │ Output: insights report          │                   │
│  │   • key message                  │                   │
│  │   • key look                     │                   │
│  │   • ad angles + CTAs             │                   │
│  │   • audience segments            │                   │
│  └──────────┬───────────────────────┘                   │
│             │                                           │
│             ▼                                           │
│  Feature 2: Creative Generation                         │
│  ┌──────────────────────────────────┐                   │
│  │ Input: key message, key look,    │                   │
│  │        product info, audiences   │                   │
│  │ Output: ad images + prompts      │                   │
│  └──────────┬───────────────────────┘                   │
│             │                                           │
│             ▼                                           │
│  Feature 3: Ad Delivery                                 │
│  ┌──────────────────────────────────┐                   │
│  │ Input: creatives, targeting,     │                   │
│  │        budget, account           │                   │
│  │ Output: live campaign            │                   │
│  └──────────┬───────────────────────┘                   │
│             │                                           │
│             ▼                                           │
│  Feature 4: Post-Campaign Review                        │
│  ┌──────────────────────────────────┐                   │
│  │ Input: performance data          │                   │
│  │ Output: diagnosis + next actions │──── loop back ────┘
│  └──────────────────────────────────┘
```

## Feature 1: Strategy Research

**Skill:** `ads-strategy-researcher` | **Details:** [strategy-research.md](references/strategy-research.md)

Perform pre-campaign market analysis using WebSearch + WebFetch. Produces a structured strategy report.

**Trigger phrases:** "ads strategy", "marketing plan", "competitor research", "market research"

**Inputs:** product URL, business objectives, campaign context, audience info, competitors

**Key outputs that feed Feature 2:**

| Output                                  | Used By                                         |
| --------------------------------------- | ----------------------------------------------- |
| Key Message (primary promise + reasons) | `product_info` / `requirements` in creative gen |
| Key Look (visual cues, composition)     | `requirements` in creative gen                  |
| Ad Angles (hooks, CTAs)                 | `input_cta` in creative gen                     |
| Audience Segments                       | `audience_descriptions` in creative gen         |

**Strategy types:** Omni-Channel (Amazon + TikTok + Meta) or Meta-Only

## Feature 2: Creative Generation

**Skill:** `creative_gen` | **Details:** [creative-generation.md](references/creative-generation.md)

Generate ad creative images via 2-step Gemini pipeline: proposals (gemini-2.5-flash) → images (gemini-3.1-flash-image-preview).

**Trigger phrases:** "generate ad", "create ad image", "ad creative", "generate creatives"

**Requires:** `GEMINI_API_KEY` (optional env var — only needed when using this feature; not required for Features 1, 3, or 4)

**Inputs:** product info, audience descriptions, requirements, CTA, aspect ratio, optional product image

**Outputs:** `creative-proposals.json` + `ad-*.png` images + reusable prompt templates

**Connection to Feature 3:** Upload generated images via `lanbow-ads images upload`, then reference image_hash in `lanbow-ads creatives create`.

## Feature 3: Ad Delivery

**Skill:** `lanbow-ads` | **Details:** [ad-delivery.md](references/ad-delivery.md)

Execute campaign setup and management via the `lanbow-ads` CLI.

**Trigger phrases:** "create campaign", "launch ads", "upload image", "show campaigns", "投放广告"

**Requires:** Meta Access Token, App ID, Ad Account ID (declared in `requires.env`). App Secret is optional — only needed for exchanging short-lived tokens to long-lived tokens via `lanbow-ads auth exchange`.

**Credential setup (try in order):**

1. **Environment variables or platform secret fields (best):** If `META_ACCESS_TOKEN`, `META_APP_ID`, and `META_AD_ACCOUNT_ID` are already set as environment variables (or via your platform's secret/credential fields), configure the CLI automatically:
   ```bash
   lanbow-ads config set --app-id "$META_APP_ID"
   lanbow-ads auth set-token "$META_ACCESS_TOKEN"
   lanbow-ads config set --account "$META_AD_ACCOUNT_ID"
   # Only if META_APP_SECRET is set (optional — needed only for token exchange):
   [ -n "$META_APP_SECRET" ] && lanbow-ads config set --app-secret "$META_APP_SECRET"
   ```

2. **Ask the user to provide credentials directly (most common):** If env vars are not set, tell the user exactly how to get each credential from Meta's web interface. **Recommend the user use their platform's secret fields or environment variables rather than pasting credentials directly into chat.** If direct inpu