Release TS SDK
aptos-labs/aptos-ts-sdk
A skill your agent uses when cutting a release of @aptos-labs/ts-sdk or @aptos-labs/confidential-asset.
Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.
Install Release
$ npx skills add OvenMediaLabs/OvenPlayer --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OvenMediaLabs/OvenPlayer release --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/OvenMediaLabs/OvenPlayer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/release && 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" agent skill from https://github.com/OvenMediaLabs/OvenPlayer/tree/master/.claude/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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/OvenMediaLabs/OvenPlayer/tree/master/.claude/skills/releaseType 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 OvenMediaLabs/OvenPlayer --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OvenMediaLabs/OvenPlayer release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OvenMediaLabs/OvenPlayer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release .agents/skills/release && 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" agent skill from https://github.com/OvenMediaLabs/OvenPlayer/tree/master/.claude/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 OvenMediaLabs/OvenPlayer --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OvenMediaLabs/OvenPlayer release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OvenMediaLabs/OvenPlayer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release .cursor/skills/release && 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" agent skill from https://github.com/OvenMediaLabs/OvenPlayer/tree/master/.claude/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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/OvenMediaLabs/OvenPlayer.git --path .claude/skills/release--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 OvenMediaLabs/OvenPlayer --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OvenMediaLabs/OvenPlayer release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OvenMediaLabs/OvenPlayer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release .gemini/skills/release && 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" agent skill from https://github.com/OvenMediaLabs/OvenPlayer/tree/master/.claude/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 OvenMediaLabs/OvenPlayer releaseInstalls 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 OvenMediaLabs/OvenPlayer --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OvenMediaLabs/OvenPlayer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release .github/skills/release && 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" agent skill from https://github.com/OvenMediaLabs/OvenPlayer/tree/master/.claude/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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 OvenMediaLabs/OvenPlayer --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OvenMediaLabs/OvenPlayer release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OvenMediaLabs/OvenPlayer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release .opencode/skills/release && 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" agent skill from https://github.com/OvenMediaLabs/OvenPlayer/tree/master/.claude/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", 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- GitHub stars
- 592
- Token cost
- ~1.3k tokens
- SKILL.md length
- 767 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.
- Works in 7 steps: Preflight → Confirm the version → Verify dist/ is final → …
- Tasks that involve Changelog and release notes
- SKILL.md covers 1. Preflight, 2. Confirm the version, 3. Verify dist/ is final and 4. Bump, if step 2 called for…, plus 3 more sections
- Calls gh, git and npm
What it does
Release is an agent skill from OvenMediaLabs/OvenPlayer. Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.
Its SKILL.md is about 1.3k 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 npm, GitHub, JavaScript and Git. The repository describes itself as: OvenPlayer is JavaScript-based LLHLS and WebRTC Player for OvenMediaEngine. The licence is MIT.
When your agent uses it
- Tasks that involve Changelog and release notes
Example prompts
- “/release”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5e4e71a. 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:
ghgitnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, git and npm, 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
Release loads about 1.3k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 767 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 OvenMediaLabs/OvenPlayer at commit 5e4e71a, republished under its MIT licence (© OvenMediaLabs). 767 words, ~1,303 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.
Release ovenplayer to npm.
The publish itself runs in CI: publishing the GitHub Release fires .github/workflows/publish.yml, which builds and publishes through npm trusted publishing (OIDC). This skill stops at a draft release. Nothing reaches npm until that draft is published, and publishing it is the user's call — see step 6.
1. Preflight
git status --shortandgit log --oneline -10. Work frommaster, with a clean tree, synced with origin (git fetch && git status -sb). Surface anything unexpected — stray modified files, unpushed commits — and ask how to proceed before continuing.- Establish the baseline with
gh release list --limit 3andnpm view ovenplayer version. Do not usegit describefor this: some tags in this repo do not sit onmaster, so it reports the wrong baseline.
2. Confirm the version
- This repo bumps
package.jsoninside the feature commit rather than in a separate release commit, so the version is often already ahead of npm. Comparepackage.jsonagainst the published version first — a bump may not be needed. - List the commits since the last release, group them into features / fixes / chores, and propose the version from that.
- Show the published version, the version in
package.json, the proposal, and the commit list. Ask the user to confirm. Never pick the version silently.
3. Verify dist/ is final
dist/ is committed to the repo and served to jsdelivr consumers, and webpack
inlines the package.json version into the bundle as __VERSION__
(webpack.config.js:86). A version bump therefore
invalidates the committed bundle.
- Run
npm run build, thengit status --short dist/.- Clean → the committed bundle matches
src/at this version. Say so. - Dirty → the committed bundle was stale. Commit the rebuild before tagging
(
chore: rebuild the bundle, or folded into the version-bump commit).
- Clean → the committed bundle matches
- Confirm the version embedded in the bundle is the version being released:
grep -o '0\.[0-9]*\.[0-9]*' dist/ovenplayer.js | sort -u.
4. Bump, if step 2 called for one
Update the version in package.json and package-lock.json, rebuild so dist/
carries the new __VERSION__, and commit them together. Match the commit style
in git log. Push before tagging.
5. Write the release notes
- Read the previous two or three releases (
gh release view <tag>). They are hand-written and feature-first: what changed for the user, with code samples for new options. They are not a commit dump. Match that. - Draft from the actual diff since the last release, not from commit subjects alone. Show the draft and get the user's approval on it.
Show full SKILL.md (361 more words)Show less
6. Create the release as a draft
Always create it as a draft, even when the user is ready to release. publish.yml
fires on release: published, so a draft publishes nothing — it is a free
checkpoint for reading the notes as GitHub renders them.
gh release create v<version> --draft --target master --title "v<version>" --notes-file <file>(the tag must bev<version>— CI checks it againstpackage.json).- Give the user the draft URL and let them read it. Editing a draft triggers
nothing, so iterate freely:
gh release edit v<version> --notes-file <file>resolves by tag name even before the tag exists. Theuntagged-...URL changes on every edit while the release id stays the same, so hand over the new link. - Do not publish the draft yourself unless the user explicitly asks. Publishing is
the point of no return: say plainly that it publishes to npm and that a
published version cannot be unpublished or replaced. Normally the user presses
Publish release in the GitHub UI; on request it is
gh release edit v<version> --draft=false --latest. - The tag is created at publish time, pointing at
masterHEAD then — not at the commit that was HEAD when the draft was made. If master moved in between, re-check the version anddist/.
7. Watch the publish
gh run list --workflow=publish.yml --limit 1, thengh run watch <id>, and confirm withnpm view ovenplayer version.404 Not Found - PUTis an authentication failure, not a missing package. Check the trusted publisher config on npmjs.com first — package → Settings → Trusted Publisher, with repoOvenMediaLabs/OvenPlayer, workflowpublish.yml, environment blank — before touchingpublish.yml. npm does not validate that config when it is saved, so a typo only surfaces here.- Retry with
gh run rerun <id>. Thepublishedevent cannot be re-fired, and a re-run replays it with fresh OIDC tokens, so the release and tag can stay as they are. This only works when the fix is outside the repo: a re-run uses the workflow file from the tagged commit, so a change topublish.ymlitself is not picked up. - If the version already landed on npm, do not attempt to republish it — the next release needs a new version.
© OvenMediaLabs, 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 .claude/skills/release of OvenMediaLabs/OvenPlayer.
Open the folder on GitHubat commit 5e4e71a
Compare with similar skills
Release 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 this skillOvenMediaLabs/OvenPlayer | 592 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Release TS SDKaptos-labs/aptos-ts-sdk | 116 | — | ~864 | Automated safety check: Pass | Custom licence | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.6k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Release Roundethereumjs/ethereumjs-monorepo | 2.8k | — | ~2k | Automated safety check: Pass | None | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | 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.
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.
Release Round
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
Release Workflow
Caldis/react-zmage
A skill your agent uses when the user wants to ship a new version of react-zmage to npm.
Related
Works with
Categories
Questions about Release
What does Release do?
Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish. Release is an agent skill from OvenMediaLabs/OvenPlayer. Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.
When should I use Release?
Release fits situations like: tasks that involve Changelog and release notes.
How do I install Release in Claude Code?
Run `npx skills add OvenMediaLabs/OvenPlayer --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in OvenMediaLabs/OvenPlayer) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.
How do I install Release in Codex?
Run `npx skills add OvenMediaLabs/OvenPlayer --skill release -a codex`. Or copy the skill folder (.claude/skills/release in OvenMediaLabs/OvenPlayer) into .agents/skills/release in your project. Codex loads it when a task matches its description.
Can I use Release 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 OvenMediaLabs/OvenPlayer --skill release -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, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.
What does Release need to run?
Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (gh, git and npm).
Does Release access the network?
SKILL.md contains no URLs. Its commands use gh, git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release 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 use?
Release 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 Release use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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?
Skills that share tags, products or a category with Release: Release TS SDK (aptos-labs/aptos-ts-sdk, 116 stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.6k stars) and Release Round (ethereumjs/ethereumjs-monorepo, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
OvenMediaLabs (a GitHub organization) maintains it in OvenMediaLabs/OvenPlayer, which has 592 GitHub stars. The repository was last updated on September 13, 2026.
Source: OvenMediaLabs/OvenPlayer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.