Agr Release
computerlovetech/agr
Release process for the agr package. An agent skill from computerlovetech/agr.
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
Install OpenWork Release Process
$ npx skills add different-ai/openwork --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install different-ai/openwork release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/release .claude/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 install https://github.com/different-ai/openwork/tree/dev/.opencode/skills/releaseType 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.
$ npx skills add different-ai/openwork --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install different-ai/openwork release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/release .agents/skills/release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.
$ npx skills add different-ai/openwork --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install different-ai/openwork release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/release .cursor/skills/release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 https://github.com/different-ai/openwork.git --path .opencode/skills/release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add different-ai/openwork --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install different-ai/openwork release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/release .gemini/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.
$ gh skill install different-ai/openwork releaseInstalls 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).
$ npx skills add different-ai/openwork --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/release .github/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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.
$ npx skills add different-ai/openwork --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install different-ai/openwork release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/different-ai/openwork.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/release .opencode/skills/release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/different-ai/openwork/tree/dev/.opencode/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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- GitHub stars
- 24k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 984 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
- Cutting a new OpenWork release
- SKILL.md covers Before you tag: open fix PRs…, Cut a release (default path), Tag-first (expedited, admins… and Watch, plus 3 more sections
- Calls gh, pnpm and git; needs WARDEN_PRIVATE_KEY
- Rerunning or recovering a release tag after a failed run
What it does
Versions live only in git tags: committed `package.json` files keep a `0.0.0-dev` placeholder and CI stamps the tag-derived version at build time, so a release makes zero commits to the repo. The Release App workflow in `.github/workflows/release-macos-aarch64.yml` builds, signs and publishes the desktop assets, and the full runbook is `docs/RELEASING.md`. A release counts as done when the run is green and the GitHub release is published rather than a draft, never when the tag is merely created.
Before tagging, the agent lists open PRs since the previous stable tag whose title or body mentions fixes such as crash, blank screen or regression, plus open fork PRs, because fork PRs get no automatic clearance. For each one it decides to land it first or ship anyway, and shipping anyway must be recorded with the PR numbers, who decided and why in the release notes PR that the changelog workflow opens after publishing. The skill also covers rerunning or recovering a tag and verifying release assets.
When your agent uses it
- Cutting a new OpenWork release
- Rerunning or recovering a release tag after a failed run
- Checking release assets once the GitHub release is published
- Screening open crash-fix PRs before tagging
Example prompts
- “Cut the next OpenWork release, but check for open crash fixes first.”
- “Recover the release tag whose workflow run failed.”
- “Verify that the published GitHub release has all the desktop assets.”
Requirements
- A checkout of the OpenWork repository with GitHub CLI (`gh`)
- Permission to push tags and run the Release App workflow
What it can do on your machine
Read from SKILL.md and the folder at commit 9ce20f8. 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:
ghpnpmgitjqcurlnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, pnpm, git, curl and npm, 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:
WARDEN_PRIVATE_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
OpenWork Release Process loads about 2.3k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 984 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 984 words (~2,295 tokens).
“Cut an OpenWork release. The "Release App" workflow (.github/workflows/release-macos-aarch64.yml) builds, signs, and publishes the desktop app assets on the GitHub release. Full runbook: docs/RELEASING.md.”
- name
- release
Files
Just SKILL.md in .opencode/skills/release of different-ai/openwork.
Open the folder on GitHubat commit 9ce20f8
Compare with similar skills
OpenWork Release Process 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| OpenWork Release Process this skilldifferent-ai/openwork | 24k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Agr Releasecomputerlovetech/agr | 451 | — | ~1.6k | Automated safety check: Pass | MIT | |
| ClickUp CLI Release Processkrodak/clickup-cli | 121 | — | ~906 | Automated safety check: Warn | MIT | |
| Vercel CI Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| Kt Search Releasejillesvangurp/kt-search | 155 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
ClickUp CLI Release Process
krodak/clickup-cli
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
Vercel CI Integration
jeremylongshore/tons-of-skills-marketplace
Configure Vercel CI/CD with GitHub Actions, preview deployments, and automated testing.
Cline CLI Release Publisher
cline/cline
Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.
Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
CI Automation
jeremylongshore/tons-of-skills-marketplace
A skill your agent uses when running GitHub Actions locally, creating task runner recipes, generating changelogs from git history, managing GitHub PRs/issues/releases programmatically, or creating…
More from different-ai/openwork
All 33 skills in this repoOpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
Fake Model Provider Faults
different-ai/openwork
Makes the desktop app's model provider fail on demand, with refused connections, resets, stalls and HTTP 4xx and 5xx errors, so error and retry states can be reproduced.
OpenWork Model Alias Manager
different-ai/openwork
Manages OpenWork's inference model aliases, discounts and overlays over the upstream OpenRouter catalog, and triggers the GitHub workflow that refreshes base models.
Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
OpenWork Electron Browser Automation
different-ai/openwork
Attaches OpenCode browser tools to the OpenWork Electron dev app through CDP to explore its UI, send a composer task and debug, not to give test verdicts.
Daytona Sandbox Operations
different-ai/openwork
Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.
Related
Works with
Categories
Questions about OpenWork Release Process
What does OpenWork Release Process do?
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward. 0-dev` placeholder and CI stamps the tag-derived version at build time, so a release makes zero commits to the repo.md`.
When should I use OpenWork Release Process?
OpenWork Release Process fits situations like: cutting a new OpenWork release; rerunning or recovering a release tag after a failed run; checking release assets once the GitHub release is published; screening open crash-fix PRs before tagging.
How do I install OpenWork Release Process in Claude Code?
Run `npx skills add different-ai/openwork --skill release -a claude-code`. Or copy the skill folder (.opencode/skills/release in different-ai/openwork) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install OpenWork Release Process in Codex?
Run `npx skills add different-ai/openwork --skill release -a codex`. Or copy the skill folder (.opencode/skills/release in different-ai/openwork) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use OpenWork Release Process 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 different-ai/openwork --skill 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/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.
What does OpenWork Release Process need to run?
Going by SKILL.md and its folder, OpenWork Release Process needs the command-line tools its instructions call (gh, pnpm, git, jq, curl and npm) and credentials named WARDEN_PRIVATE_KEY. Our summary lists: A checkout of the OpenWork repository with GitHub CLI (`gh`); Permission to push tags and run the Release App workflow.
Does OpenWork Release Process access the network?
SKILL.md contains no URLs. Its commands use gh, git, curl and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is OpenWork Release Process 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 OpenWork Release Process use?
OpenWork Release Process has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does OpenWork Release Process use?
About 2.3k tokens (SKILL.md is roughly 9.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 OpenWork Release Process?
Skills that share tags, products or a category with OpenWork Release Process: Agr Release (computerlovetech/agr, 451 stars), ClickUp CLI Release Process (krodak/clickup-cli, 121 stars), Vercel CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Cline CLI Release Publisher (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OpenWork Release Process?
different-ai (a GitHub organization) maintains it in different-ai/openwork, which has 23,943 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 8, 2026.
Source: different-ai/openwork on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.