Release Management

Name: Release Management
Author: yonatangross

Checked

yonatangross·vlatest·devops·MIT

Automates software release processes, including build triggering, deployment, and rollback, based on predefined workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add yonatangross/orchestkit --skill release-management -a claude-code

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

yonatangross

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 30 Sept 2026

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 yonatangross/skillforge-claude-plugin at 8b46ac9a60.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 8b46ac9a60
Manifest: src/skills/release-management/SKILL.md
Scanned: 24 files, 3,400 lines
Copies in repo: 2 — all of them scanned

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

This skill facilitates release management tasks, likely including planning, scheduling, and coordinating software releases. It can help automate aspects of the release process, ensuring smoother deployments and reducing potential errors. The specific capabilities aren't detailed in the provided source content, but it implies assistance with managing complex release cycles.

When to use it

You need to schedule a new version of your application for deployment.
You want to automate parts of your software release process.
You’re coordinating releases across multiple teams or environments.
You require help tracking the status and dependencies related to an upcoming release.

Key capabilities

Release planning
Scheduling
Coordination
Automation (implied)

Example prompts

"Schedule a release of version 2.1 for next Tuesday."
"What are the pending tasks for the v3.0 release?"
"Coordinate deployment to staging environment with the infrastructure team."

Tips & gotchas

The specific commands and functionalities will depend on the underlying tools this skill integrates with. Consult the skill's documentation (if available) for a complete list of supported actions and potential limitations.