Skip to content
TrustedSkillsbeta
Back to all skills

Release

Checked
max-sixty·vlatest·devops

Automates deployments to various environments, streamlining releases and reducing manual errors for faster software delivery.

Repository

Install on your platform

This skill no longer installs under the name release. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

max-sixty

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 max-sixty/worktrunk at aff6bc3b13.

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

Commit
aff6bc3b13
Manifest
.claude/skills/release/SKILL.md
Scanned
3 files, 629 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 max-sixty-release skill enables AI agents to trigger deployment workflows directly within the Worktrunk environment. It automates the process of pushing code changes from a repository to production or staging environments based on defined triggers and configurations.

When to use it

  • Automate deployments immediately after successful CI pipeline runs.
  • Trigger releases when specific branches are merged into main or develop.
  • Deploy updates to multiple environments (e.g., staging, prod) with one command.
  • Schedule recurring release tasks for maintenance windows.

Key capabilities

  • Connects directly to Worktrunk deployment pipelines.
  • Supports environment-specific configuration targeting.
  • Integrates with Git hooks and webhook events.
  • Provides status updates on release progress.

Example prompts

  • "Deploy the latest changes from the 'feature/auth' branch to the staging environment."
  • "Trigger a production release after verifying all tests pass in the CI pipeline."
  • "Schedule a maintenance release for this weekend at 2 AM UTC."

Tips & gotchas

Ensure your Worktrunk account has appropriate permissions before enabling automated releases. Always validate that your .worktrunk.yml configuration file is correctly formatted to avoid failed deployments.