Monitoring
Use when the user asks about infrastructure monitoring with Prometheus, Grafana, Loki or ELK, scrape configs and relabeling, Alertmanager routing by severity, Loki label strategy, or node and host metrics. Produces monitoring stack configs and alert routes. Not for Kubernetes ServiceMonitor setup (use prometheus-grafana) or TSDB scaling (use sre-observability-scaling).
Install
npx skills add j4flmao/agent-skills --skill monitoringgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/monitoring ~/.claude/skills/monitoringPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Monitoring Stack ## Purpose Define and enforce monitoring stack configuration with Prometheus, Grafana, Loki, and ELK for metrics, logs, traces, and alerting. ## Agent Protocol ### Trigger User request includes: `monitoring`, `prometheus`, `grafana`, `loki`, `elk`, `elasticsearch`, `kibana`, `logstash`, `beats`, `filebeat`, `metricbeat`, `tempo`, `jaeger`, `datasource`, `dashboard`. ### Input Context - Current monitoring setup (if any) - Infrastructure (Kubernetes, bare metal, cloud) - Scale (number of nodes/services) - Budget (open-source vs enterprise) - Required integrations (Slack, PagerDuty, Opsgenie) ### Output Artifact A markdown document containing: - Monitoring stack architecture diagram (text) - Tool selection rationale (Prometheus vs Datadog, etc.) - Prometheus configuration (scrape configs, recording rules, alerting rules) - Grafana dashboard structure (folder hierarchy, data source setup) - Loki configuration (log scrape, labels, retention) - ELK configuration (index templates, pipeline, shard strategy) - Integration with on-call (Alertmanager → PagerDuty/Slack) ### Response Format Produce the artifact directly. No preamble, no postamble, no explanations. No filler, no hedging, no transitions. Strip articles a/an/the where unambiguous. Compress output — why use many token when few do trick. ### Completion Criteria - Monitoring architecture defined with data flow - Prometheus scrape configs for all service types
Details
- Skill name
monitoring- Repository
- j4flmao/agent-skills
- Path
skills/devops/monitoring/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Monitoring skill do?
Use when the user asks about infrastructure monitoring with Prometheus, Grafana, Loki or ELK, scrape configs and relabeling, Alertmanager routing by severity, Loki label strategy, or node and host metrics. Produces monitoring stack configs and alert routes. Not for Kubernetes ServiceMonitor setup (use prometheus-grafana) or TSDB scaling (use sre-observability-scaling).
How do I install the Monitoring skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill monitoring. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Monitoring popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Monorepo
45j4flmao/agent-skills
Use when the user asks about monorepos, Nx, Turborepo, nx affected, pnpm/yarn/npm workspaces, remote caching, task pipelines, project graphs, or module boundary rules. Produces workspace layout and build orchestration configs. Not for dependency update bots (use dependency-management) or Git submodules (use advanced-workflows).
Microservices
45j4flmao/agent-skills
Use when the user asks about microservices, splitting a monolith, service boundaries, database per service, sagas, service discovery or strangler fig migration. Produces a decomposition and communication plan (or a monolith verdict). Not for DDD modeling (use architecture-domain-driven-design) or Kubernetes setup (use kubernetes).
Nomad
45j4flmao/agent-skills
Use when the user asks about HashiCorp Nomad, Nomad job specs (service, batch, system, periodic, parameterized), ACLs, Nomad Variables, Vault or Consul integration, CSI and host volumes, canary updates, node drain, or the Nomad Autoscaler. Produces Nomad job files and cluster operations. Not for Kubernetes (use kubernetes) or Consul service mesh (use consul).
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.