prometheus-observer

Observes Prometheus deployments to report installation state, alerts, and rule evaluation health.

4|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/kingdon/skills --skill prometheus-observer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prometheus-observer
Source: https://github.com/kingdon/skills/tree/main/.github/skills/prometheus-observer
Command: npx skills add https://github.com/kingdon/skills --skill prometheus-observer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kubectl, jq, curl, and includes scripts (resource) components.

What problem does it solve?

This Skill observes Prometheus installations to provide comprehensive visibility into installation state, active alerts, AlertManager configuration, and rule evaluation health, enabling rapid diagnostics without modifying running systems.

Core Features & Use Cases

  • Observational health checks: Validate that Prometheus pods are running, endpoints are reachable, and alert routing is configured.
  • Alert analysis: Identify firing alerts, their severities, and rule evaluation status to prioritize responses.
  • Operational guidance: Provide actionable commands and verification steps to restore monitoring health in Kubernetes environments.

Quick Start

Run the slash command '/prometheus-status' to start an autonomous validation workflow. If port-forwards are not active, start them with kubectl port-forward -n monitoring svc/kube-prometheus-stack-prometheus 9090:9090 & and kubectl port-forward -n monitoring svc/kube-prometheus-stack-alertmanager 9093:9093 & as needed.

Frequently Asked Questions about prometheus-observer

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

FAQPage Schema
How do I check Prometheus installation state and active alerts in Kubernetes?

To check Prometheus installation state, validate running pods, reachable endpoints, and active alert routing using an observational health check workflow that reports firing alerts and AlertManager configuration.

How can I inspect firing alerts and AlertManager configuration without modifying my running cluster?

Inspect firing alerts and AlertManager configuration through read-only observation, identifying alert severities and rule evaluation health while ensuring running systems remain unmodified.

What's the best way to validate Prometheus rule evaluation health in a Kubernetes monitoring environment?

Validate Prometheus rule evaluation health by observing the Prometheus deployment to assess rule evaluation status, inspect active alerts, and provide operational guidance to restore monitoring health.

Do I need kubectl and port-forwards to observe Prometheus and AlertManager endpoints?

Yes, observing Prometheus and AlertManager endpoints requires kubectl access to the cluster, standard CLI tools like curl and jq, and active port-forwards to reach the services.

Can I use standard CLI tools like curl and jq to analyze Kubernetes monitoring state?

Yes, you can use curl and jq alongside kubectl to observe Prometheus deployments, query alert statuses, and validate installation state within Kubernetes monitoring environments.

Why does my Prometheus observer workflow require reachable AlertManager endpoints?

Reachable AlertManager endpoints are required to inspect alert routing configuration, validate operational health, and report active alerts accurately during the Prometheus observation workflow.