launch-analytics
Installation
SKILL.md
- NO PII IN LINKS OR EVENTS. Never put emails, names, or identifiers in UTM parameters or event params. Honor the project's consent/cookie/GDPR setup; if consent gating exists, don't bypass it.
- ONE CONSISTENT SCHEME. Define the UTM convention once (lowercase, documented), and use it for every launch link across listing, outreach, and social — inconsistent tags fragment the report.
- DON'T BREAK EXISTING ANALYTICS. Detect the project's current stack first; extend it, never duplicate a
tag manager or double-fire
page_view. If GA4 isn't present, propose adding it — don't assume it. - MEASURE DURABLE OUTCOMES. Track the funnel to signup and activation, not just visits/upvotes — the launch's value is the emails and activated users it produces, not the vanity spike.
- VERIFY THE SNIPPET AGAINST CURRENT DOCS. GA4/gtag specifics change; confirm event syntax against the
current Google docs (use a docs/
find-docsskill) before pasting code, and adapt to the real stack. - NEVER FABRICATE NUMBERS. Set up the measurement; report only what the tools actually show.
- WRITE THE KIT TO DISK at
.ulpi/launch/<channel>/analytics.md(create the directory if needed) — a durable, paste-ready artifact, not advice that scrolls away.