prometheus-configuration

Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.

Quality

69%

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 ./plugins/observability-monitoring/skills/prometheus-configuration/SKILL.md

Quality

Content

51%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.

A tidy overview that delegates detail to a reference file, but the body lacks an actionable, sequenced setup workflow with validation, and the reference file points to several bundle files that are missing. Weakest dimensions are workflow_clarity and progressive_disclosure.

Suggestions

Add a short ordered setup workflow to the body (install → write prometheus.yml → promtool check config → start → verify /targets) with an explicit validation checkpoint, rather than only a use-case list.

Move at least one minimal executable prometheus.yml snippet into the body so the skill is actionable without opening details.md.

Create the files referenced in details.md (assets/prometheus.yml.template, references/scrape-configs.md, references/recording-rules.md, scripts/validate-prometheus.sh) or remove the dead 'Reference: See …' pointers.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — one-line best practices and terse curl commands — but the 'Purpose' section repeats the description almost verbatim and could be trimmed.	4 / 5
Actionability	The body offers only troubleshooting curl commands as executable code; the actual config and rule examples live in details.md, and the best practices are high-level directives rather than copy-paste guidance.	3 / 5
Workflow Clarity	No sequenced setup workflow exists in the body — 'When to Use' is a use-case list, not steps — and validation (promtool) is absent from the body entirely, deferred to the reference file.	2 / 5
Progressive Disclosure	The body is well-sectioned and cleanly points one level deep to references/details.md, but details.md itself references files that do not exist in the bundle (assets/prometheus.yml.template, references/scrape-configs.md, references/recording-rules.md, scripts/validate-prometheus.sh), breaking downstream navigation.	3 / 5
	Total	12 / 20 Passed

Description

87%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.

A strong description that clearly answers both what and when using third-person, concrete language and natural trigger phrases. Minor specificity and trigger-synonym gaps keep specificity and trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the domain (Prometheus) and several concrete actions — 'metric collection, storage, and monitoring' — but stops short of the fully comprehensive action list of a 5.	4 / 5
Completeness	Explicitly states both what ('Set up Prometheus for comprehensive metric collection, storage, and monitoring') and when ('Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('metrics collection', 'monitoring infrastructure', 'alerting systems'), but misses common variants like 'scraping' or 'recording rules'.	4 / 5
Distinctiveness Conflict Risk	Prometheus is a clear niche with distinct, domain-specific triggers; minimal risk of firing for an unrelated skill.	5 / 5
	Total	18 / 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: wshobson/agents
Path: plugins/observability-monitoring/skills/prometheus-configuration/SKILL.md
Commit: d6837ae

Reviewed: about 11 hours 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.