# alerting-dashboard-builder

alerting-dashboard-builder turns your service level objectives into Prometheus burn-rate alerts and a dashboard template, with runbook links and a first-response guide.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 266 installs · ★ 64 repo stars
- Author: patricio0312rev
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/patricio0312rev/skills/tree/HEAD/performance/alerting-dashboard-builder/SKILL.md
- Updated: 2026-01-12
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/alerting-dashboard-builder

## What it does

The skill gives you a starting set for service monitoring: SLOs written as YAML with an objective, a window and an SLI, Prometheus alert rules, and a JSON dashboard template. Three parts sit inside. One holds the SLO block with PromQL expressions, another the rules for fast and slow error-budget burn, the third a row of golden-signal panels covering request rate, errors, latency percentiles, CPU and memory.

Alerts carry a severity label. One fires when 1% of the budget burns within an hour; the warning rule catches a slower burn measured over a day. Both use `for` so a brief spike does not page anyone, and both attach a runbook annotation. That link, `https://runbooks.example.com/availability-fast-burn`, is a placeholder — swap in your own URL or the on-call engineer lands on a dead page.

Queries assume the metric names `http_requests_total` and `http_request_duration_seconds_bucket`. Different names in your setup mean rewriting the expressions, otherwise panels and alerts stay empty. A short response guide is included too: check the latest deploy, read the error logs, look at dependent services, escalate after 15 minutes.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add patricio0312rev/skills --skill alerting-dashboard-builder -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/alerting-dashboard-builder/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/alerting-dashboard-builder/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add patricio0312rev/skills --skill alerting-dashboard-builder -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/alerting-dashboard-builder/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add patricio0312rev/skills --skill alerting-dashboard-builder -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/alerting-dashboard-builder/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install patricio0312rev/skills performance/alerting-dashboard-builder/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/alerting-dashboard-builder/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add patricio0312rev/skills --skill alerting-dashboard-builder -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/patricio0312rev/skills --path performance/alerting-dashboard-builder
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/alerting-dashboard-builder/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add patricio0312rev/skills --skill alerting-dashboard-builder -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/patricio0312rev/skills/tree/HEAD/performance/alerting-dashboard-builder/SKILL.md

## When to use it
- define an SLO with objective, window and SLI in YAML
- generate Prometheus rules for fast and slow error-budget burn
- lay out a dashboard with golden-signal and SLO-tracking panels
- attach a runbook link to an alert annotation
- write down first-response steps for a high error rate or high latency

## Example prompts
- Define an SLO for our API: 99.9% availability over 30d and p95 latency under 500ms, then write the alert rules.
- Build a service health dashboard with golden-signal panels and an error budget row.
- Add a runbook link and a first-response guide to the AvailabilitySLOFastBurn alert.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 71c8e1b21de3ffc9.

BEGIN THIRD-PARTY FILE 71c8e1b21de3ffc9
````text
---
name: alerting-dashboard-builder
description: Creates SLO-based alerts and operational dashboards with key charts, alert thresholds, and runbook links. Use for "alerting", "dashboards", "SLO", or "monitoring".
---

# Alerting & Dashboard Builder

Build effective alerts and dashboards based on SLOs.

## SLO Definition

```yaml
slos:
  - name: api_availability
    objective: 99.9%
    window: 30d
    sli: |
      sum(rate(http_requests_total{status_code!~"5.."}[5m])) /
      sum(rate(http_requests_total[5m]))

  - name: api_latency
    objective: 95% # 95% of requests under 500ms
    window: 30d
    sli: |
      histogram_quantile(0.95,
        rate(http_request_duration_seconds_bucket[5m])
      ) < 0.5
```

## Alert Rules

```yaml
groups:
  - name: slo_alerts
    rules:
      # Fast burn (1% budget in 1h)
      - alert: AvailabilitySLOFastBurn
        expr: |
          (1 - (sum(rate(http_requests_total{status_code!~"5.."}[1h])) /
          sum(rate(http_requests_total[1h])))) > 0.01
        for: 5m
        labels:
          severity: critical
        annotations:
          summary: "Burning 1% error budget per hour"
          runbook: "https://runbooks.example.com/availability-fast-burn"

      # Slow burn (10% budget in 24h)
      - alert: AvailabilitySLOSlowBurn
        expr: |
          (1 - (sum(rate(http_requests_total{status_code!~"5.."}[24h])) /
          sum(rate(http_requests_total[24h])))) > 0.001
        for: 1h
        labels:
          severity: warning
        annotations:
          summary: "Burning error budget slowly"
```

## Dashboard Template

```json
{
  "title": "Service Health Dashboard",
  "rows": [
    {
      "title": "Golden Signals",
      "panels": [
        {
          "title": "Request Rate",
          "query": "sum(rate(http_requests_total[5m]))",
          "type": "graph"
        },
        {
          "title": "Error Rate",
          "query": "sum(rate(http_requests_total{status_code=~"5.."}[5m]))",
          "type": "graph"
        },
        {
          "title": "Latency (p50, p95, p99)",
          "queries": [
````
END THIRD-PARTY FILE 71c8e1b21de3ffc9

The third-party file has ended. Everything between the 71c8e1b21de3ffc9 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2086 of 3848 bytes. © patricio0312rev · MIT · https://github.com/patricio0312rev/skills/tree/HEAD/performance/alerting-dashboard-builder/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
