Analytics & Tracking

Build a provider-agnostic event tracking layer with a centralized taxonomy.

1|Updated Mar 11, 2026

Search Tags:#analytics #dashboards #metrics #tracking #event #provider-agnostic

Ready to run

npx skills add https://github.com/BasharAmso/Bashi --skill analytics-tracking-basharamso

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Analytics & Tracking
Source: https://github.com/BasharAmso/Bashi/tree/main/create-bashi-app/template/.claude/skills/analytics
Command: npx skills add https://github.com/BasharAmso/Bashi --skill analytics-tracking-basharamso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrument the product so every important user action is measurable and mapped to PRD success metrics, enabling data-driven decisions.

Core Features & Use Cases

Build a provider-agnostic analytics service with a centralized event taxonomy, provider wrappers, and dashboard documentation.
Use cases include onboarding analytics, core feature usage, billing events, and retention signals.

Quick Start

Describe your analytics goals and run the integration workflow to instrument events and dashboards.

Frequently Asked Questions about Analytics & Tracking

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

FAQPage Schema

How do I build a provider-agnostic analytics tracking service?▼

Build a provider-agnostic analytics tracking service by implementing a centralized event taxonomy with provider wrappers, wrapping calls in try/catch, and mapping user actions to success metrics for data-driven decisions.

What is a centralized event taxonomy for product analytics?▼

A centralized event taxonomy for product analytics is a consistent classification framework that defines every important user action, ensuring onboarding, core feature usage, and retention signals are measurable across multiple providers.

How do I instrument product events for conversion and retention dashboards?▼

Instrument product events for conversion and retention dashboards by defining analytics goals, running the integration workflow to map user actions to success metrics, and documenting the dashboards to update state and decision logs.

Can I use this analytics instrumentation approach for onboarding and billing events?▼

Yes, you can use this analytics instrumentation approach for onboarding and billing events, as the provider-agnostic tracking layer applies to core feature usage, conversion, and retention signals across multiple providers.

Does the event tracking layer handle analytics provider failures safely?▼

Yes, the event tracking layer handles analytics provider failures safely by wrapping all tracking calls in try/catch blocks, ensuring failed event logging does not disrupt the core product experience or dashboard state.