Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Generates coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency lockfiles since the previous release tag.
Install Generate Release Notes
$ npx skills add agntcy/coffeeAgntcy --skill generate-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agntcy/coffeeAgntcy 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/agntcy/coffeeAgntcy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/generate-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 agntcy/coffeeAgntcy --skill generate-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agntcy/coffeeAgntcy generate-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/generate-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 agntcy/coffeeAgntcy --skill generate-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agntcy/coffeeAgntcy generate-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy.git --path .agents/skills/repo-tooling/generate-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 agntcy/coffeeAgntcy --skill generate-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agntcy/coffeeAgntcy 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/agntcy/coffeeAgntcy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/generate-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 agntcy/coffeeAgntcy 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 agntcy/coffeeAgntcy --skill generate-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/generate-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 agntcy/coffeeAgntcy --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 agntcy/coffeeAgntcy generate-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/repo-tooling/generate-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/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/generate-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
- 112
- Token cost
- ~535 tokens
- SKILL.md length
- 94 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Generates coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency lockfiles since the previous release tag.
- The user asks for release notes
- SKILL.md covers Inputs, Workflow, Discovery commands and Rules
- Calls git and gh
- A changelog entry
What it does
Generate Release Notes is an agent skill from agntcy/coffeeAgntcy. Generates coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency lockfiles since the previous release tag. Use when the user asks for release notes, a changelog entry, GitHub release text, or preparing a semver release.
Its SKILL.md is about 540 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 GitHub. The repository describes itself as: End-to-end reference application for AGNTCY Components. The licence is Apache-2.0.
When your agent uses it
- The user asks for release notes
- A changelog entry
- GitHub release text
- Preparing a semver release
Example prompts
- “Use the generate-release-notes skill to generate coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency…”
- “/generate-release-notes”
What it can do on your machine
Read from SKILL.md and the folder at commit 36f1923. 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:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git 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
Generate Release Notes loads about 535 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 94 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 agntcy/coffeeAgntcy at commit 36f1923, republished under its Apache-2.0 licence (© agntcy). 94 words, ~535 tokens.
Download SKILL.mdSave it as
.claude/skills/generate-release-notes/SKILL.md (or your agent's skills folder).- name
- generate-release-notes
- description
- Generates coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency lockfiles since the previous release tag. Use when the user asks for release notes, a changelog entry, GitHub release text, or preparing a semver release.
- disable-model-invocation
- true
Generate release notes (coffeeAgntcy)
Inputs
| File | Purpose |
|---|---|
| .agents/prompts/release-notes/params.yaml | previous_version, current_version, repo identifiers |
| .agents/prompts/release-notes/PROMPT.md | Full generation spec |
| .agents/prompts/release-notes/example.md | Pointers to gold-standard examples |
Workflow
- [ ] 1. Read params.yaml - confirm versions with the user if missing or stale
- [ ] 2. Read PROMPT.md - follow it verbatim for structure and output rules
- [ ] 3. Read CHANGELOG.md - previous release section + example section from example.md
- [ ] 4. Collect changes since previous_version (PRs on default branch; direct commits only when no PR)
- [ ] 5. Read dependency lockfiles listed in PROMPT.md
- [ ] 6. Read README.md Built With section for formatting reference
- [ ] 7. Output two markdown code blocks - do not edit files unless askedDiscovery commands
Use when the user has not supplied a PR list:
git tag -l 'v*' --sort=-version:refname | head
git log v{previous_version}..HEAD --merges --oneline
gh pr list --repo {github_repo} --state merged --base main --limit 100Substitute {previous_version}, {current_version}, and {github_repo} from params.yaml. Prefix tags with v only if that matches existing tags in the repo.
Rules
- Follow PROMPT.md for structure, contributor omit list, and HTML
<details>format. - Do not paraphrase or shorten the user's spec; apply it as written.
- Default: generate text only. Edit
CHANGELOG.mdorREADME.mdonly when the user explicitly requests file changes.
© agntcy, Apache-2.0. 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 .agents/skills/repo-tooling/generate-release-notes of agntcy/coffeeAgntcy.
Open the folder on GitHubat commit 36f1923
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 skillagntcy/coffeeAgntcy | 112 | — | ~535 | Automated safety check: Pass | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 69k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 69k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
More from agntcy/coffeeAgntcy
All 16 skills in this repoA2a Protocol
agntcy/coffeeAgntcy
A skill your agent uses when the user asks about A2A (Agent-to-Agent) protocol communication, OASF record formats, AGNTCY directory operations, agent card parsing, or dirctl CLI usage.
Add Repo Operation
agntcy/coffeeAgntcy
Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline.
Agentic Workflows API Documentation Lungo
agntcy/coffeeAgntcy
Authors and maintains the human-facing Agentic Workflows API documentation for the lungo subproject at coffeeAGNTCY/coffeeagents/lungo/docs/workflow-instanceapi.md.
Checking Pinned References
agntcy/coffeeAgntcy
Runs task pins:check to find any third-party GitHub Action, reusable-workflow, or image reference that isn't pinned to an immutable SHA/digest, and pins each one it finds.
Checking Workflow Permissions
agntcy/coffeeAgntcy
Runs task workflows:check-permissions to find any GitHub Actions workflow file with a write-all grant or no declared permissions, and scopes it down to least privilege.
Linting GitHub Workflows
agntcy/coffeeAgntcy
Runs task workflows:lint (actionlint) against every file under .github/workflows/ and fixes what it reports.
Related
Works with
Categories
Questions about Generate Release Notes
What does Generate Release Notes do?
Generates coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency lockfiles since the previous release tag. Generate Release Notes is an agent skill from agntcy/coffeeAgntcy. Generates coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency lockfiles since the previous release tag.
When should I use Generate Release Notes?
Generate Release Notes fits situations like: the user asks for release notes; A changelog entry; GitHub release text; preparing a semver release.
How do I install Generate Release Notes in Claude Code?
Run `npx skills add agntcy/coffeeAgntcy --skill generate-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/repo-tooling/generate-release-notes in agntcy/coffeeAgntcy) 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 agntcy/coffeeAgntcy --skill generate-release-notes -a codex`. Or copy the skill folder (.agents/skills/repo-tooling/generate-release-notes in agntcy/coffeeAgntcy) 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 agntcy/coffeeAgntcy --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?
Going by SKILL.md and its folder, Generate Release Notes needs the command-line tools its instructions call (git and gh).
Does Generate Release Notes access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. 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 Apache-2.0 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 535 tokens (SKILL.md is roughly 2.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: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 69k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 69k 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?
agntcy (a GitHub organization) maintains it in agntcy/coffeeAgntcy, which has 112 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 6, 2026.
Source: agntcy/coffeeAgntcy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.