Agent skill

Release Revoke

by BlackBeltTechnology in BlackBeltTechnology/pi-agent-dashboard

Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally…

MITAuto-check passedDevOps & Cloud

Install Release Revoke

skills CLI

$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a claude-code

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

GitHub CLI

$ gh skill install BlackBeltTechnology/pi-agent-dashboard release-revoke --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/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pi/skills/release-revoke .claude/skills/release-revoke && 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/

Paste into Claude Code

Install the "release-revoke" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/.pi/skills/release-revoke into .claude/skills/release-revoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-revoke", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/.pi/skills/release-revoke

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install BlackBeltTechnology/pi-agent-dashboard release-revoke --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.pi/skills/release-revoke .agents/skills/release-revoke && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release-revoke" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/.pi/skills/release-revoke into .agents/skills/release-revoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-revoke", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install BlackBeltTechnology/pi-agent-dashboard release-revoke --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.pi/skills/release-revoke .cursor/skills/release-revoke && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release-revoke" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/.pi/skills/release-revoke into .cursor/skills/release-revoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-revoke", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/BlackBeltTechnology/pi-agent-dashboard.git --path .pi/skills/release-revoke

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install BlackBeltTechnology/pi-agent-dashboard release-revoke --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.pi/skills/release-revoke .gemini/skills/release-revoke && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "release-revoke" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/.pi/skills/release-revoke into .gemini/skills/release-revoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-revoke", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install BlackBeltTechnology/pi-agent-dashboard release-revoke

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.pi/skills/release-revoke .github/skills/release-revoke && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "release-revoke" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/.pi/skills/release-revoke into .github/skills/release-revoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-revoke", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install BlackBeltTechnology/pi-agent-dashboard release-revoke --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.pi/skills/release-revoke .opencode/skills/release-revoke && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release-revoke" agent skill from https://github.com/BlackBeltTechnology/pi-agent-dashboard/tree/develop/.pi/skills/release-revoke into .opencode/skills/release-revoke/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-revoke", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: release-revoke
GitHub stars: 315
Token cost: ~1.7k tokens
SKILL.md length: 597 words
Files: 2
Skills in repo: 70
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally…

Works in 8 steps: Select version → Inspect current state → Confirm intent → …
The user says revoke release
SKILL.md covers Step 1 — Select version, Step 2 — Inspect current state, Step 3 — Confirm intent and Step 4 — Delete GitHub Release, plus 5 more sections
Calls git, npm and gh

What it does

Release Revoke is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish vX.Y.Z", "yank release".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `SKILL.md.AGENTS.md`).

It sits in DevOps & Cloud, covering Git workflow. It works with npm, Git and GitHub. The repository describes itself as: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote… The licence is MIT.

When your agent uses it

The user says revoke release
Rollback release
Unpublish vX.Y.Z

Example prompts

“revoke release”
“rollback release”
“delete release”
“/release-revoke”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Select version
Inspect current state
Confirm intent
Delete GitHub Release
Delete git tag
npm deprecate
Offer to revert the release commit
Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 7a2d171. 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
Shell commands in SKILL.md call:
- git
- npm
- 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, npm 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Revoke loads about 1.7k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 597 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from BlackBeltTechnology/pi-agent-dashboard at commit 7a2d171, republished under its MIT licence (© BlackBeltTechnology). 597 words, ~1,673 tokens.

