An observability Skill for adding structured logging, Prometheus metrics, OpenTelemetry tracing, alerts and k6 load tests to services.
Review scope
Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.
Observable capabilities
Adds structured logging with request IDs for correlation.
Instruments services with Prometheus counters and histograms and OpenTelemetry spans.
Builds dashboards using the RED or USE methods.
Defines alerting rules and k6 load tests with thresholds.
Limitations & scope
Code examples are Node.js; other runtimes need adaptation.
Assumes a Prometheus, Grafana or OTLP backend already exists.
The alert and load-test thresholds are examples, not tuned values.
Relevant for
Backend developers adding observability
SRE and DevOps engineers
Teams preparing load tests
02 / STRUCTURE
What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
{
"name": "monitoring-expert",
"description": "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.",
"license": "MIT",
"metadata": {
"author": "https://github.com/Jeffallan",
"company": "https://synergetic.solutions",
"version": "1.1.0",
"domain": "devops",
"triggers": "monitoring, observability, logging, metrics, tracing, alerting, Prometheus, Grafana, DataDog, APM, performance testing, load testing, profiling, capacity planning, bottleneck",
"role": "specialist",
"scope": "implementation",
"output-format": "code",
"related-skills": "devops-engineer, debugging-wizard, architecture-designer"
}
}
03 / WORKFLOW
A reading of the operating sequence
This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.
01
Input
Assess what to monitor
Identify SLIs, critical paths and business metrics.
Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.
Items warrant review
84 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.
Network accessObserved
File writesObserved
Credential useNot observed
Note
File modification is described or implemented
64 occurrences
This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 64 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 20 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Point load tests only at systems you are authorized to test, and confirm logs and spans exclude passwords, tokens and PII.
05 / CONTEXT
Where context can be spent
Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.
Exact token counts unavailable
All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.
No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.
06 / EVALUATION
Controlled evaluation
No controlled evaluation
This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.
Not tested
07 / USAGE
Use with the source in view
Install command
git clone https://github.com/Jeffallan/claude-skills.git
cd claude-skills
# Copy this skill directory into one of:
# ~/.claude/skills/monitoring-expert
# .claude/skills/monitoring-expert
Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/monitoring-expert/SKILL.md.
Review the license, prerequisites and all bundled reference files.
Copy the skill directory into a personal or project-level Claude Code skills directory.
Restart or refresh Claude Code so the skill can be discovered.
Verify installation
Ask Claude Code to instrument an Express route and confirm it uses structured logs, a histogram and a /metrics endpoint.
Prerequisites
Code examples are Node.js; other runtimes need adaptation.
Assumes a Prometheus, Grafana or OTLP backend already exists.
The alert and load-test thresholds are examples, not tuned values.
Example prompts
Representative task
Using the monitoring-expert skill, add Pino structured logging, Prometheus request metrics and an error-rate alert to our Express API, plus a k6 ramp test with p95 and error thresholds.
Inspect before use
Read the monitoring-expert skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/monitoring-expert/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.
08 / VERDICT
A decision, with its limits attached
Strengths
Covers logs, metrics, traces and alerts in one workflow.
Warns against logging sensitive data and alert fatigue.
Considerations
Load tests such as k6 can stress real systems if pointed at them.
High-cardinality metric labels are not discussed in the file.
Research conclusion
A broad, example-driven starting point for instrumenting and alerting on services.
09 / PROVENANCE
Traceable by construction
The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.
Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.