Skip to content
TrustedSkillsbeta
Back to all skills

Release

Checked
ekroon·vlatest·devops

This "Release" skill automates deployment workflows, streamlining application releases and reducing manual errors for efficient DevOps practices.

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 ekroon/tabctl --skill release -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

ekroon

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 ekroon/tabctl at d83404a96c.

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

Commit
d83404a96c
Manifest
skills/release/SKILL.md
Scanned
1 file, 221 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 ekroon-release skill automates software releases. It handles tasks such as tagging repositories, creating release branches, and deploying to staging or production environments based on defined workflows. This ensures a consistent and repeatable release process, reducing errors and improving efficiency.

When to use it

  • Automating the deployment of new versions of your application to a testing environment.
  • Creating tagged releases in Git repositories after successful builds.
  • Triggering deployments to production based on specific branch merges or tag creations.
  • Managing release branches for coordinated feature rollouts and hotfixes.

Key capabilities

  • Repository tagging
  • Release branch creation
  • Deployment automation
  • Workflow definition

Example prompts

  • "Create a release tag 'v1.2.3' in the my-repo repository."
  • "Deploy to staging after merging into the release/1.x branch."
  • “Trigger a production deployment when tag ‘v2.*’ is created.”

Tips & gotchas

The skill requires appropriate permissions within your Git repositories and deployment environments. Ensure that the configured workflows accurately reflect your desired release process to avoid unintended deployments.