Skip to content
TrustedSkillsbeta
Back to all skills

Promql Validator

Listed
akin-ozer·vlatest·devops·Apache-2.0

Validates Prometheus queries (PromQL) for correctness and potential errors, ensuring data integrity and accurate monitoring insights.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add akin-ozer/cc-devops-skills --skill promql-validator -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

akin-ozer

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 5 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: grafana.com, iximiuz.com, prometheus.io, stackoverflow.com, www.robustperception.io.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    stackoverflow.comundeclaredwww.robustperception.ioundeclaredgrafana.comundeclarediximiuz.comundeclaredprometheus.ioundeclared

    What it found (3 of 6)

    • devops-skills-plugin/skills/promql-validator/scripts/check_best_practices.py:609contacts stackoverflow.com
      Per https://stackoverflow.com/questions/53191746/prometheus-absent-function
    • devops-skills-plugin/skills/promql-validator/scripts/check_best_practices.py:610contacts www.robustperception.io
      and https://www.robustperception.io/functions-to-avoid/
    • devops-skills-plugin/skills/promql-validator/scripts/check_best_practices.py:644contacts grafana.com
      Per https://grafana.com/blog/2024/12/13/promql-vector-matching-what-it-is-and-how-it-affects-your-prometheus-queries/

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned akin-ozer/cc-devops-skills at 276af751e6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
276af751e6
Manifest
devops-skills-plugin/skills/promql-validator/SKILL.md
Scanned
6 files, 3,611 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The promql-validator skill validates PromQL queries, ensuring they are syntactically correct and can be executed without errors. It provides feedback on query structure, variable usage, and potential issues that could prevent successful execution against a Prometheus data source. This helps in debugging and improving the reliability of monitoring dashboards and alerting rules.

When to use it

  • Debugging PromQL queries: When you're building or modifying alerts or dashboard panels and unsure if your query is valid.
  • Automated testing: Integrate into CI/CD pipelines to automatically validate changes to PromQL configurations before deployment.
  • Learning PromQL: Use as a learning tool to understand the syntax and common errors in PromQL queries.
  • Code review: Validate PromQL code during peer reviews to catch potential issues early on.

Key capabilities

  • PromQL query validation
  • Syntax error detection
  • Error message reporting

Example prompts

  • "Can you validate this PromQL query: up{job="my-app"}?"
  • "Is this a valid Prometheus query: sum(http_requests_total{job="api"}) by (endpoint)"?"
  • "Check the syntax of this PromQL expression and tell me if there are any errors: rate(http_requests_total[5m]) > 10."

Tips & gotchas

The skill requires a basic understanding of PromQL syntax to interpret the validation results effectively. While it checks for syntax, it doesn't guarantee that the query will return meaningful data or behave as expected against your specific Prometheus setup.