Skip to content
SkillModel-led3,248 tokens in use

analytics

Sets up and audits analytics: tracking plans, event naming, GA4 and GTM implementation, UTMs, and checks that rate metrics are calculated right.

61,709 stars on the repository MIT Licensecoreyhaines31/marketingskills · skills/analytics
npx skills add coreyhaines31/marketingskills --skill analytics
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing analytics costs

98tokens idle
3,248tokens in use
8,988tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure17/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

analytics guides an agent through tracking plans from the first question to validation. It sets core principles, event naming conventions, the essential events for a product, event properties and custom dimensions.

It also covers GA4 and Google Tag Manager implementation, a UTM parameter strategy, debugging and validation, and privacy and compliance. Rate metrics divide matching closed windows, so spend and results are compared over the same period.

What You Get

  • A tracking plan with an overview, events, custom dimensions and conversions
  • Event naming conventions and a library of essential events with properties
  • GA4 and GTM implementation guidance with debugging and validation steps
  • A UTM parameter strategy
  • Privacy and compliance considerations for tracking

Common Use Cases

  • Writing a tracking plan before launching a product
  • Auditing GA4 for missing or badly named events
  • Defining UTM rules a whole team can follow
  • Checking whether a reported conversion rate was calculated correctly

What Makes It Unique

It treats the calculation of metrics as part of the audit: rate metrics must divide matching closed windows. It stays focused on measurement setup and points to separate skills for ad platform conversions, attribution and A/B tests.

Under The Hood

The SKILL.md and three references (an event library, GA4 implementation and GTM implementation) are loaded as context. The skill ships no scripts and runs nothing. A tool table links to guides for GA4, Mixpanel, Amplitude, PostHog and Segment; using them needs your own accounts.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers