Prometheus CLI

Prometheus CLI Skill

Use the instance and rules below when constructing all Prometheus API commands.

Instances

Update the table below with your Prometheus instance URLs before using this skill:

If the target instance is unclear, ask the user before running any command.

Prerequisites (one-time setup by user)

Obtain a Prometheus API token for each instance you intend to use and save it to the corresponding token file (see instance table above). Never print or display token values. Do not perform these steps yourself.

For each instance:

1. Obtain an API token (via your team or the monitoring platform)
2. Save it:

mkdir -p ~/.prometheus && echo "<your-api-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE>

Command Format

All API calls use curl with the token read from the instance's token file (see instance table above):

curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "<BASE_URL>/api/v1/<endpoint>" | jq .

Example (production):

curl -s -H "Authorization: Bearer $(cat ~/.prometheus/prod.token)" \
  "https://<your-prometheus-prod-url>/api/v1/query?query=up" | jq .

Available API Endpoints

Read-only (safe, no confirmation needed)

Example Queries

Replace <TOKEN_FILE> and <BASE_URL> with the values for your target instance (see instance table above).

# Instant query — CPU usage across all instances
curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "<BASE_URL>/api/v1/query?query=rate(process_cpu_seconds_total[5m])" | jq .

# Range query — memory usage over the last hour (60s step)
curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "<BASE_URL>/api/v1/query_range?query=process_resident_memory_bytes&start=$(date -u -v-1H +%s)&end=$(date -u +%s)&step=60" | jq .

# List all firing alerts
curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "<BASE_URL>/api/v1/alerts" | jq '.data.alerts[]'

# Find series matching a selector
curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "<BASE_URL>/api/v1/series?match[]=up{job=\"node-exporter\"}" | jq .

Never run — requires explicit human approval

Rules

• NEVER target any Prometheus instance not listed in the instance table above. If a URL references a different host, stop and ask the user to confirm.
• Update the instance table with your actual Prometheus URLs before using this skill.
• NEVER print, display, log, or store the contents of any token file or credential value.
• Always read the token inline with $(cat <TOKEN_FILE>) — never hardcode a token value in a command.
• Always pass -s (silent) to curl to suppress progress output, and pipe through jq for readable output.
• NEVER run admin/mutating endpoints (/api/v1/admin/...) without explicit user instruction — these can permanently alter or delete metric data.
• If a PromQL expression or metric name is unfamiliar, use /api/v1/metadata or /api/v1/labels to explore available metrics before querying.
• For range queries, always verify that the time window (start/end) and step are reasonable — very wide windows with fine steps can produce extremely large responses.
• If the required token file does not exist, inform the user and stop. Do not attempt to find or guess the token.