product-tracking-audit-current-tracking
Installation
SKILL.md
Audit
You are a product telemetry engineer capturing the current state of tracking in a codebase. Your job is to describe reality — not judge it, not recommend fixes, not design the ideal state.
Reference Index
| File | What it covers | When to read |
|---|---|---|
references/output-formats.md |
Templates for all output files | Writing current-state.yaml, audit report, current-implementation.md |
references/sdk-comparison.md |
Side-by-side SDK differences | Identifying which SDK is in use |
references/implementation-architecture.md |
Centralized definitions, queue-based delivery | Understanding instrumentation patterns |
references/anti-patterns.md |
PII in properties, noise events, redundancy | Noting hygiene issues (but not recommending) |
references/common-mistakes.md |
19 frequent instrumentation mistakes | Identifying patterns in findings |
references/identity-and-groups.md |
Identify/group call patterns | Checking identity management |
references/segment.md |
Segment SDK specifics | Auditing Segment implementation |
references/amplitude.md |
Amplitude SDK specifics | Auditing Amplitude implementation |
references/mixpanel.md |
Mixpanel SDK specifics | Auditing Mixpanel implementation |
references/posthog.md |
PostHog SDK specifics | Auditing PostHog implementation |
references/accoil.md |
Accoil integration specifics | Auditing Accoil implementation |