monitoring-expert

An agent skill by Jeffallan, from Jeffallan/claude-skills. Tags: analytics, automation, debugging, devops, performance, security.

What it does

Configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing. Implements Prometheus/Grafana stacks, conducts load testing, performs application profiling, and plans infrastructure capacity. Use when setting up application monitoring, adding observability to services, debugging production issues with logs/metrics/traces, running load tests with k6 or Artillery, profiling CPU/memory bottlenecks, or forecasting capacity needs.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add Jeffallan/claude-skills --skill monitoring-expert

Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):

git clone --depth 1 https://github.com/Jeffallan/claude-skills
cp -r claude-skills/skills/monitoring-expert ~/.claude/skills/monitoring-expert

Safety box score

Grade C, moderate risk: 33 of 100 risk points, rated 2026-10-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.

This skill is a documentation-heavy observability guide with runnable examples for logging, metrics, tracing, profiling, load testing, and alerting. The main risks are that it can send telemetry to external endpoints, run profiling/load-test commands against live processes, and create local profiler artifacts; it also includes an insecure JMX remote example.

Category levels, from 0 (none) to 3 (high)
Category	Level	Why
Code & shell execution	2 (moderate)	The skill includes runnable commands and code that execute against processes, such as `clinic doctor -- node app.js`, `node --prof app.js`, and `curl http://localhost:6060/debug/pprof/profile?seconds=30 > cpu.prof` in `references/application-profiling.md`.
Network access	2 (moderate)	It configures telemetry and alert delivery to remote services, including `new OTLPTraceExporter({ url: 'http://jaeger:4318/v1/traces' })`, New Relic/DataDog examples, and Alertmanager `slack_api_url` / PagerDuty configs.
Filesystem reach	1 (low)	Profiling examples write artifacts locally, such as `v8.writeHeapSnapshot()` and shell redirections like `> cpu.prof`, `> heap.prof`, and `> goroutine.prof`, but they are generally confined to the local working area.
Secrets & credentials	1 (low)	The logging examples capture request metadata and stack traces, but the skill explicitly warns `MUST NOT DO - Log sensitive data (passwords, tokens, PII)` and even redacts `password`, `token`, and `authorization`.
Privilege & persistence	2 (moderate)	It includes a global install command `npm install -g clinic` and a Java profiling example that enables remote JMX with `authenticate=false` and `ssl=false`, which changes service/runtime exposure.
Instruction hijack surface	0 (none)	There are no instructions to ignore higher-level rules, follow remote content, hide actions, or otherwise manipulate the agent's instructions.
Irreversible actions	0 (none)	The skill does not push, publish, deploy, send messages, pay, book, or delete; it is focused on observability setup and analysis.
Transparency	0 (none)	All supplied content is plain Markdown and code snippets; there are no binaries, encoded blobs, or opaque installers.

Before installing

Read `references/application-profiling.md` first; it runs against live apps and writes profiler artifacts to disk.
Confirm any OTLP, Datadog, New Relic, Slack, or PagerDuty endpoints are test destinations before using the examples.
Do not enable the Java JMX example on a machine you care about unless you intend to expose port 9010 without auth/SSL.
Run the load-test examples only against systems you are authorized to stress, not production by default.

Rated 2026-10-20 by an automated review of 9 files from the skill's repository.

Source

Repository: Jeffallan/claude-skills (all skills from this repository)
Path: skills/monitoring-expert/SKILL.md
Branch: main
Updated: 2026-09-19

chaos-engineer — Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks.
cloud-architect — Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure.
kubernetes-specialist — Use when deploying or managing Kubernetes workloads.
agents-deploy — Use when deploying your agent to AWS, or when a deploy has failed.
eas-observe — EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC.
setup — Set up the AWS DevOps Agent and AWS Security Agent connections. Use when the user says "set up", "configure", "connect", or when MCP tools are missing.