← ClaudeAtlas

ads-strategylisted

Full Ad Strategy Orchestrator (Bucket A — multi-angle fan-out). Launches 5 parallel subagents to build a complete advertising strategy from a single URL — audience personas, creative concepts, funnel architecture, competitive intelligence, and budget allocation. Produces a composite Ad Readiness Score (0-100) with a unified, client-ready strategy report. Use when the user says "/ads strategy <url>", "full ad strategy", "complete advertising plan", "ad audit", "stratégie pub complète", "stratégie publicitaire", "audit publicitaire", "plan média complet", or wants every advertising dimension analyzed in one command.
agentik-os/claude-code-skills · ★ 1 · AI & Automation · score 72
Install: claude install-skill agentik-os/claude-code-skills
# Full Ad Strategy Orchestrator ## Skill Purpose Perform a comprehensive, end-to-end advertising strategy build for any business from a single URL. This is the flagship command of the AI Ads Strategist — it launches 5 parallel subagents simultaneously to analyze every dimension of ad readiness, then synthesizes all findings into a unified strategy document with a composite Ad Readiness Score (0-100). The output is a client-ready deliverable that covers audience research, creative strategy, funnel architecture, competitive positioning, and budget allocation — the kind of document an agency would charge $3,000-$10,000 to produce. ## When to Use - User runs `/ads strategy <url>` - User asks for a "full ad strategy", "complete advertising plan", or "ad audit" - User wants everything in one command without running individual ad skills separately - User needs a single deliverable covering all advertising dimensions - User is preparing to launch paid ads and wants a complete roadmap ## Input Requirements - **Required:** A business URL to analyze - **Optional:** Monthly budget, target geography, industry context, specific platforms of interest --- ## Dynamic Workflow orchestration This skill IS a Dynamic Workflow. The 5 agents are its units. Run them as a fan-out → verify → synthesize loop, not as a one-shot dump. 1. **Plan** — Phase 1 builds ONE shared context package (the plan input). Every unit reads the identical package so findings stay consistent. 2. **Parallel fan-o