Skip to content
Back to skills

Experimentation Metric Definition Contracts

ASecurity

One canonical definition per metric, versioned and documented, killing dashboard wars.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsbashtestinggit

Works with

  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill experimentation-metric-definition-contracts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Experimentation Metric Definition Contracts?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Experimentation Metric Definition Contracts
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-experimentation-metric-definition-contracts/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-experimentation-metric-definition-contracts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: experimentation-metric-definition-contracts
description: "One canonical definition per metric, versioned and documented, killing dashboard wars."
---
# Write metric definitions as contracts

> One canonical definition per metric, versioned and documented, killing dashboard wars.

**Track:** 📊 Data Science & Analytics · **Domain:** Experimentation & A/B Testing · **Level:** intermediate · **~30 min**

**Who this is for:** Data Scientists, Analysts, Research Scientists, Product Analysts

## When to Use This Skill

One canonical definition per metric, versioned and documented, killing dashboard wars.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Steps

1. Create a metric catalog entry per KPI: formula, grain, filters, owner
2. Specify inclusion/exclusion rules explicitly (bots, refunds, internal staff)
3. Implement once in the semantic layer; dashboards reference it
4. Version definitions; changelog when business logic changes
5. Backfill check: recompute last 12 months after any change
6. Review catalog quarterly; archive dead metrics loudly

## Common Pitfalls

- 'Active users' meaning three things in three dashboards
- Revenue defined differently between finance and product

## Commands

**Install with skills CLI**
```bash
npx skills add aniruddhaadak80/skills --skill experimentation-metric-definition-contracts
```

**Install globally**
```bash
npx skills add aniruddhaadak80/skills --skill experimentation-metric-definition-contracts -g
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…