Maintain DisCatSharp
Aiko-IT-Systems/DisCatSharp
Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.
A skill your agent uses to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag.
Install Write Release Announcements
$ npx skills add Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Gremlinq/ExRam.Gremlinq write-release-announcements --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/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-release-announcements .claude/skills/write-release-announcements && 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 "write-release-announcements" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/write-release-announcements into .claude/skills/write-release-announcements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-announcements", 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/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/write-release-announcementsType 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 Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Gremlinq/ExRam.Gremlinq write-release-announcements --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-release-announcements .agents/skills/write-release-announcements && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-release-announcements" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/write-release-announcements into .agents/skills/write-release-announcements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-announcements", 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 Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Gremlinq/ExRam.Gremlinq write-release-announcements --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-release-announcements .cursor/skills/write-release-announcements && 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 "write-release-announcements" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/write-release-announcements into .cursor/skills/write-release-announcements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-announcements", 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/Gremlinq/ExRam.Gremlinq.git --path .agents/skills/write-release-announcements--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 Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Gremlinq/ExRam.Gremlinq write-release-announcements --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-release-announcements .gemini/skills/write-release-announcements && 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 "write-release-announcements" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/write-release-announcements into .gemini/skills/write-release-announcements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-announcements", 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 Gremlinq/ExRam.Gremlinq write-release-announcementsInstalls 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 Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-release-announcements .github/skills/write-release-announcements && 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 "write-release-announcements" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/write-release-announcements into .github/skills/write-release-announcements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-announcements", 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 Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Gremlinq/ExRam.Gremlinq write-release-announcements --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Gremlinq/ExRam.Gremlinq.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-release-announcements .opencode/skills/write-release-announcements && 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 "write-release-announcements" agent skill from https://github.com/Gremlinq/ExRam.Gremlinq/tree/14.x/.agents/skills/write-release-announcements into .opencode/skills/write-release-announcements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-release-announcements", 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
write-release-announcements- GitHub stars
- 187
- Token cost
- ~1.6k tokens
- SKILL.md length
- 919 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag.
- Works in 6 steps: Run scripts/collect-prs.sh. It resolves… → Read the excluded list out loud to the… → Propose a grouping of the remaining pull… → …
- Write the release notes and the announcement texts for an upcoming release
- SKILL.md covers Usage, Where the texts go, and why…, Workflow and Curation is not automatic, plus 3 more sections
- Runs Shell scripts from its folder; calls git and gh
What it does
Write Release Announcements is an agent skill from Gremlinq/ExRam.Gremlinq. Use this skill to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag. Produces releases/<version/release-notes.md plus LinkedIn and Discord texts. Invokes when asked to "write release announcements", "write the release notes" or similar, and is invoked by the prepare-release skill. Does NOT bump versions, create tags or publish anything.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/channel-style.md`, `scripts/check-lengths.sh` and `scripts/collect-prs.sh`).
It sits in Development, covering Changelog and release notes. It works with LinkedIn, Discord, .NET and Azure Cosmos DB. The repository describes itself as: A .NET object-graph-mapper for Apache TinkerPop™ Gremlin enabled databases. The licence is MIT.
When your agent uses it
- Write the release notes and the announcement texts for an upcoming release
- From the pull requests merged since the previous tag
Example prompts
- “write release announcements”
- “write the release notes”
- “/write-release-announcements”
Requirements
- A Bash shell
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Run scripts/collect-prs.sh. It resolves the previous release tag, the target version
- Read the excluded list out loud to the user. The script drops anything labelled
- Propose a grouping of the remaining pull requests into Features / Fixes / Performance /
- Write the texts into releases// following
- Run scripts/check-lengths.sh releases/ and fix what it reports. Missing
- Commit: git add releases/ && git commit -m "Add release notes and announcements for ".
What it can do on your machine
Read from SKILL.md and the folder at commit bb8c6fe. 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
Ships 2 files in scripts/ (Shell), which the agent can run.
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
Write Release Announcements loads about 1.6k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 919 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); the scripts in this folder are not scanned.
SKILL.md
The full file from Gremlinq/ExRam.Gremlinq at commit bb8c6fe, republished under its MIT licence (© Gremlinq). 919 words, ~1,637 tokens.
Download SKILL.mdSave it as
.claude/skills/write-release-announcements/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- write-release-announcements
- description
- Use this skill to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag. Produces releases/<version>/release-notes.md plus LinkedIn and Discord texts. Invokes when asked to "write release announcements", "write the release notes" or similar, and is invoked by the prepare-release skill. Does NOT bump versions, create tags or publish anything.
Write Release Announcements
Turns the pull requests merged since the last release into the four texts a release needs.
Usage
write release announcementsRuns standalone whenever the texts need to be written or rewritten, and is invoked by
prepare-release as the step before the version is bumped.
Where the texts go, and why the order matters
Everything lands in releases/<version>/ -- for example releases/14.2.0/:
| File | Becomes |
|---|---|
release-notes.md | the GitHub release body (pack.yml passes it to gh release create --notes-file); in ExRam.Gremlinq, publishBlogPost.yml then also copies it verbatim into the blog on docs.gremlinq.net |
linkedin.md | a manual LinkedIn post |
discord-tinkerpop.md | a manual post in the TinkerPop Discord |
discord-dotnet.md | a manual post in the .NET Discord |
The LinkedIn and Discord channels described here, and the worked examples in the channel style guide, are ExRam.Gremlinq's own -- written for that library's audience and communities. A repository that shares this skill but does not run its own LinkedIn/Discord announcements should confirm with the user which of the four texts, if any, are wanted before writing all of them.
These files must be committed before nbgv prepare-release runs. That command creates
the branch the release tag is put on, and the current branch is then rebased onto it --
so the tag points at the earlier state. In ExRam.Gremlinq, pack.yml and
openAnnouncementChecklist.yml both read these files out of the tag; a repository without those workflows still benefits from the same ordering,
since a tag whose release-notes.md is missing falls back to a worse, auto-generated body.
Commit them late and they will not be there.
That is why this skill commits its own output rather than leaving it staged.
Workflow
- Run
scripts/collect-prs.sh. It resolves the previous release tag, the target version (vianbgv) and the pull requests merged since, and prints JSON. Pass a tag as an argument to collect for a different range. - Read the
excludedlist out loud to the user. The script drops anything labelledskip-changelogand the release-preparation pull requests. That is a floor, not curation -- see below. - Propose a grouping of the remaining pull requests into Features / Fixes / Performance /
Maintenance, together with anything you think should be dropped, and get agreement
before writing. Propose dropping every pull request with
tests_onlyset: its lead says "Tests only", so it changes nothing a reader of the notes would notice. Check the lead, since the flag only matches the words. - Write the texts into
releases/<version>/following the channel style guide.release_kindin the JSON says whether this is apatch,minorormajorrelease: a patch getsrelease-notes.mdonly, unless the user asks for the rest. - Run
scripts/check-lengths.sh releases/<version>and fix what it reports. Missing release notes fail it; the three channel texts are optional, so a patch release passes with only the notes. A Discord text over 2000 characters is rejected by Discord outright. - Commit:
git add releases/<version> && git commit -m "Add release notes and announcements for <version>". When onlyrelease-notes.mdwas written, say so:"Add release notes for <version>".
Show full SKILL.md (420 more words)Show less
Curation is not automatic
The skip-changelog label removes the obvious chores. It does not decide what is worth
announcing, and the history shows why: the hand-written notes for 14.1.1 covered 7 of the
13 pull requests in range. Kept were a CI change (Trusted Publishing) and a test-reporting
change; dropped were dependency bumps and Actions maintenance. There is no rule that
separates those -- it is a judgement about what a reader of the changelog would care
about.
So: propose, show what you would drop and why, and let the user decide. Do not quietly truncate, and do not pad the notes with everything in range either.
The range for 14.1.2 shows what the label misses. Eight pull requests there only added
contract tests ("Say that a bulk set may shout its type name", "Tests only."), and none
carried skip-changelog. They described behaviour the library already had, so a release
note for them would have announced a change that never happened. tests_only catches
that case; reading the leads still catches the rest.
Writing the entries
Each pull request in the JSON carries a lead field: the text above its first ##
heading, with the pull request template's HTML comment already stripped. That is the
change's changelog entry. Use lead, not body -- authors routinely leave the template
comment in, and it sits above that heading, so reading body by hand would carry
"Replace this comment with one to three sentences..." into the published notes and from
there, verbatim, into the blog post.
If a lead runs longer than about two sentences, summarise it -- the notes are scanned,
not read.
If a lead is empty or useless, the entry cannot be reconstructed honestly
from the title alone. Say so, and either read the diff for that one change or ask. Do not
paraphrase the title back as if it were a description; that is the failure mode the
open-pull-request skill exists to prevent, and it should not be reintroduced here.
Key requirements
- Version comes from
nbgv get-version, never from a guess or fromversion.jsonread by hand. - Every release-note entry links to its pull request as
([#2417](url)). - No author names. Nearly every pull request here is the maintainer's own.
- Do not create tags, do not bump
version.json, do not push. That isprepare-release. - Do not post anything anywhere. Every text is posted by hand, and whether it is posted at all is the maintainer's decision.
References
- Channel Style - what each of the four texts is for, its limits, and a worked example of each
© Gremlinq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in .agents/skills/write-release-announcements of Gremlinq/ExRam.Gremlinq.
- SKILL.md
- references/channel-style.md
- scripts/check-lengths.sh
- scripts/collect-prs.sh
Open the folder on GitHubat commit bb8c6fe
Compare with similar skills
Write Release Announcements 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 |
|---|---|---|---|---|---|---|
| Write Release Announcements this skillGremlinq/ExRam.Gremlinq | 187 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Maintain DisCatSharpAiko-IT-Systems/DisCatSharp | 140 | — | ~1.2k | Automated safety check: Pass | MIT | |
| .NET Release Verificationdotnet/core | 22k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Add Analyzerdotnet/roslynator | 3.5k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Generate .NET Release changes.jsondotnet/core | 22k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Release Feature Scoringdotnet/core | 22k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
.NET Release Verification
dotnet/core
Validates .NET release data with the release-notes CLI: download URL liveness, SHA512 hashes, CDN latest.version files and aka.ms redirects.
- Official
Add Analyzer
dotnet/roslynator
A skill your agent uses when adding a new RCS diagnostic in roslynator (RCS0 formatting, RCS1 general, RCS9 code-analysis), wiring roslynator EditorConfig options, or when docs say CHANGELOG.md…
- Official
Generate .NET Release changes.json
dotnet/core
Produces the changes.json manifest for a .NET preview, RC or GA milestone by choosing the right VMR base and head refs and running release-notes generate changes.
- Official
Release Feature Scoring
dotnet/core
Ranks the changes in a release manifest and writes a scored features file that release notes, docs and blog posts can each cut at their own threshold.
- Official
Release Notes Editorial Review
dotnet/core
Audits a scored features.json file and its draft release notes against editorial examples to catch over-scored, under-scored, or missing entries.
More from Gremlinq/ExRam.Gremlinq
Open Pull Request
Gremlinq/ExRam.Gremlinq
A skill your agent uses when opening a pull request for the current branch, or when an existing pull request needs a better description - including when the check-description CI check has failed.
Prepare Release
Gremlinq/ExRam.Gremlinq
A skill your agent uses when preparing a new release. An agent skill from Gremlinq/ExRam.Gremlinq.
Related
Works with
Categories
Questions about Write Release Announcements
What does Write Release Announcements do?
A skill your agent uses to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag. Gremlinq. Use this skill to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag.
When should I use Write Release Announcements?
Write Release Announcements fits situations like: write the release notes and the announcement texts for an upcoming release; from the pull requests merged since the previous tag.
How do I install Write Release Announcements in Claude Code?
Run `npx skills add Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a claude-code`. Or copy the skill folder (.agents/skills/write-release-announcements in Gremlinq/ExRam.Gremlinq) into .claude/skills/write-release-announcements in your project. Claude Code loads it when a task matches its description.
How do I install Write Release Announcements in Codex?
Run `npx skills add Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a codex`. Or copy the skill folder (.agents/skills/write-release-announcements in Gremlinq/ExRam.Gremlinq) into .agents/skills/write-release-announcements in your project. Codex loads it when a task matches its description.
Can I use Write Release Announcements 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 Gremlinq/ExRam.Gremlinq --skill write-release-announcements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-release-announcements, .gemini/skills/write-release-announcements, .github/skills/write-release-announcements and .opencode/skills/write-release-announcements in your project.
What does Write Release Announcements need to run?
Going by SKILL.md and its folder, Write Release Announcements needs a shell for the scripts in its folder and the command-line tools its instructions call (git and gh). Our summary lists: A Bash shell.
Does Write Release Announcements 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 Write Release Announcements 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Write Release Announcements use?
Write Release Announcements 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 Write Release Announcements use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.
What are the alternatives to Write Release Announcements?
Skills that share tags, products or a category with Write Release Announcements: Maintain DisCatSharp (Aiko-IT-Systems/DisCatSharp, 140 stars), .NET Release Verification (dotnet/core, 22k stars), Add Analyzer (dotnet/roslynator, 3.5k stars) and Generate .NET Release changes.json (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Release Announcements?
Gremlinq (a GitHub organization) maintains it in Gremlinq/ExRam.Gremlinq, which has 187 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: Gremlinq/ExRam.Gremlinq on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.