Skip to main content
skill CX Codex

monitoring-observability · ahmedasmar — Claude Code skill: metrics, logs, SLOs

A skill for building monitoring and observability: metrics strategy, alerts, dashboards, SLOs and incident troubleshooting.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ahmedasmar/devops-claude-skills --skill monitoring-observability -a claude-code
npx skills add ahmedasmar/devops-claude-skills --skill skills -a claude-code
Open on GitHub

What monitoring-observability does

The skill walks a decision tree. Setting up monitoring from scratch starts at metrics strategy design; an existing problem jumps straight to troubleshooting. It lays out the Four Golden Signals, the RED and USE methods, and PromQL snippets for request rate, error ratio and p95 latency. Separate sections cover structured logging, alert design with severity levels and multi-window burn rate, Grafana dashboard generation, and SLOs with error budgets.

Bundled scripts do the repetitive part: scripts/log_analyzer.py scans a log file for errors, patterns and stack traces, scripts/alert_quality_checker.py audits Prometheus rules for naming, required labels and the for clause, and scripts/dashboard_generator.py builds dashboard JSON from a template. There are alert templates for web apps and Kubernetes, plus an incident runbook template. Prometheus and CloudWatch queries run from the CLI through curl and aws cloudwatch get-metric-statistics.

The scripts need Python 3. CloudWatch queries expect a configured AWS CLI, and Prometheus queries need a reachable API endpoint. If you are on Datadog and the bill keeps climbing, the skill has a branch on cost optimization and moving to an open-source stack — worth doing the math on which metrics drive the volume before you migrate.

What it helps with

  • design a metrics set for a new service
  • write an alert on error budget burn
  • generate a Grafana dashboard from a template
  • scan a log file for errors and stack traces
  • calculate an SLO and error budget

Example prompts for the agent

  • help me design metrics for a new API using the Four Golden Signals
  • run alert_quality_checker against my Prometheus rules
  • generate a Grafana dashboard for the payment_api service

How to install monitoring-observability

1Skills CLI (Vercel)

npx skills add ahmedasmar/devops-claude-skills --skill monitoring-observability -a claude-code
npx skills add ahmedasmar/devops-claude-skills --skill skills -a claude-code

2Manually: put the files in place

~/.claude/skills/skills/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/skills/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about monitoring-observability

How do I install monitoring-observability in Claude?

Run npx skills add ahmedasmar/devops-claude-skills --skill monitoring-observability -a claude-code. The skill file then lands at ~/.claude/skills/skills/SKILL.md.

What does monitoring-observability do?

It covers monitoring and observability work: metrics strategy, structured logging, alerts, dashboards, SLOs with error budgets, and performance troubleshooting.

What do the skill's scripts require?

Python 3 for log_analyzer.py, alert_quality_checker.py and dashboard_generator.py. CloudWatch queries go through the AWS CLI, Prometheus queries through its HTTP API.

Similar skills

Everything for DevOps and infrastructure →

monitoring-observability by other authors comes first.

From the same set2

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor