monitoring-observability

Monitoring and observability with OpenTelemetry, Prometheus, Grafana dashboards, and structured logging

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/monitoring-observability/SKILL.md

Quality

Content

80%

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, code-first reference skill: executable examples across tracing, metrics, logging, and alerting with minimal padding. Its main gaps are the absence of an ordered setup workflow with validation checkpoints and any progressive disclosure into reference files.

Suggestions

Add a short ordered 'Setup workflow' that sequences SDK init -> verify traces export -> add metrics -> add dashboards, with explicit validation at each step.

Move larger reference material (e.g. a Grafana dashboard JSON library or full alerting rule catalog) into references/ files and link to them from the body.

Include a brief verification step for the OTLP exporter and Prometheus scrape target so users can confirm telemetry is flowing before proceeding.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste code and YAML with almost no explanatory prose, assuming Claude's competence and avoiding re-explanation of what OpenTelemetry or Prometheus are; every section earns its place.	3 / 3
Actionability	It provides fully executable TypeScript SDK setup, span/meter code, prom-client instrumentation, pino logging config, and Prometheus alerting YAML, all concrete and copy-paste ready.	3 / 3
Workflow Clarity	Content is organized into clear topical sections and ends with a checklist, but there is no sequenced multi-step workflow with explicit validation/feedback checkpoints (e.g. verify traces appear in the collector before adding metrics), so it sits at 'sequence present but checkpoints missing'.	2 / 3
Progressive Disclosure	No bundle files exist and all material (dashboard definitions, alerting rule library, logging setup) lives inline in a single ~190-line SKILL.md; sections are well-organized but content that would benefit from being split into one-level-deep references is not separated.	2 / 3
	Total	10 / 12 Passed

Description

65%

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 clearly identifies a focused tooling niche with natural trigger keywords, but it is a noun phrase listing tools rather than concrete actions and omits any 'Use when' guidance. Adding action verbs and an explicit trigger clause would raise both specificity and completeness.

Suggestions

Add concrete action verbs, e.g. 'Instrument services with OpenTelemetry, configure Prometheus scraping, and build Grafana dashboards'.

Append an explicit trigger clause such as 'Use when setting up monitoring, distributed tracing, metrics, or observability for a service'.

Clarify scope to reduce overlap, e.g. specify Node.js/TypeScript services or backend observability to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'Monitoring and observability with OpenTelemetry, Prometheus, Grafana dashboards, and structured logging' names the domain and several specific tools, but uses no action verbs (e.g. 'instrument', 'configure', 'build dashboards'), so it stops at naming domain and tools rather than listing concrete actions.	2 / 3
Completeness	It clearly states what the skill covers but provides no 'Use when...' trigger or equivalent, so per the guidelines completeness is capped at 2 (what present, when missing).	2 / 3
Trigger Term Quality	Terms like 'monitoring', 'observability', 'OpenTelemetry', 'Prometheus', 'Grafana dashboards', and 'structured logging' are natural keywords a user would actually say when requesting this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The named tooling niche is fairly specific, but the absence of an explicit trigger clause and the broad 'monitoring and observability' framing means it could still overlap with related devops or logging skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	9 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/awesome-claude-code-toolkit
Path: skills/monitoring-observability/SKILL.md
Commit: ebdf1d5

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