📈 Core Philosophy: Standardized telemetry taxonomy drives actionable product insights.
When to use
Use this skill when defining user event schemas, instrumenting CTA interaction code, building marketing/analytics conversion loops, setting up user identity profiles, or adding behavioral tracking hooks (e.g., PostHog, Amplitude, Segment).
When not to use
Do not use this skill for internal application performance monitoring (APM), database queries logging, or server-level exception handling.
Trigger cues
- Key terms: analytics, telemetry tracking, event capture, user funnel, PostHog, Amplitude, Segment, event schema, tracking plan, conversion funnel, properties, user identifier.
- Designing behavioral logs, tracking button clicks, instrumenting onboarding funnels, or setting up identity mapping.
Routing boundary
- Primary for product telemetry, behavioral schemas, funnel analysis, and tracking plans.
- Secondary to
observability-telemetry for performance tracing and system stability.
Inputs required
- Target analytics engine/tracker (e.g., PostHog, Segment, Mixpanel)
- Tracking plan requirements (funnel actions, user properties)
- Source of truth:
references/source.md
Instructions
- Detect Stack: Inspect the workspace files to identify the project's existing telemetry and analytics libraries (e.g., PostHog, Amplitude, Google Analytics, Segment).
- Do Not Migrate: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.
- Read references/source.md to understand taxonomy formatting and event mapping.
- Establish unified tracking schemas (Object:Action structure) for key conversion milestones.
- Log high-cardinality metadata in event property blocks instead of creating duplicate events.
- Verify client-side privacy safeguards (never track raw PII like passwords or full names).
Completion gate
Before reporting completion, verify the applicable binary contracts in evals/cases.json: stable Object:Action milestones, variants in properties, no raw PII, and no unnecessary analytics-stack migration.
Output format
- Primary decision/output: Tracking plan definition, event instrumentation code snippets, and property models.
- Summary: One-paragraph overview of product behavioral telemetry.
- Actions: Verification checklist for event taxonomy, PII checks, and identity mapping accuracy.
1---2name: analytics-event-tracking3description: Trigger: PostHog event, Segment schema, event properties, user funnel track, track taxonomy. Scope: Product behavioral telemetry, user funnel event models. Boundary: Excludes system performance exceptions.4---56# 📈 Core Philosophy: Standardized telemetry taxonomy drives actionable product insights.78## When to use910Use this skill when defining user event schemas, instrumenting CTA interaction code, building marketing/analytics conversion loops, setting up user identity profiles, or adding behavioral tracking hooks (e.g., PostHog, Amplitude, Segment).1112## When not to use1314Do not use this skill for internal application performance monitoring (APM), database queries logging, or server-level exception handling.1516## Trigger cues1718- Key terms: analytics, telemetry tracking, event capture, user funnel, PostHog, Amplitude, Segment, event schema, tracking plan, conversion funnel, properties, user identifier.19- Designing behavioral logs, tracking button clicks, instrumenting onboarding funnels, or setting up identity mapping.2021## Routing boundary2223- Primary for product telemetry, behavioral schemas, funnel analysis, and tracking plans.24- Secondary to `observability-telemetry` for performance tracing and system stability.2526## Inputs required2728- Target analytics engine/tracker (e.g., PostHog, Segment, Mixpanel)29- Tracking plan requirements (funnel actions, user properties)30- Source of truth: `references/source.md`3132## Instructions33341. **Detect Stack**: Inspect the workspace files to identify the project's existing telemetry and analytics libraries (e.g., PostHog, Amplitude, Google Analytics, Segment).352. **Do Not Migrate**: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.363. Read [references/source.md](references/source.md) to understand taxonomy formatting and event mapping.374. Establish unified tracking schemas (Object:Action structure) for key conversion milestones.385. Log high-cardinality metadata in event property blocks instead of creating duplicate events.396. Verify client-side privacy safeguards (never track raw PII like passwords or full names).4041## Completion gate4243Before reporting completion, verify the applicable binary contracts in `evals/cases.json`: stable `Object:Action` milestones, variants in properties, no raw PII, and no unnecessary analytics-stack migration.4445## Output format4647- Primary decision/output: Tracking plan definition, event instrumentation code snippets, and property models.48- Summary: One-paragraph overview of product behavioral telemetry.49- Actions: Verification checklist for event taxonomy, PII checks, and identity mapping accuracy.
coreyone