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

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

This is a strong skill with excellent actionability — the executable code examples across logging, metrics, tracing, alerting, and load testing are comprehensive and production-ready. The workflow is well-sequenced with validation checkpoints. The main weakness is that the skill is somewhat long for an overview file; some of the detailed code examples could be pushed to the reference files to improve conciseness and progressive disclosure.

Suggestions

Consider moving the longer code examples (Prometheus metrics, OpenTelemetry tracing) to their respective reference files and keeping only minimal snippets in the main SKILL.md to improve conciseness.

Remove the 'Bad' logging example — Claude already knows what string interpolation looks like; the 'Good' example alone is sufficient.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good executable examples, but the code examples are quite lengthy and could be trimmed. The 'Bad' logging example is unnecessary explanation Claude already knows. Some inline comments add minor verbosity but the overall structure is reasonable.	2 / 3
Actionability	Excellent executable examples across all key areas: structured logging with Pino, Prometheus metrics instrumentation, OpenTelemetry tracing with proper error handling, alerting rules in YAML, and k6 load tests with thresholds. All code is copy-paste ready with real libraries and realistic configurations.	3 / 3
Workflow Clarity	The core workflow provides a clear 5-step sequence with explicit validation checkpoints: 'verify data arrives before proceeding' at step 3 and 'validate no false-positive flood before shipping' at step 5. The sequence is logical and includes feedback-loop thinking for the alerting step.	3 / 3
Progressive Disclosure	The reference table is well-structured with clear 'Load When' guidance, but no bundle files were provided to verify the referenced paths exist. The main file includes substantial inline code examples that could arguably be in the reference files, making the SKILL.md longer than ideal for an overview. However, the quick-start examples serve a valid purpose inline.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

This is a strong skill description that excels across all dimensions. It provides comprehensive, specific capabilities with concrete tool names, clearly delineates when to use the skill with an explicit 'Use when...' clause, and occupies a distinct niche that minimizes conflict risk. The only minor concern is that it covers a broad scope (monitoring, load testing, profiling, capacity planning) which could arguably be split, but the observability/performance theme ties them together coherently.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: configures monitoring systems, implements structured logging pipelines, creates Prometheus/Grafana dashboards, defines alerting rules, instruments distributed tracing, conducts load testing, performs application profiling, and plans infrastructure capacity.	3 / 3
Completeness	Clearly answers both 'what' (configures monitoring, implements logging, creates dashboards, etc.) and 'when' with an explicit 'Use when...' clause covering multiple trigger scenarios like setting up monitoring, debugging production issues, running load tests, and profiling bottlenecks.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: monitoring, logging, Prometheus, Grafana, dashboards, alerting, distributed tracing, load testing, k6, Artillery, profiling, CPU/memory bottlenecks, capacity, observability, metrics, traces, logs. Good coverage of both tool names and conceptual terms.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche around observability, monitoring, and performance engineering with distinct tool-specific triggers (Prometheus, Grafana, k6, Artillery) that are unlikely to conflict with other skills. The combination of monitoring + load testing + profiling + capacity planning is distinctive.	3 / 3
	Total	12 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Commit: e8be415

Reviewed: 4 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.