obs-alerts
Provides visibility and troubleshooting for active monitoring and observability alerts.
Install
mkdir -p .claude/skills/obs-alerts && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12223" && unzip -o skill.zip -d .claude/skills/obs-alerts && rm skill.zipInstalls to .claude/skills/obs-alerts
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Show active alerts and their resolution steps. Use this skill whenever the user asks about alerts, wants to know if anything is broken or firing, asks about Alertmanager state, mentions alert silences, or wants to troubleshoot a specific alert like OTelCollectorDown, LokiDown, HighSessionCost, or SensitiveFileAccess. Also use when the user says "any alerts?" or "is everything ok" in the context of the obs stack.Key capabilities
- →Query Alertmanager for active alerts
- →Query Alertmanager for active silences
- →Query Prometheus for firing or pending rule states
- →Query Prometheus for the total rule count
- →Provide alert-specific resolution hints from a reference document
- →Present alert information in a structured table format
How it works
The skill executes `obs-api.sh` to query Alertmanager and Prometheus for alert and silence states, then provides resolution hints from a reference document.
Inputs & outputs
When to use obs-alerts
- →Check active alerts
- →List silenced notifications
- →Troubleshoot system failures
About this skill
Obs Alerts
Active alerts, silences, and resolution guidance.
Queries to run
Use scripts/obs-api.sh. Run independent queries in parallel.
Active alerts
scripts/obs-api.sh am /api/v2/alerts --raw --jq 'if length == 0 then "No active alerts" else .[] | "\(.labels.alertname)\t\(.labels.severity // "?")\t\(.status.state)\t\(.startsAt)" end'
Silences
scripts/obs-api.sh am /api/v2/silences --raw --jq '.[] | select(.status.state == "active") | "\(.matchers | map("\(.name)=\(.value)") | join(", "))\tuntil \(.endsAt)"'
Prometheus rule states (firing/pending)
scripts/obs-api.sh prom /api/v1/rules --raw --jq '.data.groups[].rules[] | select(.state == "firing" or .state == "pending") | "\(.name)\t\(.state)\t\(.annotations.summary // "")"'
Total rule count
scripts/obs-api.sh prom /api/v1/rules --raw --jq '[.data.groups[].rules | length] | add'
Resolution hints
For alert-specific fix instructions, read references/resolution-hints.md in this skill directory.
Output columns
| Column | Source |
|---|---|
| Alert | alertname label |
| Severity | severity label |
| Status | firing/pending |
| Since | startsAt timestamp |
| Description | summary annotation |
For output format options (table/csv/json), read .claude/skills/obs-shared/assets/output-formats.md.
Presentation
- Alert table: Alert | Severity | Status | Since
- If alerts are firing, read
references/resolution-hints.mdand provide the fix - If silences are active, mention them
- If no alerts: "All clear. 0 of 16 rules firing."
- Show total rule count for context
When not to use it
- →When the user is not asking about alerts or the observation stack
- →When the user is not interested in Alertmanager or Prometheus states
- →When the user wants to troubleshoot issues unrelated to alerts
Prerequisites
Limitations
- →Relies on `scripts/obs-api.sh` for queries
- →Resolution hints are read from `references/resolution-hints.md`
- →Output format options are defined in `output-formats.md`
How it compares
This skill automates the querying of Alertmanager and Prometheus for alert status and provides specific resolution hints, which is more efficient than manually checking multiple systems and documentation.
Compared to similar skills
obs-alerts side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| obs-alerts (this skill) | 0 | 5mo | Review | Intermediate |
| agent-performance-monitor | 3 | 6mo | Review | Advanced |
| agent-performance-optimizer | 3 | 6mo | No flags | Advanced |
| coderabbit-observability | 1 | 25d | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
agent-performance-monitor
ruvnet
Agent skill for performance-monitor - invoke with $agent-performance-monitor
agent-performance-optimizer
ruvnet
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer
coderabbit-observability
jeremylongshore
Set up comprehensive observability for CodeRabbit integrations with metrics, traces, and alerts. Use when implementing monitoring for CodeRabbit operations, setting up dashboards, or configuring alerting for CodeRabbit integration health. Trigger with phrases like "coderabbit monitoring", "coderabbit metrics", "coderabbit observability", "monitor coderabbit", "coderabbit alerts", "coderabbit tracing".
mission-control-event-digest
MN755
Summarize recent Mission Control events without raw logs. Use when the user wants the last 5 minutes, last 15 minutes, since last interaction, or since orchestration start summarized in bridge-safe markdown.
yoyopod-logs
attmous
Tail YoYoPod runtime/service logs from Raspberry Pi
sre-practices
duylinhdang1998
Site Reliability Engineering practices from Google - the company that invented SRE. Master SLOs, error budgets, incident response, and toil elimination. Use when designing reliable systems, implementing SRE practices, or improving operational excellence. Learn from the team that runs Google Search,