Agent skill

Cull Release

A skill your agent uses when orchestrating or resuming Cull's complete release cycle, reporting its current release state, or fulfilling an explicit Cull patch, minor, or major release request…

MITAuto-check passed

Install Cull Release

skills CLI

$ npx skills add glebis/claude-skills --skill cull-release -a claude-code

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

GitHub CLI

$ gh skill install glebis/claude-skills cull-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/glebis/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cull-release .claude/skills/cull-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/

Paste into Claude Code

Install the "cull-release" agent skill from https://github.com/glebis/claude-skills/tree/main/cull-release into .claude/skills/cull-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cull-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

$skill-installer install https://github.com/glebis/claude-skills/tree/main/cull-release

Type 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.

skills CLI

$ npx skills add glebis/claude-skills --skill cull-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills cull-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cull-release" agent skill from https://github.com/glebis/claude-skills/tree/main/cull-release into .agents/skills/cull-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cull-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.

skills CLI

$ npx skills add glebis/claude-skills --skill cull-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills cull-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cull-release .cursor/skills/cull-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cull-release" agent skill from https://github.com/glebis/claude-skills/tree/main/cull-release into .cursor/skills/cull-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cull-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

$ gemini skills install https://github.com/glebis/claude-skills.git --path cull-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add glebis/claude-skills --skill cull-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills cull-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cull-release .gemini/skills/cull-release && rm -rf skills-src

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

Paste into Gemini CLI

Install the "cull-release" agent skill from https://github.com/glebis/claude-skills/tree/main/cull-release into .gemini/skills/cull-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cull-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.

GitHub CLI

$ gh skill install glebis/claude-skills cull-release

Installs 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).

skills CLI

$ npx skills add glebis/claude-skills --skill cull-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/cull-release .github/skills/cull-release && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "cull-release" agent skill from https://github.com/glebis/claude-skills/tree/main/cull-release into .github/skills/cull-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cull-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.

skills CLI

$ npx skills add glebis/claude-skills --skill cull-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills cull-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cull-release .opencode/skills/cull-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cull-release" agent skill from https://github.com/glebis/claude-skills/tree/main/cull-release into .opencode/skills/cull-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cull-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: cull-release
GitHub stars: 389
Token cost: ~446 tokens
SKILL.md length: 194 words
Files: 6 (incl. scripts, references)
Skills in repo: 91
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when orchestrating or resuming Cull's complete release cycle, reporting its current release state, or fulfilling an explicit Cull patch, minor, or major release request…

Works in 8 steps: Resolve Cull from a matching current… → For a new release, require explicit… → Use cull-release-check. Stop on every… → …
Resuming Culls complete release cycle
SKILL.md covers Principle, Start or resume and Completion report
Runs Shell scripts from its folder

What it does

