Skip to content
TrustedSkillsbeta
Back to all skills

Release

Checked
parcadei·vlatest·devops·MIT

This "Release" skill automates deployment pipelines, streamlining software delivery 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 parcadei/continuous-claude-v3 --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

parcadei

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 parcadei/continuous-claude-v3 at d07ff4b06b.

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

Commit
d07ff4b06b
Manifest
.claude/skills/release/SKILL.md
Scanned
1 file, 219 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 parcadei-release skill enables AI agents to manage software deployments within the parcadei/continuous-claude-v3 environment. It automates the process of preparing, verifying, and pushing new versions of code or artifacts to production targets.

When to use it

  • Triggering automated deployment pipelines after a successful build or code review.
  • Rolling out configuration updates or hotfixes to live continuous-claude-v3 instances.
  • Managing version control workflows for specific releases in the arcadei ecosystem.
  • Coordinating release notes generation alongside artifact distribution.

Key capabilities

  • Integration with the parcadei/continuous-claude-v3 infrastructure stack.
  • Automated release lifecycle management from staging to production.
  • Support for continuous integration and deployment (CI/CD) workflows.
  • Version tracking and artifact handling specific to the arcadei platform.

Example prompts

  • "Initiate a release for version 2.4.0 of the Claude v3 model using the standard deployment pipeline."
  • "Verify the latest build artifacts and push them to the production environment if all tests pass."
  • "Rollback the previous release due to critical issues found in the last deployment."

Tips & gotchas

Ensure your agent has appropriate permissions within the parcadei/continuous-claude-v3 workspace before attempting a release. This skill is tightly coupled with the specific infrastructure of that project, so it may not function outside that context without significant modification.