prometheus-patterns
PromQL queries, alerting rules, recording rules, Grafana dashboard JSON, SLO
Profile →npx skills add vibeeval/vibecosystem --skill prometheus-patterns --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Prometheus Patterns ## PromQL Essentials ### Rate and Error Calculations ```promql # Request rate (per second, 5m window) rate(http_requests_total[5m]) # Error rate percentage sum(rate(http_requests_total{status=~"5.."}[5m])) / sum(rate(http_requests_total[5m])) * 100 # P99 latency from histogram histogram_quantile(0.99, sum(rate(http_request_duration_seconds_bucket[5m])) by (le)) # P50 latency by endpoint histogram_quantile(0.50, sum(rate(http_request_duration_seconds_bucket[5m])) by (le, handler) ) # Saturation: CPU usage per pod sum(rate(container_cpu_usage_seconds_total[5m])) by (pod) / sum(kube_pod_container_resource_limits{resource="cpu"}) by (pod) * 100 ``` ### SLO: Error Budget ```promql # SLO: 99.9% availability over 30 days # Error budget = 0.1% = 43.2 minutes/month # Current burn rate (how fast consuming budget) 1 - ( sum(rate(http_requests_total{status!~"5.."}[1h])) / sum(rate(http_requests_total[1h])) ) / (1 - 0.999) # Remaining error budget (percentage) 1 - ( sum(increase(http_requests_total{status=~"5.."}[30d])) / (sum(increase(http_requests_total[30d])) * 0.001) ) ``` ## Recording Rules ```yaml groups: - name: sli_rules interval: 30s rules: - record: job:http_requ
- PromQL Essentials
- Rate and Error Calculations
- SLO: Error Budget
- Recording Rules
- Alerting Rules
- Instrumentation (Go)
- Checklist
- Anti-Patterns
What does the prometheus-patterns skill do?
PromQL queries, alerting rules, recording rules, Grafana dashboard JSON, SLO
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill prometheus-patterns --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.