Skip to content
TrustedSkillsbeta
Back to all skills

Prometheus Go Code Review

Checked
existential-birds·vlatest·devops·Apache-2.0

Helps with Go, code review as part of developing backend services and APIs workflows.

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 existential-birds/beagle --skill prometheus-go-code-review -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

existential-birds

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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 existential-birds/beagle at d1a74899fb.

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

Commit
d1a74899fb
Manifest
plugins/beagle-go/skills/prometheus-go-code-review/SKILL.md
Scanned
1 file, 159 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

prometheus-go-code-review

What it does

This skill enables AI agents to perform automated code reviews specifically for Go applications that interact with Prometheus. It analyzes source code to ensure metrics collection logic aligns with best practices and integrates correctly with the monitoring ecosystem.

When to use it

  • Before merging changes to a Go service that exposes new metrics endpoints.
  • When refactoring existing instrumentation to reduce cardinality or improve query performance.
  • To validate that label usage in metric definitions adheres to Prometheus naming conventions.
  • During CI/CD pipelines to catch instrumentation errors before they reach production.

Key capabilities

  • Analyzes Go code for proper metric registration and labeling.
  • Identifies potential issues with metric cardinality explosion.
  • Checks alignment with Prometheus data model standards.
  • Provides feedback on counter vs. gauge usage in Go implementations.

Example prompts

  • "Review this Go file for Prometheus instrumentation errors and suggest fixes."
  • "Analyze these metrics definitions for high cardinality risks and label best practices."
  • "Check if this new endpoint correctly registers counters and follows Prometheus naming conventions."

Tips & gotchas

Ensure your Go codebase includes the necessary Prometheus client libraries before running the review, as missing dependencies may lead to incomplete analysis. This skill focuses on code structure and metric definitions; it does not validate actual runtime behavior or scrape configurations.