How does this skill help with engineering handoffs?

It serves as a formal contract between product and engineering teams, providing clear, unambiguous instructions on how to implement tracking, which reduces back-and-forth and prevents 'missing data' bugs.

Can this skill handle privacy concerns?

Yes, it includes a specific step to identify personally identifiable information (PII) and documents whether it should be hashed, encrypted, or excluded to maintain compliance.

Is this skill specific to any one analytics tool?

No, it is platform-agnostic and creates high-level specifications that can be applied to tools like Amplitude, Mixpanel, Segment, or custom data warehouses.

What is an instrumentation spec?

An instrumentation spec is a technical document that defines what analytics events to track, exactly when they should fire, and what metadata properties should be included to ensure accurate data analysis.

Analytics Instrumentation Spec

Name: Analytics Instrumentation Spec
Author: LuodashiV5

byLuodashiV5

•

分析と監視

Generates detailed event tracking and analytics specifications to ensure consistent and accurate data collection for product features.

The Analytics Instrumentation Spec skill bridges the gap between product requirements and engineering implementation by standardizing how event tracking is documented. It guides users through defining analytics goals, mapping specific user triggers, and establishing consistent naming conventions for events and properties. By providing a structured framework for data collection, it prevents common issues such as missing data points or inconsistent naming, ensuring that teams can derive actionable insights immediately after a feature launch.

主な機能

01PII and privacy handling documentation

02Comprehensive QA testing checklists

03Precise event trigger specifications

04Metadata and property mapping with data types

05Defined event tracking and naming conventions

061 GitHub stars

ユースケース

01Creating a technical contract between PMs and engineers for data collection

02Auditing existing tracking implementations for gaps or inconsistencies

03Defining analytics requirements before engineering a new feature

主な機能

01PII and privacy handling documentation

02Comprehensive QA testing checklists

03Precise event trigger specifications

04Metadata and property mapping with data types

05Defined event tracking and naming conventions

061 GitHub stars

ユースケース

01Creating a technical contract between PMs and engineers for data collection

02Auditing existing tracking implementations for gaps or inconsistencies

03Defining analytics requirements before engineering a new feature