ads-meta
Meta Ads deep analysis covering Facebook, Instagram, and Threads advertising in the Andromeda + GEM + Lattice era. Evaluates 50 checks across Pixel/CAPI health, creative diversity and Entity-ID clustering risk, account structure, ASC/AAC defaults for Sales/Leads/App, and audience targeting. Includes Advantage+ assessment and creative-as-targeting scoring. Use when user says Meta Ads, Facebook Ads, Instagram Ads, Threads ads, Advantage+, ASC, AAC, Andromeda, GEM, Lattice, Entity-ID clustering, creative diversity, Sales optimization, Leads optimization, App optimization, or Meta campaign.
What this skill does
# Meta Ads Deep Analysis ## Andromeda + GEM + Lattice (2026) Meta's delivery stack was rebuilt across three releases: - **Andromeda** (Oct 2025) — ad-retrieval ranking model with 10,000× more model capacity than the previous funnel ([Meta Engineering, Dec 2024](https://engineering.fb.com/2024/12/02/production-engineering/meta-andromeda-advantage-automation-next-gen-personalized-ads-retrieval-engine/)). Filters the candidate creative set before the auction layer ever sees it. - **GEM** (Generative Embedding Model, late 2025) — replaces the feature pipeline. Creative *content* embeds directly into the targeting space, which is why "creative is the new targeting" is now mechanical truth not slogan. - **Lattice** (rolled out late 2025 / early 2026) — sequence-aware optimizer on top of GEM that uses user-action sequences to rank candidate ads. Net effect: creative diversity is now the #1 performance lever. Ads with Similarity Score >60% (per [Confect's measured threshold](https://confect.io/tactics/meta-andromeda-2026)) get retrieval suppression — the algorithm clusters near-identical creatives and silently limits their delivery. **100 minor variations perform no better than 10 genuinely distinct ones.** Prioritize concept / angle / format diversity over variant volume. ### Creative-as-targeting scoring rubric When auditing a creative library against Andromeda's retrieval logic, score across these 5 axes (each 0-2, total 0-10): | Axis | 0 (Risk) | 1 (OK) | 2 (Strong) | |------|----------|--------|------------| | Concept diversity | Single core message / value prop across all assets | 2 distinct messages | 3+ distinct angles (problem-led, social proof, comparison, …) | | Format diversity | One format (e.g. all static image) | 2 formats | 3+ (image, video, carousel, collection) | | Visual diversity | One palette / one model / one composition | 2 distinct visual treatments | 3+ visually distinct treatments | | Hook diversity (video) | All hooks ≤3s look alike | 2 hook patterns | 3+ hook patterns (UGC POV, question, claim, demo, …) | | Headline diversity | All headlines paraphrase the same line | 2 headline structures | 3+ structures (number-led, question, claim, comparison) | Score 8-10 = LOW Entity-ID clustering risk. Score 4-7 = MEDIUM risk (some suppression likely). Score 0-3 = HIGH risk (significant retrieval ticket loss). ### Entity-ID Clustering Predictor (pre-launch) Before launch, predict which creatives Meta will cluster. Cluster-mates share retrieval tickets — only one wins per impression opportunity. **Predictor heuristics (apply to every pair of creatives in the launch set):** 1. **Visual fingerprint** — same product hero, same model, same backdrop, same lighting → **likely cluster**. Different products or different visual identities → likely *not* a cluster. 2. **Headline fingerprint** — same first 4 tokens → likely cluster (e.g. "Save 30% on" + "Save 30% off" + "Save 30% — limited time"). 3. **Body copy fingerprint** — same opening sentence, same CTA verb → likely cluster regardless of middle-body differences. 4. **Video hook fingerprint** — same 0-3s shot, same voiceover pattern → likely cluster even if the rest of the video diverges. 5. **Format mismatch wins** — if pair is (static + video) AND visual fingerprint differs, they are *not* clustered. Crossing format AND visual is a strong diversity signal. **Output**: produce a `creative-cluster-risk.md` deliverable that groups the launch set into predicted clusters, recommends which creative in each cluster should ship and which should be cut or rebuilt, and reports the final pre- launch diversity score (target ≥8/10). ### MAPI v25 ASC/AAC Deprecation Detector Meta Marketing API v25 deprecates the explicit Advantage Shopping Campaigns (ASC) and Advantage App Campaigns (AAC) creation paths — those campaign types are folded into standard Sales / Leads / App objectives where ASC behavior becomes the *default* configuration. Detection: - If the account uses MAPI v23 or earlier: ASC/AAC API endpoints will return deprecation warnings before the v25 cutover. Capture and flag them. - If the account uses MAPI v25+: confirm that previously-ASC campaigns have been migrated to the new objective-default model with the equivalent catalog + budget + existing-customer cap settings preserved. - If creating new campaigns: use the Sales / Leads / App objective + ASC defaults rather than the legacy ASC/AAC endpoints. ### ASC defaults for Sales / Leads / App (2026 behavior) When Sales / Leads / App objectives are selected, ASC behaviors are now the default. Audit confirms: - **Catalog connection** (Sales): product catalog linked and feed health green - **Existing customer cap** (Sales): set to 10-25% (default may be too high for high-LTV brands) - **Advantage+ Audience** (all three objectives): on by default; only override with manual interest stacks for highly restricted categories - **Advantage+ Creative** (all three): text / brightness / music enhancements on by default; if your brand-safety policy requires off, document the exception per ad set ## Process 1. Collect Meta Ads data (Ads Manager export, Events Manager screenshot, EMQ scores) 2. Read `ads/references/meta-audit.md` for full 50-check audit 3. Read `ads/references/benchmarks.md` for Meta-specific benchmarks 4. Read `ads/references/scoring-system.md` for weighted scoring 5. Evaluate all applicable checks as PASS, WARNING, or FAIL 6. Calculate Meta Ads Health Score (0-100) 7. Generate findings report with action plan ## What to Analyze ### Pixel / CAPI Health (30% weight) - Meta Pixel installed and firing on all pages - Conversions API (CAPI) active (30-40% data loss without it post-iOS 14.5) - Event deduplication configured (event_id matching, ≥90% dedup rate) - Event Match Quality (EMQ) ≥8.0 for Purchase event - All standard events configured (ViewContent, AddToCart, Purchase, Lead) - Custom conversions created for non-standard events - Aggregated Event Measurement (AEM) configured for iOS - Domain verification completed - Server-side events include customer_information parameters - Pixel fires with correct currency and value parameters ### Creative (30% weight) - ≥3 creative formats active (image, video, carousel, collection) - ≥5 creatives per ad set (Meta recommendation) - Creative fatigue detection: CTR drop >20% over 14 days = FAIL - Video creative: 15s max for Stories/Reels, 30s max for Feed - UGC/testimonial creative tested - Dynamic Creative Optimization (DCO) tested - Ad copy: headline under 40 chars, primary text under 125 chars - Creative refresh cadence: every 2-4 weeks for high-spend ### Account Structure (20% weight) - Campaign Budget Optimization (CBO) vs Ad Set Budget (ABO) intentional - Campaign consolidation: 1-3 campaigns total recommended - Learning phase health: <30% ad sets in "Learning Limited" (FAIL >50%) - Budget per ad set: ≥5x target CPA (minimum for learning phase exit) - Ad set audience overlap <30% (Audience Overlap tool) - Campaign naming conventions consistent and descriptive - Advantage+ Sales Campaigns active for e-commerce - Simplified campaign structure: 1-3 campaigns total (fewer, larger ad sets preferred) ### Audience & Targeting (20% weight) - Prospecting frequency (7-day): <3.0 (WARNING 3-5, FAIL >5) - Retargeting frequency (7-day): <8.0 (WARNING 8-12, FAIL >12) - Custom Audiences: website visitors, customer lists, engagement - Lookalike Audiences: multiple seed sizes tested (1%, 3%, 5%) - Advantage+ Audience tested vs manual targeting - Interest targeting: broad enough for algorithm optimization - Exclusions: purchasers excluded from prospecting, overlap managed - Location targeting reviewed for relevance ## Advantage+ Assessment If Advantage+ features are in use: - **Advantage+ Sales Campaigns**: catalog connected, existing customer cap set - **Advantage+ Audience**: performance vs manual audience compared - **Advantage+ Creative**:
Related 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".