analytics

Design event taxonomies, instrumentation contracts, and interpretation frameworks for product analytics systems.

Updated Jul 20, 2026

Search Tags:#analytics #metrics #instrumentation #taxonomy #experimentation #data-quality

Ready to run

npx skills add https://github.com/loveconnor/clove-skills --skill analytics-loveconnor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analytics
Source: https://github.com/loveconnor/clove-skills/tree/main/.agents/skills/analytics
Command: npx skills add https://github.com/loveconnor/clove-skills --skill analytics-loveconnor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the common failure of analytics systems that lack clear decision-making frameworks, leading to unreliable data, poor metric interpretation, and misinformed product decisions.

Core Features & Use Cases

Event Taxonomy Design: Create governed, versioned event models that survive UI changes and provide stable business insights.
Trustworthy Instrumentation: Define event contracts and identity rules to ensure data quality, privacy compliance, and accurate funnel/cohort analysis.
Decision Synthesis: Bridge the gap between raw behavioral data and actionable product strategy by defining guardrails, uncertainty, and clear interpretation boundaries.

Quick Start

Use the analytics skill to define the event model, instrumentation, analysis, guardrails, and interpretation for this product question.

Frequently Asked Questions about analytics

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

FAQPage Schema

How do I design an event taxonomy for product analytics that survives UI changes?▼

Designing a stable event taxonomy involves creating governed, versioned event models that abstract away UI specifics. This approach ensures your product analytics provide consistent business insights even as the interface evolves.

What's the best way to define instrumentation contracts for reliable user behavior tracking?▼

Defining instrumentation contracts requires establishing strict identity rules and event schemas. This ensures your user behavior tracking maintains high data quality, privacy compliance, and accurate funnel and cohort analysis.

How do I interpret product analytics data without falling into common statistical traps?▼

Interpreting product analytics requires defining clear guardrails, quantifying uncertainty, and setting interpretation boundaries. This framework bridges raw behavioral data and actionable strategy while preventing misinformed product decisions.

Can I use this approach to set up statistical guardrails for product experimentation?▼

Yes, establishing statistical guardrails is a core component of trustworthy experimentation. The system applies identity management and provenance rules to complex product environments, ensuring your experiments yield reliable, actionable results.

Why does my product analytics data quality degrade over time and how can I audit it?▼

Data quality degrades when analytics systems lack clear decision-making frameworks and versioned event models. Auditing these systems establishes event contracts and identity rules to restore reliable metric interpretation.

Do I need privacy-compliant identity rules for tracking user behavior in complex products?▼

Yes, defining identity rules is essential for privacy-compliant user behavior tracking. Establishing these rules within your instrumentation contracts ensures accurate data attribution while meeting privacy compliance requirements.