About instrumentation
instrumentation is an analytics standards skill for teams planning or auditing event tracking. It covers naming, identity, consent, versioning, and observability, with templates for tracking plans and data contracts.
Key features
- 01Event naming and property standards
- 02Identity and cross-system mapping
- 03Consent and privacy requirements
- 04Versioning and deprecation planning
- 05Schema and volume monitoring
Use cases
- 01Plan product or marketing event tracking
- 02Audit tracking before model refreshes
- 03Coordinate data contracts across teams
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/instrumentationin Claude Code to confirm it loaded.
Details
From the project READMEAnalytics Instrumentation Standards Skill
When to Use
- Planning event tracking for product, marketing, or revenue analytics.
- Auditing existing tracking plans before model refreshes.
- Coordinating engineering, product, and RevOps on data contracts.
Framework
- Event Naming & Structure – action-oriented names, consistent casing, required properties.
- Identity Management – user/account IDs, anonymous IDs, device IDs, cross-system mapping.
- Consent & Privacy – capture consent status, honor suppression, regional storage rules.
- Versioning – change logs, backward compatibility, deprecation timelines.
- Observability – sampling dashboards, schema change alerts, volume anomaly detection.
Templates
- Tracking plan sheet (event, description, properties, source, owner, status).
- Data contract checklist (fields, types, validation rules, SLA).
- Observability runbook (metrics, thresholds, notification channels).
Tips
- Pair each event with QA instructions and sample payloads.
- Store tracking plans in version control to align with code releases.
- Review instrumentation quarterly with stakeholders.
Comments
Markdown supported