Skip to content
TrustedSkillsbeta
Back to all skills

Release Publishing Workflow

Checked
j0kz·vlatest·devops·MIT

Automates release publishing steps, from code promotion to deployment, streamlining DevOps workflows with pre-defined checks.

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 j0kz/mcp-agents --skill release-publishing-workflow -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

j0kz

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 j0kz/mcp-agents at 1d796f6ad8.

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

Commit
1d796f6ad8
Manifest
starter-kit/template/.claude/skills/release-publishing-workflow/SKILL.md
Scanned
4 files, 1,655 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

This skill automates software release publishing workflows. It handles tasks such as version bumping, tag creation in Git repositories, and deployment to various environments (e.g., staging, production). The workflow can be customized with different triggers and actions based on project needs.

When to use it

  • Automating a new feature release for a web application.
  • Deploying a bug fix to the production environment after testing.
  • Creating a repeatable process for releasing internal tools or libraries.
  • Managing releases across multiple repositories simultaneously.

Key capabilities

  • Version bumping (Semantic Versioning)
  • Git tag creation
  • Deployment to staging and production environments
  • Customizable triggers and actions

Example prompts

  • "Publish version 1.2.3 of the 'my-app' repository."
  • "Deploy the latest tagged commit from 'backend' repo to staging."
  • “Create a release candidate for the frontend application.”

Tips & gotchas

The skill requires access to Git repositories and deployment environments, so ensure proper credentials are configured. Customization options may require familiarity with scripting or configuration files depending on the specific workflow setup.