Individual skill

analytics

Use when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing. NOT charting that data (that is dashboard), NOT choosing which metrics matter (that is kpi-framework), NOT experiment math (that is ab-testing), NOT cookie-policy text (that is gdpr-privacy).

skills/analytics/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
557
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Analytics — the instrumentation layer

This skill owns the **capture** side of analytics: deciding *what to track*, *how to name it*, *where the
SDK lives in the codebase*, and *how not to leak PII or break consent law*. It produces three checkable
artifacts — an event taxonomy, tracking code (GA4 and/or PostHog), and a consent wiring. Everything
downstream of capture (charts, KPI choice, experiment stats, raw-event SQL, legal text) belongs to a
sibling; see the routing table below.

The order of work is fixed: **taxonomy → SDK wiring → consent gate → PII scrub → funnel + validation.**

## When NOT to use

| The ask | Route to |
| --- | --- |