define-metric

Create standardized business metric specifications with calculation rules and data sources.

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill define-metric-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define-metric
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/ai-analyst/skills/ai-analyst/define-metric
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill define-metric-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the pervasive problem of ambiguous, inconsistently defined business metrics that lead to misaligned analysis, conflicting cross-team reports, and poor data-driven decision-making.

Core Features & Use Cases

  • Standardized Metric Template: Provides a complete, structured template to define any metric with clear calculation rules, component definitions, segmentation dimensions, data sources, health thresholds, and known limitations.
  • Auto-Registration to Metric Dictionary: Automatically registers newly defined metrics to a central team dictionary for consistent, reusable access across all analytics workflows.
  • Use Case: For example, if your marketing and product teams use different definitions for conversion rate, this skill creates a single, shared, unambiguous spec that both teams follow, eliminating conflicting performance reports.

Quick Start

Use the define-metric skill to build a complete standardized specification for your team's checkout conversion rate metric, including exact calculation rules, segmentation dimensions, and health thresholds.

Frequently Asked Questions about define-metric

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

FAQPage Schema
How do I create a standardized metric specification for consistent data reporting?

To create a standardized metric specification, you need a structured template that captures calculation logic, data sources, segmentation rules, thresholds, and limitations to ensure consistent data reporting across teams.

What is the best way to eliminate ambiguity in business metric definitions?

Eliminating ambiguity in business metric definitions requires applying a standardized template that enforces exact calculation rules, component definitions, and segmentation dimensions, preventing conflicting cross-stakeholder reports.

How does auto-registration work for a central metric dictionary?

Auto-registration for a central metric dictionary automatically logs newly defined metrics, capturing their specifications to provide consistent, reusable access across all subsequent product analytics workflows.

Can I use this to align product metrics across different cross-functional teams?

Yes, you can use this to align product metrics across cross-functional teams by generating a single, unambiguous metric specification that standardizes driver decomposition and calculation logic for all stakeholders.

What limitations need to be documented when defining a metric?

When defining a metric, you must document known limitations alongside calculation rules and health thresholds to ensure reproducible analysis and prevent misaligned data-driven decision-making.

Why do my cross-team reports show conflicting numbers for the same product metric?

Cross-team reports show conflicting numbers for the same product metric when teams use inconsistent calculation logic and segmentation rules, a problem solved by applying a standardized metric specification.