New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release

by vericontext in vericontext/vibeframe

Bump VibeFrame versions, regenerate release artifacts, run verification, and prepare a version commit.

MITAuto-check passedMedia & Creative

Install Release

skills CLI
$ npx skills add vericontext/vibeframe --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vericontext/vibeframe release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vericontext/vibeframe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.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/

Facts

Skill name
release
GitHub stars
174
Token cost
~1.2k tokens
SKILL.md length
521 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Bump VibeFrame versions, regenerate release artifacts, run verification, and prepare a version commit.

  • Works in 4 steps: Read the current root version → Bump the root package → Read the exact new version → …
  • Tasks that involve AI video generation
  • SKILL.md covers When Bumps Happen, Version Policy and Steps
  • Calls git, pnpm and jq

What it does

Release is an agent skill from vericontext/vibeframe. Bump VibeFrame versions, regenerate release artifacts, run verification, and prepare a version commit.

Its SKILL.md is about 1.2k 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 Media & Creative, covering AI video generation. The repository describes itself as: Frontier AI video generation for coding agents - Seedance, Runway, Veo, Kling on your own keys, behind a hard cost cap. CLI + MCP. The licence is MIT.

When your agent uses it

  • Tasks that involve AI video generation

Example prompts

  • “/release”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read the current root version
  2. Bump the root package
  3. Read the exact new version
  4. Set every workspace package to that exact version. Do not use `pnpm -r exec

What it can do on your machine

Read from SKILL.md and the folder at commit dc6dc19. 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:

    • git
    • pnpm
    • jq
    • bash
    • npm
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, pnpm, npm 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 1.2k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 521 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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 vericontext/vibeframe at commit dc6dc19, republished under its MIT licence (© vericontext). 521 words, ~1,168 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Bump VibeFrame versions, regenerate release artifacts, run verification, and prepare a version commit.

Release

Use this skill when the user asks Codex to cut a VibeFrame release.

The bump is one of patch, minor, or major. Default to patch when no bump is specified or when there is any doubt.

When Bumps Happen

Once per release, not once per PR. Ordinary feat: / fix: PRs merge to main without a version bump. This skill runs when you decide to release, and the single bump it produces must cover every commit since the last tag - git-cliff handles that automatically in step 7.

Check what the release will cover before starting:

bash
bash scripts/release-status.sh

That script is the single source of truth for release state. The push gate, the tag workflow, and the daily drift check all call it, so its answer is the same one CI will give.

Version Policy

VibeFrame is still in 0.x. patch is the default and by far the most common bump. minor is rare and must be explicitly justified — the shared push gate (scripts/pre-push-validate.sh) blocks a non-patch bump that lacks a Release-Type: trailer (see step 10).

  • patch: bug fixes, docs/tooling, UX polish, internal refactors, and most ordinary feat: / fix: commits. Use this unless a rule below clearly applies.
  • minor: new public CLI command namespace, new MCP tool family, public API contract additions, or a large product milestone.
  • major: breaking changes or an intentional 1.0 milestone.

When unsure, use patch.

Steps

  1. Read the current root version:

    bash
    jq -r '.version' package.json

  2. Bump the root package:

    bash
    npm version <patch|minor|major> --no-git-tag-version

  3. Read the exact new version:

    bash
    NEW_VERSION=$(jq -r '.version' package.json)

  4. Set every workspace package to that exact version. Do not use pnpm -r exec npm version for this step because recursive pnpm includes the root package.

    bash
    for dir in packages/cli packages/core packages/ai-providers packages/mcp-server packages/ui apps/web; do
  (cd "$dir" && npm version "$NEW_VERSION" --no-git-tag-version)
done

  5. Verify all package versions match:

    bash
    for f in package.json packages/*/package.json apps/*/package.json; do
  jq -r '.version' "$f"
done | sort -u

    The output must contain exactly one version.

  6. Build, regenerate references, lint, and test:

    bash
    pnpm build
pnpm gen:reference
pnpm lint
pnpm -F @vibeframe/cli exec vitest run --bail 1

  7. Generate the changelog for the new version:

    bash
    git-cliff --tag v$NEW_VERSION -o CHANGELOG.md

  8. Run the shared push gate:

    bash
    bash scripts/pre-push-validate.sh

  9. Stage the release files:

    bash
    git add package.json packages/*/package.json apps/*/package.json CHANGELOG.md docs/cli-reference.md

  10. Commit. For a patch bump, a plain message:

Show full SKILL.md (202 more words)Show less
bash
git commit -m "chore: bump version to $NEW_VERSION"

For a minor or major bump, the push gate requires a justification trailer in the commit body, or it blocks the push:

bash
git commit -m "chore: bump version to $NEW_VERSION" -m "Release-Type: minor: <why this is not a patch>"

Do not create a local tag. Do not push unless the user explicitly asks.

  1. The version commit reaches main via a PR, never a direct push (even though main allows admin bypass). Put it on a chore/release-$NEW_VERSION branch, open a PR, let CI go green, and merge:
bash
git switch -c chore/release-$NEW_VERSION
git push -u origin chore/release-$NEW_VERSION
gh pr create --fill --base main

  1. Tagging is automatic. Once the version commit lands on main and CI passes, the Create release tag workflow creates vX.Y.Z on its own. Before tagging it re-runs scripts/release-status.sh and refuses if feat: / fix: commits landed after the bump, or if CHANGELOG.md has no ## [X.Y.Z] entry. Do not create the tag by hand.

  2. Publishing stays manual. Run the Publish to npm workflow with the new tag.

    Tags pushed by a workflow cannot trigger another workflow, so the automatic tag never dispatches publish.yml - that is what keeps the "CI never publishes" policy intact. A human-created git push origin vX.Y.Z does trigger publish.yml, so do not push release tags manually.

If publishing is forgotten, the daily Release drift check workflow opens an issue comparing main, the latest tag, and the published npm versions.

© vericontext, 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 .agents/skills/release of vericontext/vibeframe.

Open the folder on GitHubat commit dc6dc19

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillvericontext/vibeframe174—~1.2kAutomated safety check: PassMIT
Video Generationbytedance/deer-flow83k4 repos~1.4kAutomated safety check: PassMIT
Video Shotseternityspring/reelbench-skills8682 repos~1.8kAutomated safety check: NotesApache-2.0
Video Cover Imageitwanger/toBeBetterJavaer18k—~3.3kAutomated safety check: PassNone
Seedancesongguoxs/seedance-prompt-skill2.9k1 repos~2.5kAutomated safety check: PassNone
HyperFrames Video Entry Pointheygen-com/hyperframes59k3 repos~5.2kAutomated safety check: PassApache-2.0

Similar skills

  • Video Generation

    bytedance/deer-flow

    Generates short videos from a structured JSON prompt, optionally guided by a reference image used as the first or last frame.

    83k GitHub starsUsed in 4 repos~1.4k tokens
    Media & CreativeAuto-check passed

  • Video Shots

    eternityspring/reelbench-skills

    拉片：把一条成片拆成逐镜头的分析表——每个镜头的时长、景别、类别、运镜、画面. An agent skill from eternityspring/reelbench-skills.

    868 GitHub starsUsed in 2 repos~1.8k tokens
    Media & CreativeAuto-check: notes

  • Video Cover Image

    itwanger/toBeBetterJavaer

    Generate matched 3:4, 16:9, and 4:3 short-video cover images from toBeBetterJavaer video scripts or AI/Java technical topics.

    18k GitHub stars~3.3k tokensUpdated today
    Media & CreativeAuto-check passed

  • Seedance

    songguoxs/seedance-prompt-skill

    This skill should be used when the user asks to "generate video prompts", "create Seedance prompts", "write video descriptions", mentions "Seedance", "seedance", "即梦", "即梦平台", "视频提示词", "视频生成"…

    2.9k GitHub starsUsed in 1 repo~2.5k tokens
    Media & CreativeAuto-check passed

  • HyperFrames Video Entry Point

    heygen-com/hyperframes

    Entry point for making, editing and rendering videos from HTML compositions with HyperFrames, routing each request to the right workflow.

    59k GitHub starsUsed in 3 repos~5.2k tokens
    Media & CreativeAuto-check passed

  • Lanshu Create AI Presenter Video

    cclank/lanshu-create-ai-presenter-video

    Turn a topic or finished script into a complete, publish-ready explainer video — led by an AI presenter from an authorized adult presenter image, or performed in one of nine visual explainer styles…

    2.5k GitHub stars~3.6k tokensUpdated yesterday
    Media & CreativeAuto-check passed

More from vericontext/vibeframe

  • Vibe Pipeline

    vericontext/vibeframe

    Author and run VibeFrame YAML pipelines with vibe run, checkpoints, and budget controls.

    174 GitHub stars~969 tokensUpdated 2 days ago
    Auto-check passed

  • Vibe Scene

    vericontext/vibeframe

    Author, repair, render, and inspect VibeFrame scene projects built from STORYBOARD.md and DESIGN.md.

    174 GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

  • Sync Check

    vericontext/vibeframe

    Check VibeFrame SSOT consistency across package versions, generated docs, model metadata, site counts, and agent host configs.

    174 GitHub stars~266 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Release

What does Release do?

Bump VibeFrame versions, regenerate release artifacts, run verification, and prepare a version commit. Release is an agent skill from vericontext/vibeframe. Bump VibeFrame versions, regenerate release artifacts, run verification, and prepare a version commit.

When should I use Release?

Release fits situations like: tasks that involve AI video generation.

How do I install Release in Claude Code?

Run `npx skills add vericontext/vibeframe --skill release -a claude-code`. Or copy the skill folder (.agents/skills/release in vericontext/vibeframe) 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 vericontext/vibeframe --skill release -a codex`. Or copy the skill folder (.agents/skills/release in vericontext/vibeframe) 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 vericontext/vibeframe --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 (git, pnpm, jq, bash, npm and gh).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git, npm 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?

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.2k tokens (SKILL.md is roughly 4.7k 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: Video Generation (bytedance/deer-flow, 83k stars), Video Shots (eternityspring/reelbench-skills, 868 stars), Video Cover Image (itwanger/toBeBetterJavaer, 18k stars) and Seedance (songguoxs/seedance-prompt-skill, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

vericontext (a GitHub organization) maintains it in vericontext/vibeframe, which has 174 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 5, 2026.

Source: vericontext/vibeframe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.