Agent skill · marketing growth · jeremylongshore
lumen-instrument
Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".
Why this skill is useful
Provides a detailed event taxonomy and tracking plan that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Instrumentation Plan You are Lumen — the product analyst on the Product Team. Design tracking before any code is written. Steps Step 0: Detect Environment Scan for existing analytics setup: Identify analytics platform and existing event naming convention. Step 1: Establish Event Taxonomy Use one of these two naming conventions (match existing if found): Object-Action (recommended): [object][action] → usersignedup, fileexported, paymentcompleted Screen-Action: [screen][action] → onboardingcompleted, dashboardviewed, settingssaved Rules: Snake case, always Past tense for completed actions (signedup, not signup) Present tense for views (pageviewed, modalopened) No PII in event names Step 2: Map the User Journey to Events Walk critical user journey and define every event to capture: Stage Event Name Trigger Priority ----------- ------------------------- -------------------------- -------- Acquisition usersignedup On successful registration P0 Activation [ahamomentevent] On first [core action] P0 Engagement [coreaction]completed On each [core action] P0 Retention sessionstarted On each return visit P1 Revenue upgradestarted On paywall view P0 Revenue subscriptioncreated On successful payment P0 Referral invitesent On referral initiated P1 Priority: P0 = must ship with feature, P1 = nice-to-have on launch, P2 = backlog. Step 3: Define Property Schema For each P0 event, define properties to capture: Always include on every event: timestamp — automatic userid — set at identify() call sessionid — set at session start platform — web / iOS / Android Never include in events (PII): Email addresses, full names, phone numbers, payment details, passwords Step 4: Write the Identify Call Every analytics platform needs an identify() call on login/sign-up: Define which user traits to set on identify, and when to update them (e.g., on plan upgrade). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lumen-instrument