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.
A skill your agent uses when preparing, reviewing, or publishing a BuildReactor versioned GitHub release and extension artifacts.
Install Releases
$ npx skills add AdamNowotny/BuildReactor --skill releases -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AdamNowotny/BuildReactor releases --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/AdamNowotny/BuildReactor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/releases .claude/skills/releases && 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 "releases" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/releases into .claude/skills/releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releases", 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/AdamNowotny/BuildReactor/tree/main/.agents/skills/releasesType 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 AdamNowotny/BuildReactor --skill releases -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AdamNowotny/BuildReactor releases --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/releases .agents/skills/releases && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "releases" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/releases into .agents/skills/releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releases", 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 AdamNowotny/BuildReactor --skill releases -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AdamNowotny/BuildReactor releases --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/releases .cursor/skills/releases && 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 "releases" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/releases into .cursor/skills/releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releases", 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/AdamNowotny/BuildReactor.git --path .agents/skills/releases--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 AdamNowotny/BuildReactor --skill releases -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AdamNowotny/BuildReactor releases --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/releases .gemini/skills/releases && 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 "releases" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/releases into .gemini/skills/releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releases", 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 AdamNowotny/BuildReactor releasesInstalls 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 AdamNowotny/BuildReactor --skill releases -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/releases .github/skills/releases && 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 "releases" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/releases into .github/skills/releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releases", 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 AdamNowotny/BuildReactor --skill releases -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AdamNowotny/BuildReactor releases --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AdamNowotny/BuildReactor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/releases .opencode/skills/releases && 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 "releases" agent skill from https://github.com/AdamNowotny/BuildReactor/tree/main/.agents/skills/releases into .opencode/skills/releases/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releases", 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
releases- GitHub stars
- 138
- Token cost
- ~867 tokens
- SKILL.md length
- 377 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when preparing, reviewing, or publishing a BuildReactor versioned GitHub release and extension artifacts.
- Works in 9 steps: Inspect the commits since the previous… → Update the exact version in… → Run npm test, npm run typecheck, and git… → …
- Publishing a BuildReactor versioned GitHub release and extension artifacts
- SKILL.md covers Release Sequence, Release Workflow, Publishing Requirements and Useful Commands
- Calls gh, npm and git; needs CHROME_CLIENT_SECRET and CHROME_REFRESH_TOKEN
What it does
Releases is an agent skill from AdamNowotny/BuildReactor. Use when preparing, reviewing, or publishing a BuildReactor versioned GitHub release and extension artifacts.
Its SKILL.md is about 870 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. It works with GitHub and npm. The repository describes itself as: Developer notifications and dashboard (Google Chrome extension).
When your agent uses it
- Publishing a BuildReactor versioned GitHub release and extension artifacts
Example prompts
- “/releases”
Requirements
- Node.js
- A credential in CHROME_CLIENT_SECRET
- A credential in CHROME_REFRESH_TOKEN
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Inspect the commits since the previous version tag and write concise notes
- Update the exact version in package.json. Never edit package-lock.json
- Run npm test, npm run typecheck, and git diff --check.
- Commit the version bump before creating the tag.
- Create the GitHub release as a draft with gh release create.
- Push the version-bump commit to main.
- Create the matching v tag. A draft release may be represented as
- Monitor the Build and Release workflow with gh run list or gh run watch.
- Confirm the draft contains both versioned ZIP assets before publishing.
What it can do on your machine
Read from SKILL.md and the folder at commit 5ccb151. 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:
ghnpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, npm and git, 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 these keys or tokens, usually read from environment variables:
CHROME_CLIENT_SECRETCHROME_REFRESH_TOKENFIREFOX_JWT_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Releases loads about 867 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 377 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 377 words (~867 tokens).
“grouped under Features, Bug Fixes, and Development.”
- name
- releases
Files
Just SKILL.md in .agents/skills/releases of AdamNowotny/BuildReactor.
Open the folder on GitHubat commit 5ccb151
Compare with similar skills
Releases 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 |
|---|---|---|---|---|---|---|
| Releases this skillAdamNowotny/BuildReactor | 138 | — | ~867 | Automated safety check: Pass | Custom licence | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Update .NET Supported OS Matrixdotnet/core | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.6k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Version ReleaseNG-ZORRO/ng-zorro-antd | 9.2k | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
- Official
Update .NET Supported OS Matrix
dotnet/core
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
Version Release
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
Repomix Browser Extension Developer
yamadashy/repomix
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content…
More from AdamNowotny/BuildReactor
CI Services
AdamNowotny/BuildReactor
A skill your agent uses when adding or updating BuildReactor CI service adapters, response parsing, provider fields, service fixtures, or service-specific tests.
Testing
AdamNowotny/BuildReactor
A skill your agent uses when adding or updating BuildReactor Vitest or Playwright tests, especially extension page, service-worker, options, popup, dashboard, or CI-service coverage.
Related
Categories
Questions about Releases
What does Releases do?
A skill your agent uses when preparing, reviewing, or publishing a BuildReactor versioned GitHub release and extension artifacts. Releases is an agent skill from AdamNowotny/BuildReactor. Use when preparing, reviewing, or publishing a BuildReactor versioned GitHub release and extension artifacts.
When should I use Releases?
Releases fits situations like: publishing a BuildReactor versioned GitHub release and extension artifacts.
How do I install Releases in Claude Code?
Run `npx skills add AdamNowotny/BuildReactor --skill releases -a claude-code`. Or copy the skill folder (.agents/skills/releases in AdamNowotny/BuildReactor) into .claude/skills/releases in your project. Claude Code loads it when a task matches its description.
How do I install Releases in Codex?
Run `npx skills add AdamNowotny/BuildReactor --skill releases -a codex`. Or copy the skill folder (.agents/skills/releases in AdamNowotny/BuildReactor) into .agents/skills/releases in your project. Codex loads it when a task matches its description.
Can I use Releases 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 AdamNowotny/BuildReactor --skill releases -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/releases, .gemini/skills/releases, .github/skills/releases and .opencode/skills/releases in your project.
What does Releases need to run?
Going by SKILL.md and its folder, Releases needs the command-line tools its instructions call (gh, npm and git) and credentials named CHROME_CLIENT_SECRET, CHROME_REFRESH_TOKEN and FIREFOX_JWT_SECRET. Our summary lists: Node.js; A credential in CHROME_CLIENT_SECRET; A credential in CHROME_REFRESH_TOKEN.
Does Releases access the network?
SKILL.md contains no URLs. Its commands use gh, npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Releases 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 Releases use?
Releases 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 Releases use?
About 867 tokens (SKILL.md is roughly 3.5k 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 Releases?
Skills that share tags, products or a category with Releases: Cutting A Release (TriliumNext/Trilium, 38k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Update .NET Supported OS Matrix (dotnet/core, 22k stars) and Hunk Release Workflow (modem-dev/hunk, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Releases?
AdamNowotny (a GitHub user) maintains it in AdamNowotny/BuildReactor, which has 138 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 12, 2026.
Source: AdamNowotny/BuildReactor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.