ds-metric-validation

Validates metric definitions and detects risks in experiment readouts.

6|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Khodzitcky-Vl/data-science-ai-superpowers --skill ds-metric-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ds-metric-validation
Source: https://github.com/Khodzitcky-Vl/data-science-ai-superpowers/tree/main/ds-metric-validation
Command: npx skills add https://github.com/Khodzitcky-Vl/data-science-ai-superpowers --skill ds-metric-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents experiment and validation readouts from being distorted by incorrect metric definitions, unit mismatches, denominator drift, missingness issues, or leakage risks that can silently break conclusions.

Core Features & Use Cases

  • Minimum metric checks to verify numerator/denominator definitions, filter logic, null handling, and unit alignment before trusting results.
  • Escalation triggers that identify when distributional instability, SRM/invariant failures, denominator drift, sign flips, or segment concentration indicate heightened risk.
  • Standard and optional robustness checks to quantify outlier contribution, test alternative definitions, and assess sensitivity to missingness and operational/logging artifacts.
  • Use case: A metrics team is about to report treatment lift, but observes unstable denominators and heavy tails; this Skill helps validate interpretability and stability before the number reaches stakeholders.

Quick Start

Use ds-metric-validation to validate the metric definition for an upcoming experiment and surface any risks like denominator drift, missingness imbalance, or potential leakage.

Frequently Asked Questions about ds-metric-validation

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

FAQPage Schema
How do I validate metrics for A/B testing to prevent misleading experiment readouts?

Metric validation verifies numerator and denominator definitions, unit alignment, and missingness before reporting A/B testing lift. It enforces minimum definition checks and escalates into robustness diagnostics when SRM, denominator drift, or leakage are suspected.

Why does denominator drift distort experiment results and how can I detect it?

Denominator drift distorts experiment results by shifting the baseline against which treatment lift is measured. Validation tools detect this by applying escalation triggers that identify distributional instability and segment concentration before results reach stakeholders.

What is SRM in A/A validation and when do I need to run invariant checks?

SRM, or Sample Ratio Mismatch, indicates a systematic imbalance in experiment arm sizes. You need invariant checks during A/A validation when SRM failures occur, triggering standard diagnostics to assess unit alignment and logging artifacts.

How do I check for post-treatment leakage and outlier dominance in my experiment metrics?

Checking for post-treatment leakage and outlier dominance involves running robustness diagnostics that quantify outlier contribution. Validation workflows test alternative metric definitions and assess sensitivity to operational artifacts to ensure lift remains decision-safe.

Can I use metric validation for reporting workflows outside of active A/B tests?

Yes, metric validation applies to metric-driven reporting workflows beyond active A/B tests. It ensures that numerator and denominator logic, filter logic, and null handling remain interpretable and stable for any analytics reporting.

What are the limitations of relying solely on minimum metric checks before an experiment?

Minimum metric checks only verify baseline definitions, filter logic, and unit alignment. They lack the robustness diagnostics needed to detect sign flips, outlier dominance, and missingness sensitivity, which can silently break experiment conclusions.