Skip to content
TrustedSkillsbeta
Back to all skills

Release

Checked
tobi·vlatest·devops·MIT

This "Release" skill automates deployment pipelines, streamlining software releases and ensuring consistent, reliable updates for your applications.

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 tobi/qmd --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

tobi

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 tobi/qmd at 04e4dbd824.

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

Commit
04e4dbd824
Manifest
skills/release/SKILL.md
Scanned
3 files, 305 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

The tobi-release skill enables AI agents to manage software deployment lifecycles by interacting with the Tobi platform. It allows agents to trigger builds, promote artifacts between environments, and verify release statuses directly through API calls.

When to use it

  • Automating nightly production deployments after successful staging validation.
  • Coordinating multi-environment rollouts (e.g., dev → staging → prod) without manual intervention.
  • Triggering emergency hotfixes when critical bugs are identified in live services.
  • Scheduling maintenance windows to release updates during low-traffic periods.

Key capabilities

  • Initiates new builds from source code repositories.
  • Promotes artifacts across different deployment environments.
  • Retrieves real-time status of ongoing releases and build jobs.
  • Validates artifact integrity before promotion to production.

Example prompts

  • "Deploy version 2.4.1 to the staging environment and notify me once the build completes."
  • "Check the current status of the release pipeline for the payment service."
  • "Promote the latest approved artifact from staging to production during the scheduled maintenance window."

Tips & gotchas

Ensure your AI agent has valid API credentials with appropriate permissions to access the Tobi platform before attempting deployments. Always verify environment names and version tags in your prompts to prevent accidental overwrites or incorrect promotions.