create-telemetry

Define analytics events, success metrics, and telemetry requirements for features.

5|Updated Jul 25, 2025

Search Tags:#analytics #metrics #instrumentation #telemetry #funnel #event-taxonomy

Ready to run

npx skills add https://github.com/tomzx/agents --skill create-telemetry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-telemetry
Source: https://github.com/tomzx/agents/tree/main/skills/create-telemetry
Command: npx skills add https://github.com/tomzx/agents --skill create-telemetry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines how to measure feature usage by identifying analytics events, success metrics, funnel steps, and telemetry requirements before implementation begins.

Core Features & Use Cases

Identify the user flows and system interactions to instrument.
Define event taxonomy, success metrics, funnels, and counter metrics to guide instrumentation decisions.
Produce a concrete telemetry plan document that engineers can implement.

Quick Start

Create a telemetry plan by listing events, success metrics, and instrumentation requirements, then save it to .sdlc/features/FEAT-NNNN-<slug>/telemetry.md.

Frequently Asked Questions about create-telemetry

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

FAQPage Schema

How do I define a telemetry plan for a new feature before implementation?▼

To define a telemetry plan, identify user flows and system interactions, then document analytics events, success metrics, funnel steps, and counter metrics into a formal telemetry plan document for engineers to implement.

What is event taxonomy and when do I need it for analytics instrumentation?▼

Event taxonomy is the structured classification of analytics events and their properties. You need it during feature scoping and design to ensure consistent measurement of adoption, usage, and reliability scenarios across web and mobile experiences.

How do I set up success metrics and funnel steps for feature usage tracking?▼

Set up success metrics and funnel steps by mapping user flows and system interactions, identifying key conversion points, and defining counter metrics to guide instrumentation decisions before implementation begins.

Can I use this telemetry instrumentation approach for both web and mobile experiences?▼

Yes, this telemetry instrumentation approach is applicable for both web and mobile experiences, covering adoption, usage, and reliability scenarios during the feature scoping and design phases.

What's the best way to document analytics events and infrastructure needs for a feature?▼

The best way to document analytics events and infrastructure needs is to produce a concrete telemetry plan detailing event taxonomy, properties, funnel steps, counter metrics, and infrastructure requirements, saved to a structured feature directory path.

Why define telemetry requirements during feature scoping instead of after implementation?▼

Defining telemetry requirements during feature scoping ensures measurement is instrumented from day one, preventing post-implementation gaps where user flows and system interactions lack the necessary analytics events and success metrics to evaluate usage.