metrics-definition

Define, instrument, and track key data points that measure product success, transforming business goals into a quantified feedback loop.

Skill by zpower426

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/zpower426-metrics-definition

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Define, instrument, and track key data points that measure product success, transforming business goals into a quantified feedback loop.

Use cases: data

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/metrics-definition

What's inside

Skill name: metrics-definition
Description: Define, instrument, and track key data points that measure product success, transforming business goals into a quantified feedback loop.
License: MIT
Instructions: 20 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Metrics Definition: Quantitative Metrics and Feedback Loops

What cannot be measured cannot be optimized.

## Checklist

1. **Define Core Events** — Which user actions reflect the delivery of core value?
2. **Develop Instrumentation Plan (Tracking)** — Event names, properties, and trigger conditions.
3. **Categorize Metric Attributes** —
   - **Outcome Metrics**: Retention, Revenue.
   - **Proxy Metrics (Behavioral)**: Search frequency, Share rate.
4. **Establish Dashboards** — Ensure real-time visibility of data.

## Core Mandates

- **Prevent Noise**: More tracking is not necessarily better. Every data point tracked must correspond to a specific decision.
- **Data Consistency**: Ensure that the logical meaning of backend tracking aligns with frontend tracking.
- **Interpretability**: Metrics must be understandable to team members without a data background.

From zpower426/pmpowers, MIT.

Signals

Stars: 0
Forks: 1
Open issues: 0
Last commit (this folder): Mar 31, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/zpower426/pmpowers
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from zpower426

Cite this page

metrics-definition skill. Agent Mart. https://agentmart.dev/skills/zpower426-metrics-definition (last updated 2026-10-24)