analytics-profile-setuplisted

# Analytics profile setup ## What this skill does Produces a single file, `analytics-profile.md`, in the repo root. The file captures the handful of facts every other analytics skill needs to stop giving generic advice: - Industry and business model (B2B SaaS, B2C subscription, ecommerce, lead-gen, content/ads, marketplace) - Primary conversion event - Rough traffic volume (sets sample-size expectations) - ICP / target persona - Pricing model (what LTV and CAC even mean for them) - Data stack (which analytics tool, which events are tracked, known gaps) - Known measurement quirks (bot filters on or off, UTM conventions, cross-domain tracking) Downstream skills (`analytics-diagnostic-method`, `traffic-change-diagnosis`, `channel-and-funnel-quality`, `metric-context-and-benchmarks`) open by checking for this file. If it exists, they pull their defaults from it. If it doesn't, they fall back to generic cross-industry assumptions and prompt the user to run this skill. ## When NOT to run this - The user is asking a one-off question and doesn't want ceremony. Answer the question; don't volunteer the setup. - A profile already exists and is less than ~6 months old. Re-running overwrites useful context. Only re-run if the user explicitly asks, or the business has materially changed. ## Method Five phases. Keep it tight: the whole thing should take the user 5 minutes. ### Phase 1. Check for an existing profile ``` ls analytics-profile.md ``` If it exists: 1. Read it. 2. Sum