Download SKILL.mdSave it as .claude/skills/release-revoke/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: release-revoke
description: Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (`npm unpublish` is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish vX.Y.Z", "yank release".
license: MIT
metadata.author: pi-dashboard
metadata.version: 1.0

Revoke a pi-agent-dashboard Release

This skill undoes a release cut by the release-cut skill. It handles three layers independently because they have different semantics:

Layer	Revocable?	Mechanism
GitHub Release	Yes (draft or published)	`gh release delete`
Git tag	Yes	`git push --delete` + `git tag -d`
Electron artifacts	Yes (deleted with release)	handled by `gh release delete`
npm package	Effectively permanent	`npm deprecate` (NOT `unpublish`)

Key fact about npm: npm unpublish is blocked 72h after publish, or any time the version has dependents. The right "revoke" for an npm release is npm deprecate, which leaves the tarball in place but marks it with a warning visible to anyone who tries to install it.

Step 1 — Select version

Run:

bash

git tag -l 'v*' | sort -V | tail -10

Use AskUserQuestion (select) showing the last 10 tags. Do NOT auto-pick.

Store the chosen version as <version> (with the leading v).

Step 2 — Inspect current state

bash

gh release view <version> --json isDraft,publishedAt,assets,url 2>/dev/null || echo "NO_RELEASE"
git tag -l <version>                         # local tag exists?
git ls-remote --tags origin <version>        # remote tag exists?
npm view @blackbelt-technology/pi-dashboard@${version#v} version 2>/dev/null || echo "NOT_ON_NPM"

Parse results and report to the user:

Whether GitHub Release exists (draft vs published)
Whether the tag exists locally / on origin
Whether this version is on npm

Step 3 — Confirm intent

Use AskUserQuestion (confirm) with a full impact preview, e.g.:

About to revoke <version>:
  • GitHub Release: PUBLISHED — will be deleted (artifacts gone)
  • Git tag: exists locally + on origin — will be deleted from both
  • npm: published <N> days ago — will be deprecated
         (npm unpublish not possible: > 72h old / has dependents)

This is PARTIALLY REVERSIBLE:
  • GitHub Release + tag can be re-created by re-tagging.
  • npm deprecation CAN be reversed with `npm deprecate <pkg>@<v> ""`.
  • npm version number is burned — cannot republish same version.

Proceed?

Refuse to continue without explicit confirmation.

Step 4 — Delete GitHub Release

Only if Step 2 showed the release exists:

bash

gh release delete <version> --yes --cleanup-tag=false

--cleanup-tag=false is important — we delete the tag ourselves in Step 5 so the ordering is explicit.

Step 5 — Delete git tag

bash

git push --delete origin <version>    # remote (only if it exists)
git tag --delete <version>            # local  (only if it exists)

Wrap each in an existence check — don't fail if already gone.

Step 6 — npm deprecate

Ask for a deprecation message (AskUserQuestion input), defaulting to:

Deprecated — see https://github.com/BlackBeltTechnology/pi-agent-dashboard/releases for a newer version.

Then run (only if Step 2 confirmed it's on npm):

bash

npm deprecate @blackbelt-technology/pi-dashboard@${version#v} "<message>"

Verify:

bash

npm view @blackbelt-technology/pi-dashboard@${version#v} deprecated

Should echo the message back.

Note: requires the user to be logged in as a maintainer (npm whoami + having publish rights on the package). If the command fails with auth error, surface it and ask the user to run npm login then retry this step.

Step 7 — Offer to revert the release commit

Check if the latest commit on develop is the release commit:

bash

git log -1 --format="%s"    # should be "chore(release): <version>" if yes

If yes, use AskUserQuestion (confirm) to offer:

bash

git revert HEAD --no-edit
git push origin develop

Explain: this restores ## [Unreleased] as the target for the next release and restores the pre-release package.json versions.

If the release commit is NOT the latest (other commits on top), do not revert automatically — surface the situation and let the user decide. Offer manual guidance:

Revert ad-hoc with git revert <sha> + resolve conflicts
Or leave the version bump in place and bump to the next version on the next release

Show full SKILL.md (199 more words)Show less

Step 8 — Summary

Print a final report:

Revocation complete for <version>:
  ✅ GitHub Release deleted (was: draft|published|absent)
  ✅ Git tag deleted from origin + local (was: present|absent)
  ✅ npm deprecated: "<message>"   [or: skipped — not on npm]
  ✅ Release commit reverted       [or: skipped — not the latest commit]

Note: the GitHub Pages site still advertises <version> until the next
release (or a manual workflow_dispatch of deploy-site.yml).

Guardrails

Never npm unpublish without asking. Even within 72h, it breaks anyone who happens to have installed the broken version. Deprecation is always the safer default.
Never skip confirmation. Every destructive step gets its own AskUserQuestion.
Never force-push. All deletions are explicit, non-history-rewriting operations.
Handle partial state gracefully. If the tag exists but no release, or release exists but no tag, or npm exists but tag doesn't — delete only what exists. Never error on "already gone".
If the release was auto-triggered but CI failed mid-matrix (e.g. npm published but Electron build failed), this skill is still the right tool — it will deprecate npm and delete the partial draft.
Published production releases self-distribute. Since fix-electron-auto-update-pipeline, production tags (vX.Y.Z) publish immediately (not draft) and carry latest*.yml update metadata. gh release delete removes the release, but electron-updater clients that already polled /releases/latest may have cached or downloaded it. Deleting the release stops NEW clients resolving it; it does NOT recall an update already pulled. To supersede a bad published release, cut a higher production tag (vX.Y.Z+1) so clients update forward — do not rely on deletion alone. Pre-release tags stay drafts and have no such reach.

Files

SKILL.md and 1 other file in .pi/skills/release-revoke of BlackBeltTechnology/pi-agent-dashboard.

SKILL.md
SKILL.md.AGENTS.md

Open the folder on GitHubat commit 7a2d171

Compare with similar skills

Release Revoke 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.

Release Revoke compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Revoke this skillBlackBeltTechnology/pi-agent-dashboard	315	—	~1.7k	Automated safety check: Pass	MIT	today
Hunk Release Workflowmodem-dev/hunk	9.6k	—	~3.8k	Automated safety check: Pass	MIT	3 days ago
ZCF Release AutomationUfoMiao/zcf	6.1k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
ClawRouter Release ChecklistBlockRunAI/ClawRouter	6.6k	—	~1.4k	Automated safety check: Pass	MIT	5 days ago
npm Package Publisherklaudworks/universal-skills	181	—	~923	Automated safety check: Pass	MIT	8 mo ago
GreptimeDB Release RunbookGreptimeTeam/greptimedb	6.7k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.6k GitHub stars~3.8k tokensUpdated 3 days ago
DevelopmentAuto-check passed
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
6.6k GitHub stars~1.4k tokensUpdated 5 days ago
DevelopmentAuto-check passed
npm Package Publisher
klaudworks/universal-skills
Releases an npm package by committing changes, bumping the version with npm version, pushing the tag and checking the GitHub Actions publish.
181 GitHub stars~923 tokensUpdated 8 mo ago
DevelopmentAuto-check passed
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
6.7k GitHub stars~1.4k tokensUpdated today
DevOps & CloudAuto-check passed
Release
dcb/homeassistant-claude-kit
Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.
123 GitHub stars~3.1k tokensUpdated yesterday
DevelopmentAuto-check passed

More from BlackBeltTechnology/pi-agent-dashboard

All 70 skills in this repo

Browser
BlackBeltTechnology/pi-agent-dashboard
Browser automation via the agent-browser CLI. An agent skill from BlackBeltTechnology/pi-agent-dashboard.
315 GitHub stars~2k tokensUpdated today
Auto-check passed
CI Troubleshoot
BlackBeltTechnology/pi-agent-dashboard
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and…
315 GitHub stars~3.5k tokensUpdated today
Auto-check passed
Debug Dashboard
BlackBeltTechnology/pi-agent-dashboard
Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.
315 GitHub stars~1.6k tokensUpdated today
Auto-check passed
Implement
BlackBeltTechnology/pi-agent-dashboard
Disciplined implementation in pi-agent-dashboard: the rebuild matrix (extension→reload, server→restart, client→build+restart, openspec-apply→full rebuild) plus the project's code discipline rules.
315 GitHub stars~2k tokensUpdated today
Auto-check passed
Pi Dashboard
BlackBeltTechnology/pi-agent-dashboard
Monitor and control the pi-dashboard server. An agent skill from BlackBeltTechnology/pi-agent-dashboard.
315 GitHub stars~2.2k tokensUpdated today
Auto-check passed
Session To Guideline
BlackBeltTechnology/pi-agent-dashboard
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered…
315 GitHub stars~3.2k tokensUpdated today
Auto-check passed

Works with

Questions about Release Revoke

What does Release Revoke do?

Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally…. Release Revoke is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit.

When should I use Release Revoke?

Release Revoke fits situations like: the user says revoke release; rollback release; unpublish vX.Y.Z.

How do I install Release Revoke in Claude Code?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a claude-code`. Or copy the skill folder (.pi/skills/release-revoke in BlackBeltTechnology/pi-agent-dashboard) into .claude/skills/release-revoke in your project. Claude Code loads it when a task matches its description.

How do I install Release Revoke in Codex?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a codex`. Or copy the skill folder (.pi/skills/release-revoke in BlackBeltTechnology/pi-agent-dashboard) into .agents/skills/release-revoke in your project. Codex loads it when a task matches its description.

Can I use Release Revoke 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 BlackBeltTechnology/pi-agent-dashboard --skill release-revoke -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-revoke, .gemini/skills/release-revoke, .github/skills/release-revoke and .opencode/skills/release-revoke in your project.

What does Release Revoke need to run?

Going by SKILL.md and its folder, Release Revoke needs the command-line tools its instructions call (git, npm and gh).

Does Release Revoke access the network?

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

Is Release Revoke 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. Review the folder before installing.

What licence does Release Revoke use?

Release Revoke is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Revoke use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 Release Revoke?

Skills that share tags, products or a category with Release Revoke: Hunk Release Workflow (modem-dev/hunk, 9.6k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars), ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars) and npm Package Publisher (klaudworks/universal-skills, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Revoke?

BlackBeltTechnology (a GitHub organization) maintains it in BlackBeltTechnology/pi-agent-dashboard, which has 315 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 10, 2026.

Source: BlackBeltTechnology/pi-agent-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Release Revoke

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Revoke a pi-agent-dashboard Release

Step 1 — Select version

Step 2 — Inspect current state

Step 3 — Confirm intent

Step 4 — Delete GitHub Release

Step 5 — Delete git tag

Step 6 — npm deprecate

Step 7 — Offer to revert the release commit

Step 8 — Summary

Guardrails

Files

Compare with similar skills

Similar skills

More from BlackBeltTechnology/pi-agent-dashboard

Related

Questions about Release Revoke