Skip to content
TrustedSkillsbeta
Back to all skills

Blue Green Deploy

Checked
bagelhole·vlatest·devops·MIT

Automates blue/green deployments using Bagelhole's AI, minimizing downtime and risk during application updates.

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 bagelhole/devops-security-agent-skills --skill blue-green-deploy -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

bagelhole

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 bagelhole/devops-security-agent-skills at 0365f57a07.

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

Commit
0365f57a07
Manifest
devops/release/blue-green-deploy/SKILL.md
Scanned
1 file, 478 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 blue-green deploy skill automates the process of deploying new versions of applications while minimizing downtime and risk. It creates two identical environments – "blue" (live) and "green" (staging). The new version is deployed to the green environment, tested, and then traffic is switched from blue to green, effectively making the new version live.

When to use it

  • Deploying a new feature or bug fix to a production application with minimal disruption.
  • Performing risky deployments where immediate rollback capabilities are crucial.
  • Automating release processes for faster iteration cycles and reduced manual effort.
  • Testing new versions of an application in a production-like environment before full rollout.

Key capabilities

  • Environment provisioning (blue & green)
  • Automated deployment to staging environment
  • Traffic switching between environments
  • Rollback functionality

Example prompts

  • "Deploy the latest version of the website to the green environment."
  • "Test the new checkout flow in the green environment and report any errors."
  • "Switch traffic from the blue environment to the green environment after successful testing."

Tips & gotchas

The skill requires access to both environments (blue and green) and appropriate deployment credentials. Ensure proper monitoring is set up on both environments to quickly identify and address issues post-deployment.