Prometheus Monitoring

This sets up a complete Prometheus monitoring stack with configurations for scraping metrics, alert rules, and service discovery. You'll want it when instrumenting applications for observability or building out metrics infrastructure. The skill includes working examples for Node.js and Python instrumentation, Docker Compose setups, and alert rule templates. The best practices section is solid on avoiding the classic pitfall of unbounded cardinality labels, which can absolutely wreck your Prometheus instance. It's comprehensive enough to get a production monitoring setup running without having to piece together scattered documentation.

skills.sh installs: 516
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill prometheus-monitoring --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

Implement comprehensive Prometheus monitoring infrastructure for collecting, storing, and querying time-series metrics from applications and infrastructure.

When to Use

Setting up metrics collection
Creating custom application metrics
Configuring scraping targets
Implementing service discovery
Building monitoring infrastructure

Quick Start

Minimal working example:

# /etc/prometheus/prometheus.yml
global:
  scrape_interval: 15s
  evaluation_interval: 15s
  external_labels:
    cluster: production

alerting:
  alertmanagers:
    - static_configs:
        - targets: ["localhost:9093"]

rule_files:
  - "/etc/prometheus/alert_rules.yml"

scrape_configs:
  - job_name: "prometheus"
    static_configs:
      - targets: ["localhost:9090"]

  - job_name: "node"
    static_configs:
      - targets: ["localhost:9100"]

  - job_name: "api-service"
// ... (see reference guides for full implementation)