Megaphone Release
Kuberwastaken/megaphone
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…
Install Release Readiness Review
$ npx skills add kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics release-readiness-review --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/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-readiness-review .claude/skills/release-readiness-review && 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-readiness-review" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/release-readiness-review into .claude/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", 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/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/release-readiness-reviewType 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 kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics release-readiness-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-readiness-review .agents/skills/release-readiness-review && 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-readiness-review" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/release-readiness-review into .agents/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", 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 kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics release-readiness-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-readiness-review .cursor/skills/release-readiness-review && 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-readiness-review" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/release-readiness-review into .cursor/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", 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/kernitus/BukkitOldCombatMechanics.git --path .agents/skills/release-readiness-review--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 kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics release-readiness-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-readiness-review .gemini/skills/release-readiness-review && 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-readiness-review" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/release-readiness-review into .gemini/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", 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 kernitus/BukkitOldCombatMechanics release-readiness-reviewInstalls 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 kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-readiness-review .github/skills/release-readiness-review && 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-readiness-review" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/release-readiness-review into .github/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", 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 kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kernitus/BukkitOldCombatMechanics release-readiness-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kernitus/BukkitOldCombatMechanics.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-readiness-review .opencode/skills/release-readiness-review && 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-readiness-review" agent skill from https://github.com/kernitus/BukkitOldCombatMechanics/tree/master/.agents/skills/release-readiness-review into .opencode/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", 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-readiness-review- GitHub stars
- 225
- Token cost
- ~1.5k tokens
- SKILL.md length
- 704 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…
- Works in 6 steps: Confirm secrets are referenced by… → Confirm the built jar path and uploaded… → Before the Release Please pull request… → …
- CurseForge/BukkitDev upload
- SKILL.md covers When to use, When not to use, Current release notes and Review checklist, plus 3 more sections
- Needs HANGAR_API_TOKEN
What it does
Release Readiness Review is an agent skill from kernitus/BukkitOldCombatMechanics. Use for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for day-to-day feature implementation, test authoring, or PR prose only.
Its SKILL.md is about 1.5k 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 Product & Project Management, covering Feature launches and release readiness and Changelog and release notes. It works with GitHub and Gradle. The repository describes itself as: Minecraft plugin to configure combat mechanics for 1.9 onwards. The licence is MPL-2.0.
When your agent uses it
- CurseForge/BukkitDev upload
- Spigot release handoff
- Supported-version
- Workflow readiness checks
Example prompts
- “/release-readiness-review”
Requirements
- A credential in HANGAR_API_TOKEN
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Confirm secrets are referenced by environment variable or GitHub secret name, never hard-coded.
- Confirm the built jar path and uploaded asset path match.
- Before the Release Please pull request is merged, review paperVersions against the supported Paper range and review gameVersions against…
- Confirm shaded dependency licence implications are reflected in release notes or README where needed.
- Confirm workflow changes do not alter plugin runtime behaviour.
- Prefer dry, static checks unless the user explicitly requests a release run.
What it can do on your machine
Read from SKILL.md and the folder at commit e66e7a9. 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 (its code samples are markdown).
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 these keys or tokens, usually read from environment variables:
HANGAR_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Readiness Review loads about 1.5k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 704 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 kernitus/BukkitOldCombatMechanics at commit e66e7a9, republished under its MPL-2.0 licence (© kernitus). 704 words, ~1,514 tokens.
Download SKILL.mdSave it as
.claude/skills/release-readiness-review/SKILL.md (or your agent's skills folder).- name
- release-readiness-review
- description
- Use for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for day-to-day feature implementation, test authoring, or PR prose only.
Release Readiness Review
Use this skill before changing or reviewing release workflows, publishing metadata, supported game versions, licence notes, and final release assets.
When to use
- Editing
.github/workflows/*release*or publishing-related Gradle configuration. - Checking Hangar, CurseForge/BukkitDev, or GitHub release upload behaviour.
- Reviewing licence implications of shaded dependencies such as PacketEvents.
- Updating supported Minecraft versions,
gradle.propertiesrelease metadata, or asset names. - Preparing a release-readiness checklist for maintainers.
When not to use
- Do not use for ordinary implementation or test selection; use the feature-specific skill.
- Do not use for PR description wording unless release notes are the main task; use
pr-draft-summary. - Do not use for module config behaviour unless it affects packaging or documented release defaults.
Current release notes
- GitHub release asset uses stable filename
OldCombatMechanics.jarwithout a version suffix. - Release Please uses the
javastrategy. After each stable release it opens a separateautorelease: snapshotpull request that updates the Gradle version to the next-SNAPSHOTversion. Merge that pull request before expecting development builds to publish to Hangar; while it remains pending, Release Please prioritises it over the next stable release pull request. - Release Please parses the merged release PR body to create the GitHub release. Keep its release section aligned with
CHANGELOG.md; useuser-facing-changelogfor the wording and synchronisation procedure. - The published GitHub release body is passed to CurseForge and Hangar through
github.event.release.body. - CurseForge upload uses the same path.
- Bukkit-compatible CurseForge game-version entries use
1:<version>prefixes so type-1 Bukkit versions are selected. gradle.propertieskeeps platform metadata separate.paperVersionsis the Hangar range andgameVersionsis the exact CurseForge Bukkit-version list.- Hangar supports ranges and wildcards. Keep
paperVersionsaligned with the complete supported Paper range; its current value is1.9-26.2. - Before merging every Release Please pull request, compare
gameVersionswith the current stable Bukkit versions offered by CurseForge. Include every supported stable subversion and exclude every entry labelledSnapshot. - Hangar publish configuration expects
HANGAR_API_TOKEN. - README licence note: source remains MPL-2.0; pre-built jars bundling PacketEvents are distributed under GPLv3; builds without PacketEvents can remain MPL-2.0.
gameVersionscurrently covers every stable Bukkit version from 1.9 through 26.2.
Review checklist
- Confirm secrets are referenced by environment variable or GitHub secret name, never hard-coded.
- Confirm the built jar path and uploaded asset path match.
- Before the Release Please pull request is merged, review
paperVersionsagainst the supported Paper range and reviewgameVersionsagainst every exact stable Bukkit version offered by CurseForge. Confirm that no CurseForge entry labelledSnapshotis present. - Confirm shaded dependency licence implications are reflected in release notes or README where needed.
- Confirm workflow changes do not alter plugin runtime behaviour.
- Prefer dry, static checks unless the user explicitly requests a release run.
Show full SKILL.md (258 more words)Show less
Release note template
### Release readiness
- Asset: `OldCombatMechanics.jar`
- Platforms checked: GitHub / Hangar / CurseForge
- Supported game versions checked: Hangar range; CurseForge exact list
- Version metadata checked:
- Licence notes checked:
- Secrets touched: none / list variable names only
- Remaining manual steps:Final step: Spigot update details
When preparing or completing a release, finish by providing all four fields for Spigot's Post Resource Update form together. Also provide them when the user requests a Spigot release handoff. Do not add this handoff to unrelated workflow or licence questions.
- Direct download URL: Use the version-specific GitHub release asset URL for
OldCombatMechanics.jar, such ashttps://github.com/kernitus/BukkitOldCombatMechanics/releases/download/v<VERSION>/OldCombatMechanics.jar. Resolve the actual tag and asset from the intended release; do not use a moving latest-release URL. Verify the asset exists before presenting it as ready. If publishing has not completed, label the URL as pending and still prepare the remaining fields. - Version String: Use the stable release version without the tag's leading
v. Do not copy the next development-SNAPSHOTversion from the working branch. - Update Title: Provide a concise title containing the version and the main user-visible changes.
- Message: Provide one fenced
bbcodeblock ready to paste into the editor's BBCode mode. Convert the matching curated release notes using[b],[list],[*]and[url=...]tags. Preserve material compatibility limitations and useful issue links; omit Release Please's robot header and attribution. End with a link to the full GitHub release andReport issues on [url=https://github.com/kernitus/BukkitOldCombatMechanics/issues]GitHub[/url].
Use the published release body as the source, or the matching curated changelog section when publication is pending. Resolve material discrepancies before calling the message ready. Follow user-facing-changelog when rewriting the prose, retaining British English. Keep the handoff in chat unless the user requests a file. Preparing these fields does not authorise website submission.
References
- Broader historical notes:
../integration-test-verification/references/relocated-agents-notes.md.
© kernitus, MPL-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/release-readiness-review of kernitus/BukkitOldCombatMechanics.
Open the folder on GitHubat commit e66e7a9
Compare with similar skills
Release Readiness Review 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 Readiness Review this skillkernitus/BukkitOldCombatMechanics | 225 | — | ~1.5k | Automated safety check: Pass | MPL-2.0 | |
| Megaphone ReleaseKuberwastaken/megaphone | 170 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Create Release Checklistsoftware-mansion/smelter | 734 | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Doc View Release Readinessliuzhihang/doc-view | 207 | — | ~494 | Automated safety check: Pass | MIT | |
| Release MaintainerUndertone0809/rudder | 292 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Release Swiftrobinebers/openusage | 4.3k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Create Release Checklist
software-mansion/smelter
Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.
Doc View Release Readiness
liuzhihang/doc-view
A skill your agent uses when preparing, checking, or reviewing a Doc View plugin release, including changelog, version, plugin verification, manual IDE validation, Marketplace preparation, and…
Release Maintainer
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
Release Swift
robinebers/openusage
Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes.
Release
sol4k/sol4k
Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.
More from kernitus/BukkitOldCombatMechanics
All 9 skills in this repoIntegration Test Verification
kernitus/BukkitOldCombatMechanics
A skill your agent uses when running, selecting, authoring, or triaging integration tests, Kotest specs, Gradle matrix tasks, FakePlayer-backed test cases, or compact test-result files; do not use…
Dependabot PR Review
kernitus/BukkitOldCombatMechanics
A skill your agent uses for Dependabot PRs, dependency bumps, Gradle or Maven dependency updates, GitHub Actions updates, dependency changelog/licence/release-note review, JVM/classfile checks, and…
Module Config Change
kernitus/BukkitOldCombatMechanics
A skill your agent uses for config.yml, module enablement, modesets, config migration, configurable module assignment, and per-module option changes; do not use for unrelated integration-test…
PR Draft Summary
kernitus/BukkitOldCombatMechanics
A skill your agent uses when drafting pull-request titles, descriptions, change summaries, risk notes, validation sections, or reviewer handoff text; do not use for implementation design, release…
User Facing Changelog
kernitus/BukkitOldCombatMechanics
A skill your agent uses when rewriting CHANGELOG.md, GitHub release notes, or Release Please PR changelog sections into user-facing release notes; do not use for release publishing, assets, licence…
Compatibility Strategy
kernitus/BukkitOldCombatMechanics
A skill your agent uses for Java 8 backports, Bukkit/Paper version differences, NMS/reflection, PacketEvents compatibility, fake-player implementation choices, and feature-detection design; do not…
Related
Categories
Questions about Release Readiness Review
What does Release Readiness Review do?
A skill your agent uses for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for…. Release Readiness Review is an agent skill from kernitus/BukkitOldCombatMechanics. Use for GitHub release, Hangar, CurseForge/BukkitDev upload, Spigot release handoff, licence, asset naming, supported-version, and workflow readiness checks; do not use for day-to-day feature implementation, test authoring, or PR prose only.
When should I use Release Readiness Review?
Release Readiness Review fits situations like: curseForge/BukkitDev upload; spigot release handoff; supported-version; workflow readiness checks.
How do I install Release Readiness Review in Claude Code?
Run `npx skills add kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a claude-code`. Or copy the skill folder (.agents/skills/release-readiness-review in kernitus/BukkitOldCombatMechanics) into .claude/skills/release-readiness-review in your project. Claude Code loads it when a task matches its description.
How do I install Release Readiness Review in Codex?
Run `npx skills add kernitus/BukkitOldCombatMechanics --skill release-readiness-review -a codex`. Or copy the skill folder (.agents/skills/release-readiness-review in kernitus/BukkitOldCombatMechanics) into .agents/skills/release-readiness-review in your project. Codex loads it when a task matches its description.
Can I use Release Readiness Review 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 kernitus/BukkitOldCombatMechanics --skill release-readiness-review -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-readiness-review, .gemini/skills/release-readiness-review, .github/skills/release-readiness-review and .opencode/skills/release-readiness-review in your project.
What does Release Readiness Review need to run?
Going by SKILL.md and its folder, Release Readiness Review needs credentials named HANGAR_API_TOKEN. Our summary lists: A credential in HANGAR_API_TOKEN.
Does Release Readiness Review 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 Release Readiness Review 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 Release Readiness Review use?
Release Readiness Review is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Readiness Review use?
About 1.5k tokens (SKILL.md is roughly 6.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 Release Readiness Review?
Skills that share tags, products or a category with Release Readiness Review: Megaphone Release (Kuberwastaken/megaphone, 170 stars), Create Release Checklist (software-mansion/smelter, 734 stars), Doc View Release Readiness (liuzhihang/doc-view, 207 stars) and Release Maintainer (Undertone0809/rudder, 292 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Readiness Review?
kernitus (a GitHub user) maintains it in kernitus/BukkitOldCombatMechanics, which has 225 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 4, 2026.
Source: kernitus/BukkitOldCombatMechanics on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.