Skip to content
TrustedSkillsbeta
Back to all skills

Agent Release Manager

Checked
ruvnet·vlatest·devops·MIT

Automates software release processes, managing deployments, approvals, and rollbacks based on predefined 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 ruvnet/ruflo --skill agent-release-manager --full-depth -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

ruvnet

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 ruvnet/claude-flow at 49da6ecc44.

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

Commit
49da6ecc44
Manifest
.agents/skills/agent-release-manager/SKILL.md
Scanned
1 file, 356 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 agent-release-manager skill automates and streamlines the process of releasing AI agents. It handles tasks such as versioning, packaging, deployment to various environments (staging, production), and managing release notes. This reduces manual effort and potential errors associated with agent releases, ensuring a more consistent and reliable deployment pipeline.

When to use it

  • Automated Deployments: When you need to regularly deploy new versions of your AI agents without manual intervention.
  • Multi-Environment Releases: For deploying agents across different environments like staging for testing before production release.
  • Release Note Generation: To automatically create and manage release notes based on changes in agent versions.
  • Version Control Integration: When you want to tie releases directly to specific code commits or branches within your version control system.

Key capabilities

  • Versioning of AI agents
  • Packaging for deployment
  • Deployment to staging environments
  • Deployment to production environments
  • Release note management

Example prompts

  • "Create a new release for agent 'OrderProcessor' with version 1.2.0."
  • "Deploy the latest version of 'CustomerSupportBot' to the staging environment."
  • “Generate release notes for agent ‘DataAnalyzer’ version 2.0, highlighting bug fixes and feature additions.”

Tips & gotchas

The skill requires integration with your existing version control system (e.g., Git) and deployment infrastructure. Ensure proper configuration of these integrations before use to avoid deployment failures or incorrect versioning.