agentleFS
45ck45ck/marketing-product-skills/.claude/skills/event-tracking-plan/SKILL.md

event-tracking-plan

Skill3 starsChanged 8 months agoMITView on GitHub

Create or audit an event tracking plan for product, growth, and analytics workflows. Use when a team needs a source-of-truth taxonomy, instrumentation plan, and data governance rules.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to design, repair, or review a product analytics tracking plan.

    line 9
  2. Distinctive:

    If these are missing, infer a reasonable first pass and label assumptions.

    line 41
  3. Distinctive:

    Treat the tracking plan as the source of truth.

    line 45
  4. Distinctive:

    Prefer human-readable event names.

    line 46
  5. Distinctive:

    Use an object-action naming convention unless the repo already uses a different standard.

    line 47
  6. Distinctive:

    When auditing an existing taxonomy, explicitly call out:

    line 198
  7. Distinctive:

    If the product is B2B SaaS, strongly prefer including org/account properties and account-level events where relevant.

    line 208

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Event Tracking Plan

Use this skill to design, repair, or review a product analytics tracking plan.

What this skill must produce

Always produce:

  1. Tracking objective
  2. Critical event
  3. North Star tie-in
  4. Core funnel
  5. Event taxonomy
  6. Property taxonomy
  7. Identity model
  8. Client vs server instrumentation map
  9. Data quality / governance checks
  10. Implementation backlog

Inputs to gather

If available, extract:

  • Product name
  • Core user journey
  • Target conversion / activation event
  • Existing event names
  • Current analytics stack
  • User/account model
  • Main reporting questions
  • Planned experiments / funnels
  • Regions / privacy constraints
  • Existing dashboards / warehouse / CDP

If these are missing, infer a reasonable first pass and label assumptions.

Working rules

  • Treat the tracking plan as the source of truth.
  • Prefer human-readable event names.
  • Use an object-action naming convention unless the repo already uses a different standard.
  • Include event purpose, owner, source, and destination.
  • Track only data that is necessary and useful.
  • Distinguish clearly between event properties, user properties, and organization properties.
  • Explicitly mark whether each event is client-side or server-side.
  • Design for analysis and activation.

Step-by-step method

Step 1: define the business questions

List the 5-10 most important questions the team wants the data to answer.

Examples:

  • What drives activation?
  • Where do users drop in onboarding?
  • Which behaviors correlate with retention?
  • What qualifies an account as product-qualified?
  • Which experiments require new events?

Step 2: define the critical event

Choose the user action that most closely represents the core value exchange in the product.

State:

  • why this is the critical event
  • what should count as an active user
  • what should not count as active usage

Step 3: map the core funnel

Define the critical path funnel from first touch to activation / conversion.

For each stage specify:

  • stage name
  • target event
  • key failure mode
  • key diagnostic event

Step 4: design the event taxonomy

For every required event include:

  • canonical event name
  • plain-English purpose
  • when it fires
  • trigger source
  • actor
  • destinations
  • owner

Step 5: design properties

For each event list required properties with:

  • property name
  • type
  • example value
  • why it is needed
  • whether required or optional

Then separately list:

  • user properties
  • org/account properties

Step 6: define instrumentation ownership

For each event specify whether it is:

  • client-side
  • server-side
  • both
  • derived / warehouse modeled

Step 7: define governance rules

Specify:

  • naming rules
  • deprecation rules
  • duplicate event checks
  • required documentation fields
  • QA checklist
  • audit cadence

Step 8: create implementation order

Prioritize events into:

  • P0 must-have
  • P1 next
  • P2 later

Required outputs

Tracking objective

Summarize the job of this tracking plan in 2-4 sentences.

Critical event

  • Event:
  • Why it matters:
  • Active user definition:
  • Non-active noise to exclude:

North Star tie-in

Explain how the critical event and funnel relate to the team’s North Star or primary KPI.

Core funnel

StageTarget eventWhy it mattersCommon drop-off cause

Event taxonomy

Event namePurposeFires whenSourceOwnerPriority

Event properties

EventPropertyTypeExampleRequired?Why needed

User properties

PropertyTypeExampleWhy needed

Account / org properties

PropertyTypeExampleWhy needed

Identity model

State clearly:

  • anonymous ID
  • user ID
  • account / org ID
  • merge behavior
  • multi-org behavior
  • device/session considerations

Client vs server instrumentation map

EventClientServerNotes

Data quality / governance checks

  • Naming convention:
  • Required docs:
  • QA process:
  • Audit cadence:
  • Deprecation process:
  • PII guidance:
  • Common failure patterns to watch:

Implementation backlog

PriorityTaskOwnerWhy now

Additional rules

When auditing an existing taxonomy, explicitly call out:

  • duplicates
  • ambiguous names
  • events without business purpose
  • missing properties
  • events that cannot support the desired funnels or experiments
  • active-user definitions that are too shallow
  • places where account-level context is missing

If the product is B2B SaaS, strongly prefer including org/account properties and account-level events where relevant.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.