New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Delete Remote Release

by muutot in muutot/Clipboard

Delete a remote git tag and/or its GitHub release draft — for example cleaning up a failed CI draft release left behind after re-tagging a version, or removing an orphaned/duplicate release tag.

AGPL-3.0Auto-check passedDevelopment

Install Delete Remote Release

skills CLI
$ npx skills add muutot/Clipboard --skill delete-remote-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install muutot/Clipboard delete-remote-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/muutot/Clipboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/delete-remote-release .claude/skills/delete-remote-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
delete-remote-release
GitHub stars
61
Token cost
~1k tokens
SKILL.md length
489 words
Files
2 (incl. scripts)
Skills in repo
3
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Delete a remote git tag and/or its GitHub release draft — for example cleaning up a failed CI draft release left behind after re-tagging a version, or removing an orphaned/duplicate release tag.

  • Works in 2 steps: git push access to the target remote… → A GitHub token for the release-draft API…
  • Asks to remove a remote (published) git tag
  • SKILL.md covers Purpose, When to use, Prerequisites and How to use, plus 2 more sections
  • Runs Python scripts from its folder; calls git, python and gh; needs GITHUB_TOKEN

What it does

Delete Remote Release is an agent skill from muutot/Clipboard. Delete a remote git tag and/or its GitHub release draft — for example cleaning up a failed CI draft release left behind after re-tagging a version, or removing an orphaned/duplicate release tag. This skill should be used when the user asks to remove a remote (published) git tag, delete a GitHub release draft, or undo a botched release tag — e.g. "delete the remote v1.4.0 tag and its draft release", "remove the orphaned release draft", "clean up the tag after re-tagging". GitHub only.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/delete_remote_release.py`).

It sits in Development, covering Git workflow. It works with GitHub and Git. The repository describes itself as: High performance·Local first·Full platform clipboard manager. The licence is AGPL-3.0.

When your agent uses it

  • Asks to remove a remote (published) git tag
  • Delete a GitHub release draft
  • Undo a botched release tag — e.g

Example prompts

  • “delete the remote v1.4.0 tag and its draft release”
  • “remove the orphaned release draft”
  • “clean up the tag after re-tagging”
  • “/delete-remote-release”

Requirements

  • Python 3
  • A credential in GITHUB_TOKEN

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. git push access to the target remote (for tag deletion). Uses the user's normal git
  2. A GitHub token for the release-draft API delete. The script resolves it in this

What it can do on your machine

Read from SKILL.md and the folder at commit 6f722cc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • python
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Delete Remote Release loads about 1k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 489 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from muutot/Clipboard at commit 6f722cc, republished under its AGPL-3.0 licence (© muutot). 489 words, ~1,038 tokens.

Download SKILL.mdSave it as .claude/skills/delete-remote-release/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
delete-remote-release
description
Delete a remote git tag and/or its GitHub release draft — for example cleaning up a failed CI draft release left behind after re-tagging a version, or removing an orphaned/duplicate release tag. This skill should be used when the user asks to remove a remote (published) git tag, delete a GitHub release draft, or undo a botched release tag — e.g. "delete the remote v1.4.0 tag and its draft release", "remove the orphaned release draft", "clean up the tag after re-tagging". GitHub only.
agent_created
true

delete-remote-release

Purpose

Remove a remote git tag and/or its GitHub draft release for a given version. A botched or re-tagged release often leaves a stale vX.Y.Z draft Release on GitHub that blocks the next tauri-action run ("release already exists"). This skill deletes both the tag and the draft cleanly so the release workflow can be re-triggered.

Key fact: deleting a git tag does NOT delete the GitHub Release object. Both must be removed, which is exactly what this skill does.

When to use

  • The user asks to delete a remote/remote git tag (e.g. v1.4.0).
  • The user mentions a "draft release", "orphaned release", or a failed CI run that left a draft behind.
  • After re-tagging a release (version-release --regenerate), to clear the old remote tag and draft before re-pushing.

Prerequisites

  1. git push access to the target remote (for tag deletion). Uses the user's normal git credentials — no extra setup.
  2. A GitHub token for the release-draft API delete. The script resolves it in this order: $GITHUB_TOKEN env → gh auth token → git credential fill (github.com) → ~/.workbuddy/secrets/github_token. If none is found, tag deletion still runs; the draft delete is skipped with instructions. A fine-grained or classic PAT with repo (or public_repo) scope is sufficient.

How to use

Run the bundled script from the repository root. By default it is dry-run — it shows what would be deleted and changes nothing.

bash
# 1) See what would be deleted (safe, no changes):
python skills/delete-remote-release/scripts/delete_remote_release.py --tag v1.4.0

# 2) Actually delete (IRREVERSIBLE):
python skills/delete-remote-release/scripts/delete_remote_release.py --tag v1.4.0 --yes

Parameters:

  • --tag <tag> (required): the tag to clean up, e.g. v1.4.0. Never guessed.
  • --remote <name>: git remote to delete the tag from. Default: github if present, else origin.
  • --repo <owner/repo>: GitHub repo for the API call. Default: derived from the remote URL.
  • --tag-only: delete only the remote tag, skip the draft release.
  • --draft-only: delete only the GitHub draft release, skip the tag.
  • --dry-run: force dry-run (no changes) even if --yes is given.
  • --yes: perform the actual deletions. Required for any change.
Show full SKILL.md (181 more words)Show less

Safety rules (enforce these)

  • Always run dry-run first and show the user exactly what will be deleted before passing --yes.
  • Require an explicit --tag — never infer or default a tag name.
  • Deleting a remote tag and a draft release is not reversible remotely. Confirm with the user before --yes.
  • Only draft releases matching the tag are auto-deleted. If a published (non-draft) release shares the tag, the script warns and leaves it alone — deleting a published release is a bigger deal and must be a conscious, separate decision.
  • Published releases are never auto-deleted. If the user wants a published release removed, confirm explicitly and act deliberately.

Companion workflow (re-tagging a release)

When used right after version-release --regenerate (which re-creates the local tag on the fixed commit), the typical sequence is:

  1. delete-remote-release --tag v1.4.0 --yes — remove the old remote tag + draft.
  2. git push origin <branch> --force-with-lease — push the new release commit.
  3. git push origin v1.4.0 --force — push the re-created tag, re-triggering CI on the fixed workflow.

(Per project convention, the remote push is performed by the user, not the agent.)

© muutot, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in skills/delete-remote-release of muutot/Clipboard.

  • SKILL.md
  • scripts/delete_remote_release.py

Open the folder on GitHubat commit 6f722cc

Compare with similar skills

Delete Remote Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Delete Remote Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Delete Remote Release this skillmuutot/Clipboard61—~1kAutomated safety check: PassAGPL-3.0
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT

Similar skills

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Pascal Editor PR Opener

    pascalorg/editor

    Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain.

    25k GitHub stars~619 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from muutot/Clipboard

  • Version Release

    muutot/Clipboard

    Automated version bumping and release workflow for Clipboard Desktop.

    61 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Clipboard Dev

    muutot/Clipboard

    Develop and maintain the Clipboard Desktop repository. An agent skill from muutot/Clipboard.

    61 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Delete Remote Release

What does Delete Remote Release do?

Delete a remote git tag and/or its GitHub release draft — for example cleaning up a failed CI draft release left behind after re-tagging a version, or removing an orphaned/duplicate release tag. Delete Remote Release is an agent skill from muutot/Clipboard. Delete a remote git tag and/or its GitHub release draft — for example cleaning up a failed CI draft release left behind after re-tagging a version, or removing an orphaned/duplicate release tag.

When should I use Delete Remote Release?

Delete Remote Release fits situations like: asks to remove a remote (published) git tag; delete a GitHub release draft; undo a botched release tag — e.g.

How do I install Delete Remote Release in Claude Code?

Run `npx skills add muutot/Clipboard --skill delete-remote-release -a claude-code`. Or copy the skill folder (skills/delete-remote-release in muutot/Clipboard) into .claude/skills/delete-remote-release in your project. Claude Code loads it when a task matches its description.

How do I install Delete Remote Release in Codex?

Run `npx skills add muutot/Clipboard --skill delete-remote-release -a codex`. Or copy the skill folder (skills/delete-remote-release in muutot/Clipboard) into .agents/skills/delete-remote-release in your project. Codex loads it when a task matches its description.

Can I use Delete Remote Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add muutot/Clipboard --skill delete-remote-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/delete-remote-release, .gemini/skills/delete-remote-release, .github/skills/delete-remote-release and .opencode/skills/delete-remote-release in your project.

What does Delete Remote Release need to run?

Going by SKILL.md and its folder, Delete Remote Release needs Python for the scripts in its folder, the command-line tools its instructions call (git, python and gh) and credentials named GITHUB_TOKEN. Our summary lists: Python 3; A credential in GITHUB_TOKEN.

Does Delete Remote Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Delete Remote Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Delete Remote Release use?

Delete Remote Release is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Delete Remote Release use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Delete Remote Release?

Skills that share tags, products or a category with Delete Remote Release: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Release Bump (jamiepine/voicebox, 57k stars) and Create Pull Request with Work Item ID (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Delete Remote Release?

muutot (a GitHub user) maintains it in muutot/Clipboard, which has 61 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 10, 2026.

Source: muutot/Clipboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.