CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/prometheus-configuration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable with complete, executable Prometheus configs and validation commands, but it is verbose and monolithic — generic boilerplate, redundant scrape-config sections, and inlined rule content that belongs in separate reference files keep it mid-pack on efficiency and structure.

Suggestions

Remove the generic "Instructions" filler ("Clarify goals...", "Apply relevant best practices...") and replace it with a real sequenced workflow with explicit validate→fix→retry checkpoints.

Move full recording-rule and alert-rule catalogs into reference files (e.g. references/recording-rules.md, references/alert-rules.md) and link to them from a concise overview, eliminating the duplicated scrape-config examples.

Deduplicate the scrape configuration material that appears both inside prometheus.yml and again under "Scrape Configurations".

DimensionReasoningScore

Conciseness

Mostly efficient config examples, but the generic "Instructions" boilerplate ("Clarify goals, constraints, and required inputs") and redundancy between the inlined prometheus.yml and the later Scrape Configurations section add padding Claude does not need.

3 / 5

Actionability

Copy-paste-ready helm commands, docker-compose, full prometheus.yml, recording/alert rule YAML, promtool validation, and curl troubleshooting cover the common cases with fully executable guidance.

5 / 5

Workflow Clarity

Sections imply an install→configure→rules→validate order and a Validation section exists, but there is no explicit step sequence with checkpoints or a validate→fix→retry feedback loop woven through the workflow; the generic Instructions section adds no real sequence.

3 / 5

Progressive Disclosure

Headers are well organized, but this is a ~390-line monolithic SKILL.md with no bundle files and no one-level-deep references, inlining full recording-rule and alert-rule content that would fit better in separate reference files.

3 / 5

Total

14

/

20

Passed

Description

75%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 clear, third-person, and covers both what the skill does and when to use it with a Prometheus-specific niche. It sits comfortably above the midpoint but stops short of the top anchor due to slightly generic action wording and limited trigger synonym coverage.

Suggestions

Tighten the action list toward concrete verbs (e.g. "scrape metrics, define recording rules, configure alerts, set up service discovery") rather than the broad "collection, storage, and monitoring".

Expand the "Use when" clause with natural trigger variants users say (e.g. "scraping metrics", "setting up alerts", "recording rules", "Prometheus config").

DimensionReasoningScore

Specificity

Names the domain (Prometheus) and several concrete actions — "comprehensive metric collection, storage, and monitoring of infrastructure and applications" — with only minor gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Set up Prometheus for...") and when ("Use when implementing...") in third person, though the trigger list could be more concrete and varied to reach a 5.

4 / 5

Trigger Term Quality

The "Use when" clause surfaces natural phrases ("metrics collection", "monitoring infrastructure", "alerting systems") users would actually say, but misses common variants like scraping, recording rules, or alerts.

4 / 5

Distinctiveness Conflict Risk

Naming the specific tool (Prometheus) carves a clear niche with minimal conflict risk, though the broad "monitoring infrastructure" trigger could overlap slightly with general observability skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

rmyndharis/antigravity-skills

Path

skills/prometheus-configuration/SKILL.md

Revision

364ea63

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill