Skip to content
TrustedSkillsbeta
Back to all skills

Guarding Deployments

Checked
roelofvheeren·vlatest·devops

Automatically monitors deployment pipelines for failures and alerts, ensuring smooth releases and rapid issue resolution in 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 roelofvheeren/elvison-os --skill guarding-deployments -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

roelofvheeren

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 roelofvheeren/elvison-os at 07d248ea99.

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

Commit
07d248ea99
Manifest
.agent/skills/deployment-guard/SKILL.md
Scanned
2 files, 73 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 guarding-deployments skill automates deployment checks and approvals. It verifies that deployments meet pre-defined criteria, such as passing tests or adhering to security policies, before allowing them to proceed. This helps prevent faulty or insecure code from reaching production environments, improving overall system stability and reducing risk.

When to use it

  • Automated Release Pipelines: Integrate with CI/CD pipelines to automatically gate deployments based on defined rules.
  • Security Compliance: Enforce security policies by requiring specific checks (e.g., vulnerability scans) before deployment.
  • Staging Environments: Ensure that changes are thoroughly tested and validated in staging environments before promotion to production.
  • Pre-Production Approvals: Require manual approval after automated checks pass, providing a final layer of oversight.

Key capabilities

  • Automated deployment verification
  • Customizable check criteria
  • Integration with CI/CD pipelines
  • Manual approval workflows
  • Security policy enforcement

Example prompts

  • "Check if the latest build passes all integration tests before deploying to staging."
  • "Enforce that deployments to production must have a security vulnerability scan result below 50."
  • “Require manual approval for any deployment exceeding a certain size.”

Tips & gotchas

The skill requires configuration of specific checks and policies. Ensure these are accurately defined to avoid blocking valid deployments or allowing problematic ones through.