Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Cut (publish) a release of meshery-operator by publishing the current Release Drafter draft with the gh CLI.
Install Cut Release
$ npx skills add meshery/meshery-operator --skill cut-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install meshery/meshery-operator cut-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/meshery/meshery-operator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cut-release .claude/skills/cut-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 "cut-release" agent skill from https://github.com/meshery/meshery-operator/tree/master/.claude/skills/cut-release into .claude/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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/meshery/meshery-operator/tree/master/.claude/skills/cut-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 meshery/meshery-operator --skill cut-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install meshery/meshery-operator cut-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meshery/meshery-operator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/cut-release .agents/skills/cut-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 "cut-release" agent skill from https://github.com/meshery/meshery-operator/tree/master/.claude/skills/cut-release into .agents/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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 meshery/meshery-operator --skill cut-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install meshery/meshery-operator cut-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meshery/meshery-operator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/cut-release .cursor/skills/cut-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 "cut-release" agent skill from https://github.com/meshery/meshery-operator/tree/master/.claude/skills/cut-release into .cursor/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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/meshery/meshery-operator.git --path .claude/skills/cut-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 meshery/meshery-operator --skill cut-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install meshery/meshery-operator cut-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meshery/meshery-operator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/cut-release .gemini/skills/cut-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 "cut-release" agent skill from https://github.com/meshery/meshery-operator/tree/master/.claude/skills/cut-release into .gemini/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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 meshery/meshery-operator cut-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 meshery/meshery-operator --skill cut-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/meshery/meshery-operator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/cut-release .github/skills/cut-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 "cut-release" agent skill from https://github.com/meshery/meshery-operator/tree/master/.claude/skills/cut-release into .github/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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 meshery/meshery-operator --skill cut-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 meshery/meshery-operator cut-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/meshery/meshery-operator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/cut-release .opencode/skills/cut-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 "cut-release" agent skill from https://github.com/meshery/meshery-operator/tree/master/.claude/skills/cut-release into .opencode/skills/cut-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cut-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
cut-release- GitHub stars
- 151
- Token cost
- ~1.4k tokens
- SKILL.md length
- 599 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Cut (publish) a release of meshery-operator by publishing the current Release Drafter draft with the gh CLI.
- Works in 4 steps: Confirm the Release Drafter run for the… → Identify and inspect the draft → Publish the draft → …
- Asks to cut a release
- SKILL.md covers How releasing works in this repo, Steps and What to watch for
- Calls gh and git
What it does
Cut Release is an agent skill from meshery/meshery-operator. Cut (publish) a release of meshery-operator by publishing the current Release Drafter draft with the gh CLI. Use this whenever the user asks to "cut a release", "publish the release", "ship a release", "release meshery-operator", "release the operator", "do a release", "release the latest merge", or wants the recently merged PR to go out. Handles waiting for the Release Drafter workflow to fold the just-merged PR into the draft notes, then flipping the draft to published so the multi-platform Docker build and the…
Its SKILL.md is about 1.4k 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 DevOps & Cloud, covering Containers. It works with Docker, GitHub Actions and Kubernetes. The repository describes itself as: Meshery Operator is a Kubernetes Operator that deploys and manages the lifecycle of two Meshery components critical to Meshery's operations of Kubernetes clusters. The licence is Apache-2.0.
When your agent uses it
- Asks to cut a release
- Publish the release
- Release meshery-operator
- Release the operator
Example prompts
- “cut a release”
- “publish the release”
- “ship a release”
- “/cut-release”
Requirements
- Docker
Workflow steps
4 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 632cd41. 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:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, 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
Cut Release loads about 1.4k tokens when it runs. Until then it costs about 177 tokens; SKILL.md has 599 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 meshery/meshery-operator at commit 632cd41, republished under its Apache-2.0 licence (© meshery). 599 words, ~1,415 tokens.
Download SKILL.mdSave it as
.claude/skills/cut-release/SKILL.md (or your agent's skills folder).- name
- cut-release
- description
- Cut (publish) a release of meshery-operator by publishing the current Release Drafter draft with the gh CLI. Use this whenever the user asks to "cut a release", "publish the release", "ship a release", "release meshery-operator", "release the operator", "do a release", "release the latest merge", or wants the recently merged PR to go out. Handles waiting for the Release Drafter workflow to fold the just-merged PR into the draft notes, then flipping the draft to published so the multi-platform Docker build and the downstream CRD/ chart sync workflows fire. The version tag is already set by Release Drafter and auto-increments after each release, so this skill never creates or bumps a tag.
Cut a meshery-operator release
Publishing a release here is intentionally a one-action step: flip the existing Release Drafter draft from draft to published. Everything downstream is automated by GitHub Actions.
How releasing works in this repo
.github/workflows/release-drafter.ymlruns on every push tomaster. As PRs merge, it maintains a single draft GitHub Release whose tag auto-increments (the patch version bumps after each publish). There is always exactly one draft waiting to be published. This repo publishes immutable releases (assets cannot be added after publish), so the drafter also attaches the rendered CRD bundles to the draft on every master push - that is the canonical asset path, and it is why you must never hand-create the release.- Publishing that draft (the release
publishedevent) triggers:.github/workflows/multi-platform.yml- builds the multi-architecture operator container images and pushes them to the registry, tagged with the released version..github/workflows/sync-downstream.yml- renders the CRD bundles, syncs the CRDs + chart versions intomeshery/meshery's Helm charts, and publishes the operator-versioned chart tooci://ghcr.io/meshery/charts.
So the tag is already chosen and the notes are already drafted. Your job is only to make sure the just-merged PR is reflected in the draft, then publish it. Do not create a tag, do not bump a version, do not write release notes by hand - Release Drafter owns all of that.
Steps
1. Confirm the Release Drafter run for the latest master commit has finished
The draft only includes a PR after the drafter workflow run for that merge commit completes. If you publish too early, the just-merged PR is missing from the notes.
# Latest master commit that should be in the release
git fetch origin master --quiet && git rev-parse origin/master
# Most recent Release Drafter runs (headSha should match origin/master, status "completed")
gh run list --workflow="release-drafter.yml" --branch master --limit 3 \
--json databaseId,status,conclusion,headSha,createdAtIf the run for the current origin/master SHA is still in_progress (or absent because the
push just landed), wait for it before publishing:
gh run watch <databaseId> --exit-statusA conclusion of success for the run whose headSha matches origin/master means the draft
is up to date (and its CRD bundles are attached). If the latest run failed, stop and surface
that - do not publish stale notes or a draft missing its CRD assets.
Show full SKILL.md (272 more words)Show less
2. Identify and inspect the draft
# Tag of the current draft (there is normally exactly one)
gh release list --limit 25 --json tagName,isDraft --jq '.[] | select(.isDraft) | .tagName'
# Read the draft notes and confirm the recently merged PR appears in them
gh release view <draftTag> --json tagName,name,isDraft,body --jq \
'{tag: .tagName, name: .name, isDraft: .isDraft, body: .body}'Verify the merged PR the user is releasing shows up under one of the category headings. If it does not, the drafter run from step 1 has not yet indexed it - re-check step 1 rather than publishing without it.
If more than one draft is ever returned, stop and ask the user which to publish rather than guessing - publishing the wrong one ships an unintended version.
3. Publish the draft
Flipping --draft=false publishes it and fires the published event that drives the
multi-platform image build and the downstream CRD/chart sync. Mark it --latest so it carries
the "Latest" badge.
gh release edit <draftTag> --draft=false --latest4. Confirm it published
gh release view <draftTag> --json tagName,isDraft,isLatest,publishedAt --jq \
'{tag: .tagName, isDraft: .isDraft, isLatest: .isLatest, publishedAt: .publishedAt}'isDraft: false and a non-null publishedAt confirm the release is out. Report the published
version to the user and note that the multi-platform Docker build and the downstream CRD +
Helm-chart sync workflows have been triggered by the release event.
What to watch for
- Don't publish ahead of the drafter run. The most common failure is publishing before the Release Drafter workflow has folded the merged PR into the notes, shipping a release whose notes omit the very change being released. Because releases here are immutable, the drafter also has to have attached the CRD bundles to the draft first. Step 1 exists to prevent exactly this.
- Never hand-author the tag or notes. If you find yourself computing a version number or writing changelog entries, something is wrong - Release Drafter already did both.
- One draft only. If
gh release listshows zero drafts, no drafter run has occurred since the last release; if it shows more than one, ask the user which to publish.
© meshery, Apache-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 .claude/skills/cut-release of meshery/meshery-operator.
Open the folder on GitHubat commit 632cd41
Compare with similar skills
Cut 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 |
|---|---|---|---|---|---|---|
| Cut Release this skillmeshery/meshery-operator | 151 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Data Processingaiskillstore/marketplace | 430 | 1 repos | ~720 | Automated safety check: Notes | MIT | |
| CI/CD Pipeline Principlesirahardianto/awesome-agv | 157 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Devops Automationrohitg00/awesome-claude-code-toolkit | 2.7k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Devops Excellencemajiayu000/spellbook | 286 | — | ~2.4k | Automated safety check: Notes | MIT |
Similar skills
Data Processing
aiskillstore/marketplace
Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.
CI/CD Pipeline Principles
irahardianto/awesome-agv
Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.
Devops Automation
rohitg00/awesome-claude-code-toolkit
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
Devops Excellence
majiayu000/spellbook
DevOps and CI/CD expert. An agent skill from majiayu000/spellbook.
Devops Deployment
yonatangross/orchestkit
A skill your agent uses when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code.
More from meshery/meshery-operator
All 8 skills in this repoIterate PR
meshery/meshery-operator
Iterate on a PR until CI passes. An agent skill from meshery/meshery-operator.
QA Test Planner
meshery/meshery-operator
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers.
Command Creator
meshery/meshery-operator
This skill should be used when creating a Claude Code slash command.
Gepetto
meshery/meshery-operator
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review.
Database Schema Designer
meshery/meshery-operator
Design robust, scalable database schemas for SQL and NoSQL databases.
Reducing Entropy
meshery/meshery-operator
Manual-only skill for minimizing total codebase size. An agent skill from meshery/meshery-operator.
Related
Works with
Categories
Questions about Cut Release
What does Cut Release do?
Cut (publish) a release of meshery-operator by publishing the current Release Drafter draft with the gh CLI. Cut Release is an agent skill from meshery/meshery-operator. Cut (publish) a release of meshery-operator by publishing the current Release Drafter draft with the gh CLI.
When should I use Cut Release?
Cut Release fits situations like: asks to cut a release; publish the release; release meshery-operator; release the operator.
How do I install Cut Release in Claude Code?
Run `npx skills add meshery/meshery-operator --skill cut-release -a claude-code`. Or copy the skill folder (.claude/skills/cut-release in meshery/meshery-operator) into .claude/skills/cut-release in your project. Claude Code loads it when a task matches its description.
How do I install Cut Release in Codex?
Run `npx skills add meshery/meshery-operator --skill cut-release -a codex`. Or copy the skill folder (.claude/skills/cut-release in meshery/meshery-operator) into .agents/skills/cut-release in your project. Codex loads it when a task matches its description.
Can I use Cut 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 meshery/meshery-operator --skill cut-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/cut-release, .gemini/skills/cut-release, .github/skills/cut-release and .opencode/skills/cut-release in your project.
What does Cut Release need to run?
Going by SKILL.md and its folder, Cut Release needs the command-line tools its instructions call (gh and git). Our summary lists: Docker.
Does Cut Release access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Cut 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 Cut Release use?
Cut Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cut Release use?
About 1.4k tokens (SKILL.md is roughly 5.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 Cut Release?
Skills that share tags, products or a category with Cut Release: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Data Processing (aiskillstore/marketplace, 430 stars), CI/CD Pipeline Principles (irahardianto/awesome-agv, 157 stars) and Devops Automation (rohitg00/awesome-claude-code-toolkit, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cut Release?
meshery (a GitHub organization) maintains it in meshery/meshery-operator, which has 151 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 21, 2026.
Source: meshery/meshery-operator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.