EverOS Release Workflow
EverMind-AI/EverOS
Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.
Guide a Dallinger release (minor from master, or patch/major) including changelog, bumpversion, demo constraints, tagging, PyPI/ghcr deploy, GitHub Release, and the post-release alpha bump.
Install Release
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add Dallinger/Dallinger --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Dallinger/Dallinger 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/Dallinger/Dallinger.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/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/Dallinger/Dallinger/tree/master/.cursor/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/Dallinger/Dallinger/tree/master/.cursor/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 Dallinger/Dallinger --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Dallinger/Dallinger release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dallinger/Dallinger.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/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/Dallinger/Dallinger/tree/master/.cursor/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 Dallinger/Dallinger --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Dallinger/Dallinger release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dallinger/Dallinger.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/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/Dallinger/Dallinger/tree/master/.cursor/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/Dallinger/Dallinger.git --path .cursor/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 Dallinger/Dallinger --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Dallinger/Dallinger release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dallinger/Dallinger.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/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/Dallinger/Dallinger/tree/master/.cursor/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 Dallinger/Dallinger 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 Dallinger/Dallinger --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Dallinger/Dallinger.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/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/Dallinger/Dallinger/tree/master/.cursor/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 Dallinger/Dallinger --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 Dallinger/Dallinger release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dallinger/Dallinger.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/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/Dallinger/Dallinger/tree/master/.cursor/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
- 124
- Token cost
- ~4.6k tokens
- SKILL.md length
- 1,915 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guide a Dallinger release (minor from master, or patch/major) including changelog, bumpversion, demo constraints, tagging, PyPI/ghcr deploy, GitHub Release, and the post-release alpha bump.
- Works in 11 steps: Pre-flight → Cut the release branch → Finalize CHANGELOG.md → …
- Cutting a Dallinger release
- SKILL.md covers Decide the version, Prerequisites, Human-in-the-loop policy and 1. Pre-flight, plus 12 more sections
- Calls git, gh and python3; reaches pypi.org
What it does
Release is an agent skill from Dallinger/Dallinger. Guide a Dallinger release (minor from master, or patch/major) including changelog, bumpversion, demo constraints, tagging, PyPI/ghcr deploy, GitHub Release, and the post-release alpha bump. Use when cutting a Dallinger release or publishing to PyPI/ghcr.
Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes and Deployment. It works with GitHub. The repository describes itself as: Laboratory automation for the behavioral and social sciences; human culture on a chip.
When your agent uses it
- Cutting a Dallinger release
- Publishing to PyPI/ghcr
Example prompts
- “/release”
Requirements
- Python 3
Workflow steps
11 steps, taken from the step headings in SKILL.md.
- Pre-flight
- Cut the release branch
- Finalize CHANGELOG.md
- Bump the version
- Push the release branch
- Regenerate demo constraints
- Open the PR
- Merge
- Wait for master CI, then tag
- Create the GitHub Release
- Wait for the tag pipeline, then bump master
What it can do on your machine
Read from SKILL.md and the folder at commit 1f5092e. 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:
gitghpython3ruff
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:
pypi.org
Also links to:
semver.org
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 4.6k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 1,915 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:116
Do not wait for a second confirmation, and do not wait for the GitHub
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 1,915 words (~4,626 tokens).
“Invoke this skill with /release. Determine major vs minor vs patch yourself from the unreleased CHANGELOG and current version (see Decide the version). Honor an explicit override only if the user already named a type (/release patch, etc.).”
- name
- release
Files
Just SKILL.md in .cursor/skills/release of Dallinger/Dallinger.
Open the folder on GitHubat commit 1f5092e
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 skillDallinger/Dallinger | 124 | — | ~4.6k | Automated safety check: Warn | Custom licence | |
| EverOS Release WorkflowEverMind-AI/EverOS | 13k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Remotion Bits Releaseav/remotion-bits | 490 | — | ~1.2k | Automated safety check: Pass | None | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| Releasehyhmrright/brooks-lint | 1.5k | — | ~1.2k | Automated safety check: Pass | MIT | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Remotion Bits Release
av/remotion-bits
Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.
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.
Release
hyhmrright/brooks-lint
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG…
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.
AnyDrag Release Routine
XueshiQiao/AnyDrag
Runs the full AnyDrag release process end to end, from cumulative bilingual release notes through version bumping to watching CI and the Homebrew cask update.
More from Dallinger/Dallinger
Branch Review
Dallinger/Dallinger
Review branch changes against master using a diff-to-master workflow that emphasizes correctness, regressions, API breaks, side effects, and missing tests.
Related
Works with
Categories
Questions about Release
What does Release do?
Guide a Dallinger release (minor from master, or patch/major) including changelog, bumpversion, demo constraints, tagging, PyPI/ghcr deploy, GitHub Release, and the post-release alpha bump. Release is an agent skill from Dallinger/Dallinger. Guide a Dallinger release (minor from master, or patch/major) including changelog, bumpversion, demo constraints, tagging, PyPI/ghcr deploy, GitHub Release, and the post-release alpha bump.
When should I use Release?
Release fits situations like: cutting a Dallinger release; publishing to PyPI/ghcr.
How do I install Release in Claude Code?
Run `npx skills add Dallinger/Dallinger --skill release -a claude-code`. Or copy the skill folder (.cursor/skills/release in Dallinger/Dallinger) 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 Dallinger/Dallinger --skill release -a codex`. Or copy the skill folder (.cursor/skills/release in Dallinger/Dallinger) 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 Dallinger/Dallinger --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, python3 and ruff). Our summary lists: Python 3.
Does Release access the network?
SKILL.md names 2 domains. In commands or code: pypi.org; the agent is likely to contact it when it follows the instructions. As links in the text: semver.org. This is read from the text; nothing was executed.
Is Release safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Release use?
Release 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 Release use?
About 4.6k tokens (SKILL.md is roughly 19k 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: EverOS Release Workflow (EverMind-AI/EverOS, 13k stars), Remotion Bits Release (av/remotion-bits, 490 stars), Cline CLI Release Publisher (cline/cline, 70k stars) and Release (hyhmrright/brooks-lint, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
Dallinger (a GitHub organization) maintains it in Dallinger/Dallinger, which has 124 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 10, 2026.
Source: Dallinger/Dallinger on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.