Instrumenting product analytics so the data can answer questions later: the event taxonomy as its schema, naming events around the user-visible action, property design with types and enums, the identity stitching that connects anonymous to logged-in, the client-side delivery mechanics including beacons, batching, and lifecycle loss, the event plan and its governance, and the written event-record. It designs the tracking layer; it never recommends an analytics vendor and never reads the data to draw conclusions. Use when asking "event taxonomy", "event naming convention", "analytics event schema", "track event design", "property naming", "user vs account analytics", "anonymous to logged-in identity", "analytics instrumentation", "event tracking plan". Not for the experiment and its statistics (ac-online-experiments), not for the warehouse schema the events land in (ac-analytical-data-modeling), not for the privacy obligations the events create (ac-privacy-engineering).
cp -r cryptoskill/skills/exchanges/anoscranel-ac-product-analytics-instrumentation .claude/skills/clawhub install anoscranel-ac-product-analytics-instrumentationCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
read_only Phase 1 single-mode classification — multi-mode breakdown deferred to Phase 2.
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed