Release Openclaw Maintainer
openclaw/openclaw
Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.
Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts.
MITAuto-check passed
Install Release
$ npx skills add nowledge-co/con-terminal --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nowledge-co/con-terminal 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/nowledge-co/con-terminal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/nowledge-co/con-terminal/tree/main/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/nowledge-co/con-terminal/tree/main/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 nowledge-co/con-terminal --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nowledge-co/con-terminal release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowledge-co/con-terminal.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/nowledge-co/con-terminal/tree/main/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 nowledge-co/con-terminal --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nowledge-co/con-terminal release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowledge-co/con-terminal.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/nowledge-co/con-terminal/tree/main/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/nowledge-co/con-terminal.git --path 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 nowledge-co/con-terminal --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nowledge-co/con-terminal release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowledge-co/con-terminal.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/nowledge-co/con-terminal/tree/main/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 nowledge-co/con-terminal 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 nowledge-co/con-terminal --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nowledge-co/con-terminal.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/nowledge-co/con-terminal/tree/main/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 nowledge-co/con-terminal --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 nowledge-co/con-terminal release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowledge-co/con-terminal.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/nowledge-co/con-terminal/tree/main/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
- 625
- Token cost
- ~1k tokens
- SKILL.md length
- 502 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts.
- SKILL.md covers Release contract, Before tagging, Publish and Verify the public result, plus 2 more sections
- Calls git, gh and curl; reaches con-releases.nowledge.co
What it does
Release is an agent skill from nowledge-co/con-terminal. Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: The Native Terminal Emulator with a builtin AI Harness. The licence is MIT.
Example prompts
- “/release”
What it can do on your machine
Read from SKILL.md and the folder at commit d3c8d80. 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:
gitghcurlrg
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
con-releases.nowledge.co
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 loads about 1k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 502 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
The full file from nowledge-co/con-terminal at commit d3c8d80, republished under its MIT licence (© nowledge-co). 502 words, ~1,034 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts.
Con Release
Use this skill when preparing a release, pushing a release tag, checking a release workflow, or recovering a failed publication. The release workflow is the source of truth; do not treat a green build on one platform as a release.
Release contract
- Release from
mainonly. - Prepare
CHANGELOG.mdbefore tagging. The top section must be the next unreleased beta and every PR-derived item must credit its GitHub author. - Push exactly one immutable tag. Use
v0.1.0-beta.Nfor beta,v0.1.0-dev.Nfor dev, and the project stable tag when stable is explicitly approved. - A tag push starts the macOS, Linux, Windows, and Flatpak workflows. Platform jobs create or update one GitHub draft release and upload their own assets.
- A release is public only after all required platform assets and release-gate checks pass. Installers and updaters must never consume a draft.
- Never delete and recreate a tag to repair a release. Fix the workflow or rerun the affected workflow against the same commit.
Before tagging
Run these checks from a clean checkout:
git fetch origin main --tags
git switch main
git pull --ff-only origin main
git status --short
git tag --sort=-v:refname | rg '^v[0-9]+\\.[0-9]+\\.[0-9]+-(beta|dev)\\.' | head
gh release list --limit 5Confirm the next version is greater than the latest released version, the
changelog heading matches it, and git status --short is empty. Run the
release-relevant test suite before tagging; platform packaging tests belong in
the release workflows and must not be replaced by a local cross-build.
Publish
Create an annotated tag at the verified main commit and push only that tag:
git tag -a v0.1.0-beta.N origin/main -m "Release v0.1.0-beta.N"
git push origin refs/tags/v0.1.0-beta.NTrack the four tag-triggered workflows:
gh run list --limit 20 --json workflowName,status,conclusion,headBranch,headSha,url \\
--jq '.[] | select(.headBranch == "v0.1.0-beta.N")'Do not publish a draft manually while a required platform is still running or failed. The finalizer checks the newest matching run for each required platform, then validates assets, checksums, appcasts, and public installer scripts before promoting the draft.
Show full SKILL.md (227 more words)Show less
Verify the public result
After the finalizer succeeds, verify the public contract:
gh release view v0.1.0-beta.N --json isDraft,isPrerelease,publishedAt,assets,urlFor a beta, expect isDraft: false and the repository's beta-channel release
semantics. Confirm the expected macOS arm64/x86_64 DMGs and ZIPs, Linux
tarball, Windows ZIP, and checksum files are present. Check the beta appcasts
and the public installer endpoints if they are part of the release:
curl -fsSL https://con-releases.nowledge.co/install.sh >/dev/null
curl -fsSL https://con-releases.nowledge.co/install.ps1 >/dev/nullRecovery
- If a platform workflow is cancelled, rerun that exact workflow run; do not push a second tag.
- If all platform workflows succeeded but the release remains draft, inspect
the latest
Finalize releaserun. Rerun only the finalizer after confirming the release gate inputs are complete. - If an asset is missing, rerun the platform that owns it and verify its checksum before promotion.
- If the release is already public, later finalizer runs are harmless and must not change its prerelease/channel semantics.
- Record a workflow or release incident in
postmortem/when the failure exposes a new invariant or requires manual recovery.
Common mistakes
- Do not tag from a stale local
main. - Do not use
--forceon release tags. - Do not mark beta releases as prereleases unless the channel policy changes; current installers use the public latest beta semantics.
- Do not assume a draft URL or an uploaded asset means the release is public.
- Do not use a repository-wide GitHub Actions concurrency group for finalizer events; each source completion must remain observable.
© nowledge-co, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/release of nowledge-co/con-terminal.
Open the folder on GitHubat commit d3c8d80
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release this skillnowledge-co/con-terminal | 625 | — | ~1k | Automated safety check: Pass | MIT | |
| Release Openclaw Maintaineropenclaw/openclaw | 392k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Release Openclaw Announcementopenclaw/openclaw | 392k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Verify Releaseopenclaw/openclaw | 392k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Releasepaperclipai/paperclip | 99k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Release Changelogpaperclipai/paperclip | 99k | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
Release Openclaw Announcement
openclaw/openclaw
Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence.
Verify Release
openclaw/openclaw
Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, smoke tests, and live Gateway behavior expected for that release…
Release
paperclipai/paperclip
Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up.
Release Changelog
paperclipai/paperclip
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.
Release Generate Release Notes
mountain-loop/yaak
Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links.
More from nowledge-co/con-terminal
Con CLI E2E
nowledge-co/con-terminal
Validate Con's local socket control plane against a real running app session, and write/run con-test integration tests.
Changelog Release Notes
nowledge-co/con-terminal
Maintain Con's CHANGELOG.md and release notes. An agent skill from nowledge-co/con-terminal.
Terminal Agent Benchmark
nowledge-co/con-terminal
Run and maintain Con's terminal-agent benchmark against a live app session.
Terminal Agent Improvement Loop
nowledge-co/con-terminal
Run a benchmark-driven improvement loop for Con's terminal agent.
Questions about Release
What does Release do?
Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts. Release is an agent skill from nowledge-co/con-terminal. Run and verify Con beta, dev, and stable releases without publishing incomplete artifacts.
How do I install Release in Claude Code?
Run `npx skills add nowledge-co/con-terminal --skill release -a claude-code`. Or copy the skill folder (skills/release in nowledge-co/con-terminal) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install Release in Codex?
Run `npx skills add nowledge-co/con-terminal --skill release -a codex`. Or copy the skill folder (skills/release in nowledge-co/con-terminal) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use 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 nowledge-co/con-terminal --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 Release need to run?
Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git, gh, curl and rg).
Does Release access the network?
SKILL.md names 1 domain. In commands or code: con-releases.nowledge.co; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is 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. Review the folder before installing.
What licence does Release use?
Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release use?
About 1k tokens (SKILL.md is roughly 4.1k 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?
Skills that share tags, products or a category with Release: Release Openclaw Maintainer (openclaw/openclaw, 392k stars), Release Openclaw Announcement (openclaw/openclaw, 392k stars), Verify Release (openclaw/openclaw, 392k stars) and Release (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
nowledge-co (a GitHub organization) maintains it in nowledge-co/con-terminal, which has 625 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: nowledge-co/con-terminal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.