← ClaudeAtlas

meta_ads_analyserlisted

Analyze extracted Meta ad creatives and generate a professional competitive strategy report with inline videos/images grouped by funnel and landing page. Use when user says "/meta_ads_analyser", "analyze ads", "analyse les pubs", "rapport de stratégie pub", "ad strategy report", "review competitor creatives", "analyse créatives concurrentes", or "audit pub Meta". Run /meta_ads_extractor first to extract assets. For the full extraction + analysis pipeline in one command, see /ads_analyst.
agentik-os/claude-code-skills · ★ 1 · AI & Automation · score 72
Install: claude install-skill agentik-os/claude-code-skills
# Meta Ads Analyser Generate a professional ad strategy analysis report from extracted Meta ad creatives. > **Portability note:** Examples assume the OmegaOS VPS (`~/clawd/output/meta-ads/...`, > `sips` on macOS, Telegram delivery). On other hosts: substitute your own asset/output > directory, use `ffprobe`/`identify` (ImageMagick) instead of macOS-only `sips`, and > deliver the zip via whatever channel is available. The analysis logic is unchanged. ## Dynamic Workflow orchestration (Bucket A — fan-out) This is multi-angle competitive analysis. Decompose into independent units, fan out, adversarially verify, then synthesize one coherent report. 1. **Plan** — inventory the assets folder. Enumerate units: N ad creatives, M landing pages. Build the work list before analyzing anything (R-RUBRIC: criteria up front). 2. **Parallel fan-out** — analyze file-disjoint units concurrently (each creative and each landing page is independent): per-creative analysis (hook/script/emotion/CTA/gaps), per-landing-page analysis (headline/strategy/conversion flow), funnel mapping. One Workflow lane per unit; never two lanes writing the same file (R-SCOPE). 3. **Adversarial verify (2-of-3)** — before a claim enters the report, falsify it across 3 independent lenses: (a) does the asset actually show this hook/emotion (re-watch the exact frame / re-read the exact line)? (b) is the funnel mapping supported by the real destination URL, not assumed? (c) is the strategy pattern