metrics-design

Designs service metrics with naming conventions, labels, dashboards, and alerts for Prometheus and OpenTelemetry.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/marquesfelip/agents-and-skills --skill metrics-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics-design
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/metrics-design
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill metrics-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design and implement robust service metrics, enabling observability across production systems by providing a structured approach to metric types, naming conventions, labeling, and dashboards.

Core Features & Use Cases

  • Design metric types (Counter, Gauge, Histogram, Summary) and their usage for common operational signals.
  • Apply RED (Rate, Errors, Duration) and USE (Utilization, Saturation, Errors) methodologies to align instrumentation with business goals.
  • Define naming conventions and low-cardinality labels, plus guidance on recording rules and dashboards for Prometheus, OpenTelemetry, Datadog, and CloudWatch.
  • Create business and domain metrics to quantify user journeys and revenue-impacting operations, with examples for alerting and dashboards.

Quick Start

Configure a metrics design plan for your service by selecting metric types, naming conventions, and RED/USE signals, then implement instrumentation in your codebase.

Frequently Asked Questions about metrics-design

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

FAQPage Schema
Can I use this metrics design approach with Prometheus, OpenTelemetry, and Datadog?

Prometheus, OpenTelemetry, Datadog, and CloudWatch are all supported for metrics design and instrumentation. The Skill provides specific guidance on defining naming conventions, low-cardinality labels, and recording rules across these monitoring stacks.

How do I choose the right metric types like Counters and Histograms for my service?

Choosing the right metric types like Counters, Gauges, Histograms, and Summaries depends on the operational signal you need to track. Counters measure cumulative events, Gauges capture instantaneous values, and Histograms or Summaries record distributions such as request durations.

What are the steps to design a metrics plan for a new service?

Designing a metrics plan for a new service involves selecting appropriate metric types, defining naming conventions, and identifying RED/USE signals. After finalizing the design, you implement the instrumentation directly in your codebase to capture production observability data.

Why do I need low-cardinality labels for Prometheus recording rules and dashboards?

Low-cardinality labels are required for Prometheus recording rules and dashboards to prevent unbounded time series growth. High cardinality degrades query performance and increases storage costs, making strict label schema control essential for production metrics.