Cull Release is an agent skill from glebis/claude-skills. Use when orchestrating or resuming Cull's complete release cycle, reporting its current release state, or fulfilling an explicit Cull patch, minor, or major release request through verified GitHub and Homebrew distribution.

Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/phase-contracts.md` and `references/release-lessons-2026-09.md`).

It works with Homebrew and GitHub. The repository describes itself as: Collection of Claude Code skills for enhanced AI workflows. The licence is MIT.

When your agent uses it

Resuming Culls complete release cycle
Reporting its current release state
Fulfilling an explicit Cull patch
Major release request through verified GitHub and Homebrew distribution

Example prompts

“/cull-release”

Requirements

A Bash shell

Workflow steps

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

Resolve Cull from a matching current origin, absolute CULL_REPO, or
For a new release, require explicit patch|minor|major; never infer it.
Use cull-release-check. Stop on every blocker.
Use cull-release-prepare in its isolated worktree.
Use cull-release-publish after preparation. An explicit complete-release
Use cull-release-verify after GitHub publication and Homebrew promotion.
On interruption, derive the last verified state from commit, tag, workflow,
Route every mismatch or failed phase through cull-release-recover.

What it can do on your machine

Read from SKILL.md and the folder at commit 7524dff. 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
Ships 2 files in scripts/ (Shell), which the agent can run.
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cull Release loads about 446 tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 194 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~446
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.1k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from glebis/claude-skills at commit 7524dff, republished under its MIT licence (© glebis). 194 words, ~446 tokens.

Download SKILL.mdSave it as .claude/skills/cull-release/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: cull-release
description: Use when orchestrating or resuming Cull's complete release cycle, reporting its current release state, or fulfilling an explicit Cull patch, minor, or major release request through verified GitHub and Homebrew distribution.

Cull Release

Principle

Orchestrate Cull's repository-enforced phases; never recreate release logic in the skill. Read references/phase-contracts.md before acting.

Start or resume

Resolve Cull from a matching current origin, absolute CULL_REPO, or $HOME/ai_projects/cull.
For a new release, require explicit patch|minor|major; never infer it.
Use cull-release-check. Stop on every blocker.
Use cull-release-prepare in its isolated worktree.
Use cull-release-publish after preparation. An explicit complete-release request already authorizes publication: Do not ask for a second publication confirmation.
Use cull-release-verify after GitHub publication and Homebrew promotion.
On interruption, derive the last verified state from commit, tag, workflow, artifacts, release, and tap evidence. Resume the first incomplete phase; do not repeat completed work.
Route every mismatch or failed phase through cull-release-recover.

Before the first tag of a cycle, read references/release-lessons-2026-09.md — it documents the failure modes that cost four burned attempts in the v0.6.x cycle (record-anchor vs workflow-gate mismatch, dependabot staleness races, closed-bead bd filter, provenance type drift) and the exact tag-time sequence that avoids them.

Completion report

Report version, release commit, annotated tag object, workflow run, artifact hashes, release URL, Homebrew tap commit, and final post-publish-verified state. Do not print secret values.

Files

SKILL.md and 5 other files (scripts, references) in cull-release of glebis/claude-skills.

SKILL.md
agents/openai.yaml
references/phase-contracts.md
references/release-lessons-2026-09.md
scripts/install-suite.sh
scripts/install-suite.test.sh

Open the folder on GitHubat commit 7524dff

Compare with similar skills

Cull 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.

Cull Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cull Release this skillglebis/claude-skills	389	—	~446	Automated safety check: Pass	MIT	12 days ago
Mole CLI Release Flowtw93/Mole	70k	—	~2.5k	Automated safety check: Pass	GPL-3.0	today
Release Asc CLIrorkai/App-Store-Connect-CLI	7.7k	—	~2.4k	Automated safety check: Pass	MIT	today
Releaseeugene1g/agent-safehouse	2.1k	—	~3.5k	Automated safety check: Pass	Apache-2.0	8 days ago
Releasetrasta298/keifu	811	—	~1.2k	Automated safety check: Pass	MIT	2 mo ago
Release VersionGOODBOY008/r-shell	151	—	~4k	Automated safety check: Pass	MIT	yesterday

Similar skills

Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
70k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Release Asc CLI
rorkai/App-Store-Connect-CLI
Publish and verify a new release of the App-Store-Connect-CLI repository.
7.7k GitHub stars~2.4k tokensUpdated today
MobileAuto-check passed
Release
eugene1g/agent-safehouse
Run the local Agent Safehouse release flow: inspect commits since the last published release, propose the next SemVer version and changelog, present a dry-run for confirmation, then update…
2.1k GitHub stars~3.5k tokensUpdated 8 days ago
DevelopmentAuto-check passed
Release
trasta298/keifu
Create a new release with tag, GitHub release, and homebrew-tap update
811 GitHub stars~1.2k tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Release Version
GOODBOY008/r-shell
Release a new r-shell version and create a published GitHub release with contributor credits.
151 GitHub stars~4k tokensUpdated yesterday
DevelopmentAuto-check passed
Kanvibe Release Deploy
rookedsysc/kanvibe
A skill your agent uses whenever releasing or deploying KanVibe desktop from a clean, up-to-date dev checkout: ask only for the target version and release-note approval, then let the AI update…
143 GitHub stars~12k tokensUpdated today
DevelopmentAuto-check: notes

More from glebis/claude-skills

All 91 skills in this repo

PII Annotation and Agreement Scorer
glebis/claude-skills
Runs a human-first workflow for labeling PII spans in a transcript, then scores inter-annotator agreement and drafts an adjudicated gold set.
389 GitHub stars~1.3k tokensUpdated 12 days ago
Auto-check passed
Non-Destructive Chrome Automation
glebis/claude-skills
Automates a dedicated, logged-in Chrome instance per profile without ever closing the user's own open tabs or browser windows.
389 GitHub stars~973 tokensUpdated 12 days ago
Auto-check passed
Deep Research
glebis/claude-skills
This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.
389 GitHub stars~2.6k tokensUpdated 12 days ago
Auto-check: notes
Elimination Research
glebis/claude-skills
This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric…
389 GitHub stars~1.6k tokensUpdated 12 days ago
Auto-check passed
Narrated HTML Presentations
glebis/claude-skills
Generates a self-contained HTML presentation with article and slides modes, ElevenLabs voiceover narration and optional GPT Image 2 illustrations.
389 GitHub stars~2.3k tokensUpdated 12 days ago
Auto-check: notes
Synthetic Coaching Session Generator
glebis/claude-skills
Writes fictional but realistic coaching or therapy session transcripts for evals, demos and few-shot examples, in several modalities and export formats.
389 GitHub stars~2.9k tokensUpdated 12 days ago
Auto-check passed

Works with

Questions about Cull Release

What does Cull Release do?

A skill your agent uses when orchestrating or resuming Cull's complete release cycle, reporting its current release state, or fulfilling an explicit Cull patch, minor, or major release request…. Cull Release is an agent skill from glebis/claude-skills. Use when orchestrating or resuming Cull's complete release cycle, reporting its current release state, or fulfilling an explicit Cull patch, minor, or major release request through verified GitHub and Homebrew distribution.

When should I use Cull Release?

Cull Release fits situations like: resuming Culls complete release cycle; reporting its current release state; fulfilling an explicit Cull patch; major release request through verified GitHub and Homebrew distribution.

How do I install Cull Release in Claude Code?

Run `npx skills add glebis/claude-skills --skill cull-release -a claude-code`. Or copy the skill folder (cull-release in glebis/claude-skills) into .claude/skills/cull-release in your project. Claude Code loads it when a task matches its description.

How do I install Cull Release in Codex?

Run `npx skills add glebis/claude-skills --skill cull-release -a codex`. Or copy the skill folder (cull-release in glebis/claude-skills) into .agents/skills/cull-release in your project. Codex loads it when a task matches its description.

Can I use Cull 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 glebis/claude-skills --skill cull-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/cull-release, .gemini/skills/cull-release, .github/skills/cull-release and .opencode/skills/cull-release in your project.

What does Cull Release need to run?

Going by SKILL.md and its folder, Cull Release needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Cull Release 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 Cull 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Cull Release use?

Cull 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 Cull Release use?

About 446 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.

What are the alternatives to Cull Release?

Skills that share tags, products or a category with Cull Release: Mole CLI Release Flow (tw93/Mole, 70k stars), Release Asc CLI (rorkai/App-Store-Connect-CLI, 7.7k stars), Release (eugene1g/agent-safehouse, 2.1k stars) and Release (trasta298/keifu, 811 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cull Release?

glebis (a GitHub user) maintains it in glebis/claude-skills, which has 389 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on September 26, 2026.

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

Install Cull Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Cull Release

Principle

Start or resume

Completion report

Files

Compare with similar skills

Similar skills

More from glebis/claude-skills

Related

Questions about Cull Release