data-analyst

Define KPIs and verify telemetry instrumentation across frontend and backend codebases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/phishkatlabs/phishkat-crew --skill data-analyst-phishkatlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-analyst
Source: https://github.com/phishkatlabs/phishkat-crew/tree/main/data-analyst
Command: npx skills add https://github.com/phishkatlabs/phishkat-crew --skill data-analyst-phishkatlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines KPIs and telemetry instrumentation in Phase 2 (Design), then verifies every tracking call in the codebase during Phase 4 (Verify).

Core Features & Use Cases

  • Defines 3-5 KPIs with exact definitions and success criteria.
  • Maps KPIs to a complete event catalog and funnels for end-to-end telemetry validation.
  • Provides implementation guidance for frontend and backend analytics, identity management, and verification workflows.

Quick Start

Define 3-5 KPIs, map each KPI to concrete events, and run the verification pass against the codebase to ensure complete telemetry coverage.

Frequently Asked Questions about data-analyst

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

FAQPage Schema
How do I define KPIs for product telemetry instrumentation?

To define KPIs for product telemetry, specify 3-5 exact KPIs with success criteria, then map each KPI to concrete events in an event catalog for end-to-end telemetry validation.

How do I verify telemetry tracking calls across my codebase?

Verify telemetry tracking calls by running a verification pass against your codebase during the verify phase, ensuring complete telemetry coverage for both frontend and backend analytics.

What's the best way to map user behavior funnels to an event catalog?

Map user behavior funnels to an event catalog by defining KPIs first, then linking each KPI to concrete events and funnels to enable end-to-end telemetry validation across the product.

Does this telemetry instrumentation approach work for both frontend and backend?

Yes, telemetry instrumentation provides implementation guidance for both frontend and backend analytics, including identity management and verification workflows for complete codebase coverage.

When do I need identity management for product analytics?

Identity management for product analytics is needed when defining telemetry instrumentation to accurately track user behavior across events, funnels, and KPIs throughout the product lifecycle.

Why does telemetry verification require mapping KPIs to concrete events?

Telemetry verification requires mapping KPIs to concrete events because it validates that every tracking call in the codebase aligns with defined success criteria, ensuring complete coverage.