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.
Create a new version release for vidpipe. An agent skill from htekdev/vidpipe.
Install Release
$ npx skills add htekdev/vidpipe --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install htekdev/vidpipe 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/htekdev/vidpipe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/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/htekdev/vidpipe/tree/main/.github/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/htekdev/vidpipe/tree/main/.github/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 htekdev/vidpipe --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install htekdev/vidpipe release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htekdev/vidpipe.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/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/htekdev/vidpipe/tree/main/.github/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 htekdev/vidpipe --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install htekdev/vidpipe release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htekdev/vidpipe.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/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/htekdev/vidpipe/tree/main/.github/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/htekdev/vidpipe.git --path .github/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 htekdev/vidpipe --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install htekdev/vidpipe release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htekdev/vidpipe.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/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/htekdev/vidpipe/tree/main/.github/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 htekdev/vidpipe 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 htekdev/vidpipe --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/htekdev/vidpipe.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/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/htekdev/vidpipe/tree/main/.github/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 htekdev/vidpipe --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 htekdev/vidpipe release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/htekdev/vidpipe.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/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/htekdev/vidpipe/tree/main/.github/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
- 228
- Token cost
- ~817 tokens
- SKILL.md length
- 330 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Create a new version release for vidpipe. An agent skill from htekdev/vidpipe.
- Works in 9 steps: Determine Version Bump → Bump Version → Build and Test → …
- Asked to release
- SKILL.md covers Prerequisites, Release Workflow and Important Notes
- Calls npm, git and gh
What it does
Release is an agent skill from htekdev/vidpipe. Create a new version release for vidpipe. Use this skill when asked to release, version, tag, or create a new version. Handles version bump, changelog generation, GitHub release, and npm publishing.
Its SKILL.md is about 820 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 and Git. The repository describes itself as: CLI tool that auto-processes video recordings: transcribes, removes silence, generates captions, creates shorts, social posts, and more.
When your agent uses it
- Asked to release
- Create a new version
Example prompts
- “/release”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
- Determine Version Bump
- Bump Version
- Build and Test
- Commit Version Bump
- Create Git Tag
- Generate Release Notes
- Create GitHub Release
- Publish to npm
- Verify
What it can do on your machine
Read from SKILL.md and the folder at commit 99a5378. 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:
npmgitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, 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
Release loads about 817 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 330 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 330 words (~817 tokens).
“Complete workflow for creating a new versioned release of vidpipe, including version bump, release notes, GitHub release, and npm publishing.”
- name
- release
Files
Just SKILL.md in .github/skills/release of htekdev/vidpipe.
Open the folder on GitHubat commit 99a5378
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 skillhtekdev/vidpipe | 228 | — | ~817 | Automated safety check: Pass | None | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Release Clawpatchopenclaw/clawpatch | 813 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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.
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.
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
Release Clawpatch
openclaw/clawpatch
clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.
Release
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.
More from htekdev/vidpipe
Late API
htekdev/vidpipe
Manage Late.co social media scheduling API — list, reschedule, bulk delete, and sync scheduled posts.
Video Review
htekdev/vidpipe
Review and inspect video files using Gemini AI vision. An agent skill from htekdev/vidpipe.
npm Publish
htekdev/vidpipe
Publish packages to npm registry. An agent skill from htekdev/vidpipe.
Related
Categories
Questions about Release
What does Release do?
Create a new version release for vidpipe. An agent skill from htekdev/vidpipe. Release is an agent skill from htekdev/vidpipe. Create a new version release for vidpipe.
When should I use Release?
Release fits situations like: asked to release; create a new version.
How do I install Release in Claude Code?
Run `npx skills add htekdev/vidpipe --skill release -a claude-code`. Or copy the skill folder (.github/skills/release in htekdev/vidpipe) 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 htekdev/vidpipe --skill release -a codex`. Or copy the skill folder (.github/skills/release in htekdev/vidpipe) 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 htekdev/vidpipe --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 (npm, git and gh).
Does Release access the network?
SKILL.md contains no URLs. Its commands use npm, git and gh, 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?
No licence was found for Release or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Release use?
About 817 tokens (SKILL.md is roughly 3.3k 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: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars) and ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
htekdev (a GitHub user) maintains it in htekdev/vidpipe, which has 228 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 3, 2026.
Source: htekdev/vidpipe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.