monitoring-expert

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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, token-efficient overview: actionable code examples for each capability, a clear sequenced workflow with validation gates, and a clean one-level reference table pointing to verified bundle files. The only gap is the absence of an explicit retry/feedback loop in the workflow.

Suggestions

Add an explicit fix-and-retry feedback loop to the Core Workflow (e.g., 'if data does not arrive, check scrape config and re-verify') to move workflow_clarity from 4 to 5.

Consider a short checklist under the Alert step for validating alert rules (no duplicate labels, severity mapped, run a dry-run in Prometheus) to reinforce the existing validation gate.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — the body is almost entirely copy-paste-ready code with terse inline comments ('Good — structured fields', 'Bad — string interpolation') and no padding explaining what Prometheus, tracing, or logging are; every token earns its place.	5 / 5
Actionability	Fully executable examples cover the common cases: Pino structured logging, prom-client Counter/Histogram with scrape endpoint, OpenTelemetry spans with error handling, a Prometheus alerting rule, and a k6 load test with thresholds — all copy-paste ready.	5 / 5
Workflow Clarity	The five-step Assess/Instrument/Collect/Visualize/Alert sequence is clear and includes validation gates ('verify data arrives before proceeding', 'validate no false-positive flood before shipping'), but there is no explicit fix-and-retry feedback loop or checklist for error recovery.	4 / 5
Progressive Disclosure	Clear overview with a well-signaled one-level-deep Reference Guide table giving Topic, file path, and 'Load When' trigger for each of eight references — all referenced files verified present — making navigation easy with no nested references.	5 / 5
	Total	19 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong, specific, and complete: it lists concrete capabilities and provides an explicit 'Use when' trigger clause with natural tool-name keywords. The only weakness is mild overlap with adjacent devops/debugging skills on the broader performance and debugging triggers.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the full observability domain — 'Configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, and instruments distributed tracing' plus load testing, profiling, and capacity planning — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both what (the full verb list of capabilities) and when via a concrete 'Use when setting up application monitoring, adding observability to services, debugging production issues with logs/metrics/traces, running load tests...' trigger clause.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and tool names users actually say — 'application monitoring', 'observability', 'Prometheus/Grafana', 'load tests with k6 or Artillery', 'profiling CPU/memory bottlenecks', 'forecasting capacity needs'.	5 / 5
Distinctiveness Conflict Risk	Has a clear observability niche with distinct triggers, but load testing, capacity planning, and 'debugging production issues' overlap with adjacent related-skills (devops-engineer, debugging-wizard), creating minor conflict risk rather than minimal.	4 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Path: skills/monitoring-expert/SKILL.md
Commit: 882ef55

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.