Release Skills
nexmoe/eve
Universal release workflow. An agent skill from nexmoe/eve.
Generate release notes for CTk Theme Builder by checking for uncommitted changes, verifying the release version in .bumpversion.cfg, and appending the standard installation and upgrade footer.
Install Generate Release Notes
$ npx skills add avalon60/ctk_theme_builder --skill generate-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install avalon60/ctk_theme_builder generate-release-notes --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/avalon60/ctk_theme_builder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/release-notes .claude/skills/generate-release-notes && 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 "generate-release-notes" agent skill from https://github.com/avalon60/ctk_theme_builder/tree/develop/.codex/skills/release-notes into .claude/skills/generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-release-notes", 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/avalon60/ctk_theme_builder/tree/develop/.codex/skills/release-notesType 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 avalon60/ctk_theme_builder --skill generate-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install avalon60/ctk_theme_builder generate-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avalon60/ctk_theme_builder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/release-notes .agents/skills/generate-release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "generate-release-notes" agent skill from https://github.com/avalon60/ctk_theme_builder/tree/develop/.codex/skills/release-notes into .agents/skills/generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-release-notes", 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 avalon60/ctk_theme_builder --skill generate-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install avalon60/ctk_theme_builder generate-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avalon60/ctk_theme_builder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/release-notes .cursor/skills/generate-release-notes && 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 "generate-release-notes" agent skill from https://github.com/avalon60/ctk_theme_builder/tree/develop/.codex/skills/release-notes into .cursor/skills/generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-release-notes", 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/avalon60/ctk_theme_builder.git --path .codex/skills/release-notes--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 avalon60/ctk_theme_builder --skill generate-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install avalon60/ctk_theme_builder generate-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avalon60/ctk_theme_builder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/release-notes .gemini/skills/generate-release-notes && 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 "generate-release-notes" agent skill from https://github.com/avalon60/ctk_theme_builder/tree/develop/.codex/skills/release-notes into .gemini/skills/generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-release-notes", 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 avalon60/ctk_theme_builder generate-release-notesInstalls 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 avalon60/ctk_theme_builder --skill generate-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/avalon60/ctk_theme_builder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/release-notes .github/skills/generate-release-notes && 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 "generate-release-notes" agent skill from https://github.com/avalon60/ctk_theme_builder/tree/develop/.codex/skills/release-notes into .github/skills/generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-release-notes", 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 avalon60/ctk_theme_builder --skill generate-release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install avalon60/ctk_theme_builder generate-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avalon60/ctk_theme_builder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/release-notes .opencode/skills/generate-release-notes && 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 "generate-release-notes" agent skill from https://github.com/avalon60/ctk_theme_builder/tree/develop/.codex/skills/release-notes into .opencode/skills/generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "generate-release-notes", 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
generate-release-notes- GitHub stars
- 328
- Token cost
- ~287 tokens
- SKILL.md length
- 133 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate release notes for CTk Theme Builder by checking for uncommitted changes, verifying the release version in .bumpversion.cfg, and appending the standard installation and upgrade footer.
- Works in 3 steps: Check whether the repository has… → Check that the application version has… → Append the following footer text after…
- Tasks that involve Changelog and release notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Generate Release Notes is an agent skill from avalon60/ctk_theme_builder. Generate release notes for CTk Theme Builder by checking for uncommitted changes, verifying the release version in .bumpversion.cfg, and appending the standard installation and upgrade footer.
Its SKILL.md is about 290 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. It works with Python. The repository describes itself as: CTk Theme Builder for CustomTkinter, a comprehensive and easy solution, for creating CustomTkinter themes. The licence is MIT.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/generate-release-notes”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Check whether the repository has outstanding modifications. If the worktree is dirty, tell the user that the release notes may not reflect…
- Check that the application version has already been bumped to the intended release version before drafting the notes. For OraTAPI, treat…
- Append the following footer text after the release-specific notes. Replace placeholders such as x.y.z with the actual release version…
What it can do on your machine
Read from SKILL.md and the folder at commit a27fba6. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Generate Release Notes loads about 287 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 133 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 avalon60/ctk_theme_builder at commit a27fba6, republished under its MIT licence (© avalon60). 133 words, ~287 tokens.
Download SKILL.mdSave it as
.claude/skills/generate-release-notes/SKILL.md (or your agent's skills folder).- name
- generate-release-notes
- description
- Generate release notes for CTk Theme Builder by checking for uncommitted changes, verifying the release version in .bumpversion.cfg, and appending the standard installation and upgrade footer.
When requested to generate release notes:
- Check whether the repository has outstanding modifications. If the worktree is dirty, tell the user that the release notes may not reflect all uncommitted changes and confirm whether the notes should be based on the current working tree or only on committed changes.
- Check that the application version has already been bumped to the intended release version before drafting the notes. For OraTAPI, treat
.bumpversion.cfgas the authoritative release-version source unless the user explicitly says otherwise. If.bumpversion.cfghas not yet been updated, warn the user that version-specific wording, artifact names, and upgrade guidance may be inaccurate until the version bump is complete. - Append the following footer text after the release-specific notes. Replace placeholders such as
x.y.zwith the actual release version where applicable.
© avalon60, 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 .codex/skills/release-notes of avalon60/ctk_theme_builder.
Open the folder on GitHubat commit a27fba6
Compare with similar skills
Generate Release Notes 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 |
|---|---|---|---|---|---|---|
| Generate Release Notes this skillavalon60/ctk_theme_builder | 328 | — | ~287 | Automated safety check: Pass | MIT | |
| Release Skillsnexmoe/eve | 421 | 3 repos | ~3.3k | Automated safety check: Pass | None | |
| Commitizencommitizen-tools/commitizen | 3.5k | — | ~839 | Automated safety check: Pass | MIT | |
| pybind11 Release Preparationpybind/pybind11 | 18k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| pybind11 Release Publicationpybind/pybind11 | 18k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| EverOS Release WorkflowEverMind-AI/EverOS | 13k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Commitizen
commitizen-tools/commitizen
A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
pybind11 Release Publication
pybind/pybind11
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
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.
Pre Release
ZhuoZhuoCrayon/throttled-py
Automates release preparation for throttled-py. An agent skill from ZhuoZhuoCrayon/throttled-py.
More from avalon60/ctk_theme_builder
Ctkfontawesome Usage
avalon60/ctk_theme_builder
A skill your agent uses when implementing Font Awesome icons in a CustomTkinter app with the ctkfontawesome package.
Release Package
avalon60/ctk_theme_builder
Prepare a release artefact for this project by bumping the requested semantic version level and running the packaging script.
Enhance Theme
avalon60/ctk_theme_builder
Locate, modify, and optionally promote CTk Theme Builder theme JSON files
Related
Works with
Categories
Questions about Generate Release Notes
What does Generate Release Notes do?
Generate release notes for CTk Theme Builder by checking for uncommitted changes, verifying the release version in .bumpversion.cfg, and appending the standard installation and upgrade footer. Generate Release Notes is an agent skill from avalon60/ctk_theme_builder.cfg, and appending the standard installation and upgrade footer.
When should I use Generate Release Notes?
Generate Release Notes fits situations like: tasks that involve Changelog and release notes.
How do I install Generate Release Notes in Claude Code?
Run `npx skills add avalon60/ctk_theme_builder --skill generate-release-notes -a claude-code`. Or copy the skill folder (.codex/skills/release-notes in avalon60/ctk_theme_builder) into .claude/skills/generate-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Generate Release Notes in Codex?
Run `npx skills add avalon60/ctk_theme_builder --skill generate-release-notes -a codex`. Or copy the skill folder (.codex/skills/release-notes in avalon60/ctk_theme_builder) into .agents/skills/generate-release-notes in your project. Codex loads it when a task matches its description.
Can I use Generate Release Notes 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 avalon60/ctk_theme_builder --skill generate-release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-release-notes, .gemini/skills/generate-release-notes, .github/skills/generate-release-notes and .opencode/skills/generate-release-notes in your project.
What does Generate Release Notes need to run?
SKILL.md names no scripts, command-line tools or credentials: Generate Release Notes is instructions for the agent only.
Does Generate Release Notes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Generate Release Notes 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 Generate Release Notes use?
Generate Release Notes 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 Generate Release Notes use?
About 287 tokens (SKILL.md is roughly 1.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 Generate Release Notes?
Skills that share tags, products or a category with Generate Release Notes: Release Skills (nexmoe/eve, 421 stars), Commitizen (commitizen-tools/commitizen, 3.5k stars), pybind11 Release Preparation (pybind/pybind11, 18k stars) and pybind11 Release Publication (pybind/pybind11, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Generate Release Notes?
avalon60 (a GitHub user) maintains it in avalon60/ctk_theme_builder, which has 328 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: avalon60/ctk_theme_builder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.