Skip to content
TrustedSkillsbeta
Back to all skills

Release Health Gates

Checked
athola·vlatest·devops·MIT

Automates releasing deployments based on pre-defined health checks, ensuring only stable code reaches production and streamlining DevOps 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 athola/claude-night-market --skill release-health-gates -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

athola

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 athola/claude-night-market at 9045831255.

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

Commit
9045831255
Manifest
plugins/minister/skills/release-health-gates/SKILL.md
Scanned
3 files, 125 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 release-health-gates skill automates the process of evaluating and managing release health gates. It assesses key metrics, compares them against defined thresholds, and automatically opens or closes release progression based on these evaluations. This ensures releases only proceed when pre-defined conditions are met, minimizing risk and improving deployment reliability.

When to use it

  • Automated Go/No-Go Decisions: When you need a system that automatically determines if a release should proceed to the next stage based on health checks.
  • Pre-Deployment Validation: Before deploying code to production, verify critical metrics like error rates and latency are within acceptable limits.
  • Release Blocking: If key performance indicators fall below defined thresholds, prevent further release progression until issues are resolved.
  • Continuous Delivery Pipelines: Integrate with your CI/CD pipeline to enforce quality gates automatically.

Key capabilities

  • Metric evaluation against defined thresholds
  • Automated gate opening and closing based on evaluations
  • Release progression control

Example prompts

  • "Check the release health gates for version 1.2.3."
  • "What are the current status of the release health gates?"
  • "Open the 'performance' health gate if error rates are below 0.5%."

Tips & gotchas

The skill requires properly configured metrics and thresholds to function correctly. Ensure these are accurately defined and reflect your organization’s acceptable risk levels for releases.