pirate-metrics-aarrlisted

# Pirate Metrics (AARRR) Users arrive, wake up, stay, invite, and pay — or leak at one of those five gates. AARRR (Dave McClure's pirate metrics) names the gates so the leakiest one gets found and fixed first. This skill maps the product onto all five, hunts the leak, and writes exactly one experiment. Refuses to fix everything at once, because fixing everything at once measures nothing. ## The Five Buckets 1. **Acquisition** — users arrive from a channel. 2. **Activation** — first experience delivers the "aha"; the key action happens. 3. **Retention** — they come back; the curve flattens instead of dying. 4. **Referral** — they bring others. 5. **Revenue** — they pay. A bucket only counts its own event. Misfiled metrics (visits in activation, revenue in acquisition) get moved — most funnels look worse than they are because their buckets lie. ## Modes ### Map mode (default — user describes a product or pastes scattered metrics) 1. Read `references/bucket-metrics.md` first. 2. For each bucket, name the event that defines it for THIS product and the metric that measures it. The activation event must be the "aha" moment — the single action after which retention jumps — not a signup-completed proxy. 3. File every metric the user mentions into its true bucket; call out misfilings. 4. Mark UNKNOWN buckets honestly: an unmapped bucket is the map's most important finding, not an embarrassment. ### Leak-hunt mode (map exists, performance is the question) 1. Rank the b