How do I install the Monitoring Sysadmin skill?

Run npx skillmds@latest add neuralblitz/monitoring-sysadmin in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Monitoring Sysadmin skill do?

System monitoring, metrics, alerting, dashboards, and observability It is listed under Coding & Dev Tools on SkillMD.

Is Monitoring Sysadmin safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Monitoring Sysadmin?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Monitoring Sysadmin free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Monitoring Sysadmin?

NeuralBlitz (@neuralblitz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Monitoring Sysadmin by neuralblitz — Agent Skill

Name: Monitoring Sysadmin
Author: NeuralBlitz

File contents

What I do

Set up comprehensive monitoring systems
Configure meaningful alerts
Create actionable dashboards
Analyze metrics and trends
Implement observability
Establish SLOs and SLIs

When to use me

When tracking system health, debugging issues, or establishing operational excellence.

The Three Pillars

Metrics (Prometheus, Datadog)

Quantitative measurements
Time-series data
Counters, gauges, histograms
Aggregations

Logs (ELK, Loki, Splunk)

Detailed event records
Structured/unstructured
Log levels (DEBUG, INFO, WARN, ERROR)
Correlation IDs

Traces (Jaeger, Zipkin)

Request flow across services
Latency breakdown
Distributed tracing
Span context

Metrics Types

Golden Signals

Latency: Response time
Traffic: Requests per second
Errors: Error rate
Saturation: Resource utilization

RED Metrics (Rate, Errors, Duration)

For request-driven services

USE Metrics (Utilization, Saturation, Errors)

For resource-driven services

Alerting

Best Practices

Alert on symptoms, not causes
Tune thresholds
Avoid alert fatigue
Include context
Runbooks for each alert

Severity Levels

Critical: Immediate action needed
Warning: Attention needed
Info: For awareness

Dashboards

Design Principles

Show relevant data
Include context
Time ranges
Drill-down capability
Shareable links

Common Dashboards

Service overview
Infrastructure
Application performance
Business metrics
Incident response

Tools

Monitoring

Prometheus: Metrics, alerting
Datadog: Full-stack
CloudWatch: AWS
Stackdriver: GCP

Visualization

Grafana: Dashboards
Kibana: Logs

Logging

ELK Stack: Elasticsearch, Logstash, Kibana
Loki: Promtail + Loki + Grafana
Splunk: Enterprise

Tracing

Jaeger: Distributed tracing
Zipkin: Twitter's tracer
AWS X-Ray: Cloud

SRE Concepts

SLI (Service Level Indicator)

Metric measuring service level
Request latency
Error rate
Availability

SLO (Service Level Objective)

Target SLI value
"99.9% of requests < 200ms"

SLA (Service Level Agreement)

Customer-facing commitment
SLO + consequences

---name: monitoring-sysadmindescription: System monitoring, metrics, alerting, dashboards, and observabilitylicense: MIT---## What I do- Set up comprehensive monitoring systems- Configure meaningful alerts- Create actionable dashboards- Analyze metrics and trends- Implement observability- Establish SLOs and SLIs## When to use meWhen tracking system health, debugging issues, or establishing operational excellence.## The Three Pillars### Metrics (Prometheus, Datadog)- Quantitative measurements- Time-series data- Counters, gauges, histograms- Aggregations### Logs (ELK, Loki, Splunk)- Detailed event records- Structured/unstructured- Log levels (DEBUG, INFO, WARN, ERROR)- Correlation IDs### Traces (Jaeger, Zipkin)- Request flow across services- Latency breakdown- Distributed tracing- Span context## Metrics Types### Golden Signals- **Latency**: Response time- **Traffic**: Requests per second- **Errors**: Error rate- **Saturation**: Resource utilization### RED Metrics (Rate, Errors, Duration)- For request-driven services### USE Metrics (Utilization, Saturation, Errors)- For resource-driven services## Alerting### Best Practices- Alert on symptoms, not causes- Tune thresholds- Avoid alert fatigue- Include context- Runbooks for each alert### Severity Levels- **Critical**: Immediate action needed- **Warning**: Attention needed- **Info**: For awareness## Dashboards### Design Principles- Show relevant data- Include context- Time ranges- Drill-down capability- Shareable links### Common Dashboards- Service overview- Infrastructure- Application performance- Business metrics- Incident response## Tools### Monitoring- **Prometheus**: Metrics, alerting- **Datadog**: Full-stack- **CloudWatch**: AWS- **Stackdriver**: GCP### Visualization- **Grafana**: Dashboards- **Kibana**: Logs### Logging- **ELK Stack**: Elasticsearch, Logstash, Kibana- **Loki**: Promtail + Loki + Grafana- **Splunk**: Enterprise### Tracing- **Jaeger**: Distributed tracing- **Zipkin**: Twitter's tracer- **AWS X-Ray**: Cloud## SRE Concepts### SLI (Service Level Indicator)- Metric measuring service level- Request latency- Error rate- Availability### SLO (Service Level Objective)- Target SLI value- "99.9% of requests < 200ms"### SLA (Service Level Agreement)- Customer-facing commitment- SLO + consequences

Frequently asked questions

Monitoring Sysadmin