promql-validator

Validate PromQL syntax and flag anti-patterns with optimization recommendations.

7|3|Updated May 4, 2026
One-click install
npx skills add https://github.com/nopperabbo/codebuddy2api --skill promql-validator-nopperabbo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promql-validator
Source: https://github.com/nopperabbo/codebuddy2api/tree/main/opencode-config/skills/_archived/promql-validator
Command: npx skills add https://github.com/nopperabbo/codebuddy2api --skill promql-validator-nopperabbo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill validates Prometheus Query Language (PromQL) expressions for syntax correctness, identifies anti-patterns, and suggests performance improvements to improve reliability and efficiency of monitoring queries.

Core Features & Use Cases

  • Syntax validation: checks metric names, label matchers, durations, and structure.
  • Best-practice audit: flags common pitfalls such as missing rate() on counters, rate() on gauges, high cardinality, subquery inefficiencies, and quantile misuse; provides actionable remediation.
  • Recording-rule guidance: detects opportunities to extract complex or expensive queries into recording rules for reuse and performance.
  • Explanations and recommendations: returns plain-English explanations and concrete optimizations to help operators refine queries.
  • Works with both classic histograms and native histograms.

Quick Start

Provide a PromQL query to the validator to receive syntax validation and optimization suggestions.

Frequently Asked Questions about promql-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a PromQL query is correct and follows best practices?

PromQL validation checks syntax correctness and applies best-practice audits to identify anti-patterns like missing rate() on counters or subquery inefficiencies. It returns structured errors, warnings, and concrete optimization recommendations to improve query reliability.

What are common PromQL anti-patterns I should look for in my Prometheus queries?

Common PromQL anti-patterns include missing rate() on counters, applying rate() to gauges, subquery inefficiencies, and quantile misuse. Identifying these issues helps optimize query performance and ensures accurate metric analysis across classic and native histograms.

Can I validate PromQL expressions for both classic and native histograms?

Yes, PromQL validation supports both classic histograms and native histograms. It checks metric names, label matchers, and structures, while identifying specific histogram anti-patterns like quantile misuse to ensure accurate and efficient monitoring queries.

When should I extract a PromQL query into a recording rule?

You should extract a PromQL query into a recording rule when the query is complex or expensive to compute repeatedly. Validation tools can detect these opportunities and provide guidance to pre-compute expressions for reuse and improved dashboard performance.

Why does my Prometheus query using rate() on a gauge return unexpected results?

Applying rate() to a gauge metric is a common PromQL anti-pattern that causes unexpected results because gauges represent instantaneous values, not monotonically increasing counters. Validation identifies this misuse and recommends appropriate functions for your metric type.