skills.rest
vibbs
vibbsCOMMUNITY
Explore all skills by this author →
GitHub

instrumentation

Define AARRR-aligned event taxonomy and tracker ID conventions for analytics instrumentation.

6|1|Updated Feb 25, 2026
Search Tags:#analytics#data collection#instrumentation#product metrics#tracking#event taxonomy
One-click install
npx skills add https://github.com/vibbs/company-os --skill instrumentation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: instrumentation
Source: https://github.com/vibbs/company-os/tree/main/.claude/skills/instrumentation
Command: npx skills add https://github.com/vibbs/company-os --skill instrumentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all product features are built with consistent, measurable analytics instrumentation, bridging the gap between product requirements and actual data collection.

Core Features & Use Cases

  • Event Taxonomy Definition: Establishes a clear, AARRR-aligned event naming convention and required properties.
  • Tracker ID Conventions: Defines standardized attributes for UI elements to ensure consistent tracking.
  • Per-Feature Planning: Maps PRD success metrics to specific events and identifies UI elements needing tracking.
  • Use Case: When building a new user onboarding flow, this Skill helps define events like onboarding.started, onboarding.step_completed, and onboarding.completed, ensuring you can measure completion rates and identify drop-off points.

Quick Start

Generate the event taxonomy and tracker ID conventions for analytics instrumentation.

Frequently Asked Questions about instrumentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize event taxonomy for product analytics?▼

Standardize event taxonomy by defining AARRR-aligned event naming conventions and required properties, ensuring consistent tracking attributes for measurable product development.

What is the best way to define tracker ID conventions for UI elements?▼

Tracker ID conventions are standardized attributes applied to UI elements to ensure consistent data collection and bridge the gap between product requirements and analytics tracking.

How do I map PRD success metrics to specific tracking events?▼

Map PRD success metrics to specific events through per-feature instrumentation planning, which identifies the exact UI elements needing tracking to measure feature performance accurately.

Can I use this approach to audit existing analytics instrumentation?▼

Yes, engineering teams can audit existing analytics setups by checking current event tracking against established AARRR metrics and standardized event naming conventions for compliance.

How do I measure user onboarding completion rates and drop-off points?▼

Measure onboarding completion rates by defining specific events like onboarding.started, onboarding.step_completed, and onboarding.completed to track user progression and identify exact drop-off points.

Related Skills

Explore More Data & Analytics Skills→
ljucaskljucask
1

pm-kpis

Generate KPI frameworks, funnel measurements, and OKRs from business goals and customer validation insights.

Community
Advanced
telum-aitelum-ai
2

posthog-integration

Integrate PostHog for event tracking, feature flags, and funnel analysis.

Official
Intermediate
imankhaimankha

ui-style-guide

Apply design tokens and component rules to React-based UI elements.

Community
Basic
tarunccettarunccet
5

event-tracking-plan

Design analytics event tracking plans with naming conventions and payload examples.

Community
Intermediate