Skip to content
TrustedSkillsbeta
Back to all skills

Release

Checked
freenet·vlatest·devops·LGPL-3.0

Automates deployments to various environments, streamlining your DevOps workflows and accelerating application releases for faster delivery.

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 freenet/freenet-agent-skills --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

freenet

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 freenet/freenet-agent-skills at e3f2f96aa6.

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

Commit
e3f2f96aa6
Manifest
skills/release/SKILL.md
Scanned
1 file, 171 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 freenet-release skill automates the process of releasing software, specifically within the Freenet ecosystem. It handles tasks such as building release candidates, managing version numbers, and potentially deploying to staging or production environments. This allows for streamlined and repeatable release workflows.

When to use it

  • Automating nightly builds of Freenet releases for testing purposes.
  • Preparing a new stable release candidate for distribution.
  • Triggering deployment pipelines after successful build verification.
  • Managing version bumping during the development lifecycle.

Key capabilities

  • Release Candidate Generation
  • Version Number Management
  • Automated Build Processes
  • Deployment Automation (potential)

Example prompts

  • "Create a release candidate for Freenet version 1.15.3."
  • "Bump the Freenet version number to 1.16.0-beta1."
  • "Initiate the build process for the latest development branch."

Tips & gotchas

This skill likely requires a working knowledge of Freenet's build system and release procedures. Successful execution may depend on proper configuration of environment variables and access to necessary repositories.