event-analytics SKILL.md skillA
event-analytics from leadmagic/gtm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leadmagic/gtm-skills/event-analytics@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leadmagic/gtm-skills
- Path
skills/analytics/event-analytics/SKILL.md- Versions recorded
- 6
- Latest version
- v1.0.1, committed Oct 1, 2026
- First version recorded
- Jun 8, 2026
- Size
- 12,217 bytes
- Repository stars
- 76
- License
- MIT
Customer event analytics across every GTM system — Intercom, Zendesk, Salesforce, HubSpot, Segment, Amplitude, Mixpanel, PostHog, and custom event pipelines. Covers event taxonomy design, tracking implementation, event-driven workflows, and unified customer views. Use when implementing event tracking, building a customer data pipeline, or designing event-driven GTM automations. Triggers on: "event analytics", "customer events", "event tracking", "product analytics", "Segment setup…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Event Analytics
## Overview
Events are the atomic unit of customer understanding. Every signup, click,
feature use, upgrade, and cancellation is an event. The mistake: tracking
events haphazardly ("track everything!") with no taxonomy, creating a data
swamp instead of a data pipeline. This skill covers event analytics across
every GTM system — how to design an event taxonomy, implement tracking, and
unify event data across your stack to build a complete customer picture.
## Authoritative Foundations
- **Segment** — Customer Data Platform (CDP) and event taxonomy
- **Amplitude** — Behavioral analytics and event design
- **Mixpanel** — Product analytics and event-based reporting
- **Intercom** — Event-driven messaging and automation
- **Avo** — Event taxonomy and governance
- **Snowplow** — Open-source event pipeline
## When to Use
Trigger phrases: "event analytics setup", "customer event tracking",
"implement Segment", "Amplitude setup for SaaS", "event taxonomy design",
"customer data pipeline", "product analytics events", "Intercom events",
"event-driven workflows"
## Step-by-Step Process
### Phase 1: Event Taxonomy Design
**The 4 event types (Segment spec):**
…Read the whole file at its exact version.
How to install
mdr add leadmagic/gtm-skills/event-analytics@sha256:9c5aa56d7f168874The line at the top of this page pins the label v1.0.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vkgqtn2lfnlkj3wp)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 8, 2026 and Oct 1, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-10-01 | ca0d2ec | 12,217 B | A | view · diff |
| v1.0.1 | 2026-09-07 | 92666c2 | 12,473 B | A | view · diff |
| v1.0.0 | 2026-09-02 | a19750a | 12,470 B | A | view · diff |
| v1.0.0 | 2026-06-10 | e030e67 | 12,464 B | A | view · diff |
| v1.0.0 | 2026-06-10 | 17b6e1f | 13,032 B | A | view · diff |
| v1.0.0 | 2026-06-08 | 07ce0cd | 13,033 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12217 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
leadmagic/gtm-skills · 76 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vkgqtn2lfnlkj3wp GET https://markdownregistry.com/api/v1/resolve?ref=leadmagic/gtm-skills/event-analytics GET https://markdownregistry.com/api/v1/blob/9c5aa56d7f1688746664601ca387373ba6377fc3a6cfc2c3aa5a20331918219d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.