Skip to content
TrustedSkillsbeta
Back to all skills

Github Release Management

Checked
proffesor-for-testing·vlatest·backend·MIT

Helps with testing, GitHub, management as part of automating DevOps pipelines and CI/CD workflows workflows.

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 proffesor-for-testing/sentinel-api-testing --skill github-release-management -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

proffesor-for-testing

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 proffesor-for-testing/sentinel-api-testing at 704f47fbc4.

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

Commit
704f47fbc4
Manifest
.claude/skills/github-release-management/SKILL.md
Scanned
1 file, 1,012 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

This skill automates GitHub release management tasks. It can create, edit, and delete releases, as well as manage associated assets like binaries or documentation. The agent interacts directly with your GitHub repository using the GitHub API to streamline the release process.

When to use it

  • Automating repetitive release creation steps for software projects.
  • Generating draft releases with placeholder notes for review before final publication.
  • Updating existing releases with new assets or modified release notes.
  • Cleaning up old, unused releases from your GitHub repository.

Key capabilities

  • Create GitHub Releases
  • Edit Existing GitHub Releases
  • Delete GitHub Releases
  • Manage Release Assets (upload/delete)

Example prompts

  • "Create a draft release for version 1.2.3 with the title 'Release 1.2.3' and notes: 'Bug fixes and minor improvements.'"
  • "Update the existing release v1.0 with the asset 'documentation.pdf'."
  • "Delete the release tagged as 'beta-1'."

Tips & gotchas

  • Requires appropriate GitHub API access tokens to authenticate and perform actions on your repositories. Ensure the token has write permissions for the target repository.