Skip to content
TrustedSkillsbeta
Back to all skills

Release Manager

Listed
borghei·vlatest·devops

This Release Manager skill automates deployment workflows, streamlining releases and reducing errors for faster, more reliable software delivery.

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 borghei/claude-skills --skill release-manager -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

borghei

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 3 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.datadog.com, api.ourapp.com, staging.ourapp.com.

    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

    github.comsource hostapi.ourapp.comundeclaredstaging.ourapp.comundeclaredapi.datadog.comundeclared

    What it found (3 of 5)

    • engineering/release-manager/references/hotfix-procedures.md:317contacts api.ourapp.com
      curl -f https://api.ourapp.com/health
    • engineering/release-manager/references/hotfix-procedures.md:427contacts api.ourapp.com
      curl -s https://api.ourapp.com/health | jq '.'
    • engineering/release-manager/references/hotfix-procedures.md:393contacts staging.ourapp.com
      curl -f https://staging.ourapp.com/api/health
  • 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 borghei/claude-skills at 4a698e8d07.

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

Scanned
16 files, 4,506 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 borghei-release-manager skill automates software release management tasks. It handles versioning, tagging, and deployment processes based on defined workflows. This reduces manual effort and potential errors associated with releasing new versions of applications.

When to use it

  • Automating the release process for a new feature or bug fix.
  • Managing releases across multiple environments (e.g., development, staging, production).
  • Ensuring consistent tagging and versioning practices within a software project.
  • Streamlining deployments based on predefined workflows.

Key capabilities

  • Automated Versioning
  • Tagging
  • Deployment Workflow Management

Example prompts

  • "Initiate release v1.2.0 for the 'backend' service."
  • "Deploy version 1.3.1 to the production environment."
  • "Create a tag for the current commit and increment the version number."

Tips & gotchas

The skill requires pre-configured deployment workflows and access credentials to relevant repositories and environments. Ensure these are properly set up before using the skill, or it may fail during execution.