Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly…
Install Create Release Tags
$ npx skills add kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kubernetes-sigs/cloud-provider-azure create-release-tags --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/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-release-tags .claude/skills/create-release-tags && 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 "create-release-tags" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/create-release-tags into .claude/skills/create-release-tags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-tags", 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/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/create-release-tagsType 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 kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kubernetes-sigs/cloud-provider-azure create-release-tags --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/create-release-tags .agents/skills/create-release-tags && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-release-tags" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/create-release-tags into .agents/skills/create-release-tags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-tags", 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 kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kubernetes-sigs/cloud-provider-azure create-release-tags --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/create-release-tags .cursor/skills/create-release-tags && 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 "create-release-tags" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/create-release-tags into .cursor/skills/create-release-tags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-tags", 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/kubernetes-sigs/cloud-provider-azure.git --path .agents/skills/create-release-tags--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 kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kubernetes-sigs/cloud-provider-azure create-release-tags --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/create-release-tags .gemini/skills/create-release-tags && 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 "create-release-tags" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/create-release-tags into .gemini/skills/create-release-tags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-tags", 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 kubernetes-sigs/cloud-provider-azure create-release-tagsInstalls 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 kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/create-release-tags .github/skills/create-release-tags && 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 "create-release-tags" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/create-release-tags into .github/skills/create-release-tags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-tags", 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 kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kubernetes-sigs/cloud-provider-azure create-release-tags --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/create-release-tags .opencode/skills/create-release-tags && 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 "create-release-tags" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/create-release-tags into .opencode/skills/create-release-tags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-release-tags", 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
create-release-tags- GitHub stars
- 294
- Token cost
- ~574 tokens
- SKILL.md length
- 199 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly…
- Works in 5 steps: Fetch the chosen remote and tags → Resolve the commit at the tip of… → Compute the next stable tag if one is… → …
- The user wants to tag a release
- SKILL.md covers Goal, Recommended Workflow, Commands and Notes, plus 2 more sections
- Runs Python scripts from its folder; calls git and python3
What it does
Create Release Tags is an agent skill from kubernetes-sigs/cloud-provider-azure, published by the product's own GitHub organization. Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly without checking out the branch. Use when the user wants to tag a release, create a version tag, or mentions release tagging, cutting a release, or bumping a patch version.
Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/create_release_tags.py`).
It sits in DevOps & Cloud, covering Container orchestration. It works with Kubernetes. The repository describes itself as: Cloud provider for Azure. The licence is Apache-2.0.
When your agent uses it
- The user wants to tag a release
- Create a version tag
- Mentions release tagging
- Cutting a release
Example prompts
- “/create-release-tags”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Fetch the chosen remote and tags
- Resolve the commit at the tip of /release-X.Y
- Compute the next stable tag if one is not given explicitly
- Create the tag pointing at that commit (no branch checkout required)
- Optionally push the tag to the remote
What it can do on your machine
Read from SKILL.md and the folder at commit 0201852. 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 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
gitpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use 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
Create Release Tags loads about 574 tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 199 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); the scripts in this folder are not scanned.
SKILL.md
The full file from kubernetes-sigs/cloud-provider-azure at commit 0201852, republished under its Apache-2.0 licence (© kubernetes-sigs). 199 words, ~574 tokens.
Download SKILL.mdSave it as
.claude/skills/create-release-tags/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- create-release-tags
- description
- Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly without checking out the branch. Use when the user wants to tag a release, create a version tag, or mentions release tagging, cutting a release, or bumping a patch version.
Push Release Tag
Goal
Cut a new stable release tag for a Kubernetes-style release branch:
- Branch:
release-X.Y - Tag:
vX.Y.Z(patch bump)
Recommended Workflow
Use scripts/create_release_tags.py to:
- Fetch the chosen remote and tags
- Resolve the commit at the tip of
<remote>/release-X.Y - Compute the next stable tag if one is not given explicitly
- Create the tag pointing at that commit (no branch checkout required)
- Optionally push the tag to the remote
Multiple branches can be tagged in parallel since the script never checks out or modifies the local working tree.
Commands
Replace <SKILL_DIR> with the path of this skill directory.
Plan only:
python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34Create the tag locally:
python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --createCreate and push the tag:
python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --pushNotes
- Default remote is
upstream. Override with--remote <name>. - If the branch name does not match
release-X.Y, pass--series X.Y. - Tags are annotated by default. Use
--signfor signed tags. --force-branchis a no-op kept for backward compatibility.
Manual Fallback
Fetch the remote branch and tags:
git fetch upstream --prune --tagsFind the latest stable tag merged into the branch:
git tag --merged upstream/release-1.34 --list 'v1.34.*' --sort=version:refname | grep -E '^v1\.34\.[0-9]+$' | tail -n1Create and push an annotated tag at the remote branch tip:
git tag -a -m "v1.34.7" v1.34.7 upstream/release-1.34
git push upstream v1.34.7Safety Checks
- Ensure the computed tag does not already exist.
- Push only the intended tag, not every local tag.
© kubernetes-sigs, 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
SKILL.md and 1 other file (scripts) in .agents/skills/create-release-tags of kubernetes-sigs/cloud-provider-azure.
- SKILL.md
- scripts/create_release_tags.py
Open the folder on GitHubat commit 0201852
Compare with similar skills
Create Release Tags 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 |
|---|---|---|---|---|---|---|
| Create Release Tags this skillkubernetes-sigs/cloud-provider-azure | 294 | — | ~574 | Automated safety check: Pass | Apache-2.0 | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere Multi-Tenant Managementkubesphere/kubesphere | 17k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Sim Helmsimstudioai/sim | 30k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Helm Chart ScaffoldingCybereason-Public/owLSM | 280 | 13 repos | ~381 | Automated safety check: Pass | GPL-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
Sim Helm
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
Helm Chart Scaffolding
Cybereason-Public/owLSM
Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
More from kubernetes-sigs/cloud-provider-azure
All 12 skills in this repo- Official
Run E2E Test
kubernetes-sigs/cloud-provider-azure
Parse a Go e2e test from tests/e2e/, translate each step to kubectl and az CLI commands, and interactively replay the test against a live cluster.
- Official
Build Images
kubernetes-sigs/cloud-provider-azure
Build cloud-provider-azure container images through the repo Makefile with explicit IMAGETAG and IMAGEREGISTRY inputs, optional make flag overrides, and opt-in bounded Docker or Podman retries.
- Official
Cherry Pick PR
kubernetes-sigs/cloud-provider-azure
Cherry-pick a merged pull request onto a release branch with Prow-style branch naming, manual conflict resolution, targeted validation, and GitHub PR creation.
- Official
Create Release Note Doc PR
kubernetes-sigs/cloud-provider-azure
Generate or update the documentation-site release note for a given tag, commit it on a branch, push it to a writable remote, and open a GitHub PR to the docs branch.
- Official
Cve Remediator V2
kubernetes-sigs/cloud-provider-azure
Raise Go modules to caller-supplied minimum fixed versions from CVE/GO findings in any format, per tracked module root, sync go.mod/go.sum and root vendor/, audit the source module graphs, run the…
- Official
Debug E2E Pipeline
kubernetes-sigs/cloud-provider-azure
Fetch and analyze Prow e2e pipeline failures for cloud-provider-azure.
Related
Works with
Categories
Questions about Create Release Tags
What does Create Release Tags do?
Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly…. Create Release Tags is an agent skill from kubernetes-sigs/cloud-provider-azure, published by the product's own GitHub organization.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly without checking out the branch.
When should I use Create Release Tags?
Create Release Tags fits situations like: the user wants to tag a release; create a version tag; mentions release tagging; cutting a release.
How do I install Create Release Tags in Claude Code?
Run `npx skills add kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a claude-code`. Or copy the skill folder (.agents/skills/create-release-tags in kubernetes-sigs/cloud-provider-azure) into .claude/skills/create-release-tags in your project. Claude Code loads it when a task matches its description.
How do I install Create Release Tags in Codex?
Run `npx skills add kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a codex`. Or copy the skill folder (.agents/skills/create-release-tags in kubernetes-sigs/cloud-provider-azure) into .agents/skills/create-release-tags in your project. Codex loads it when a task matches its description.
Can I use Create Release Tags 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 kubernetes-sigs/cloud-provider-azure --skill create-release-tags -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-release-tags, .gemini/skills/create-release-tags, .github/skills/create-release-tags and .opencode/skills/create-release-tags in your project.
What does Create Release Tags need to run?
Going by SKILL.md and its folder, Create Release Tags needs Python for the scripts in its folder and the command-line tools its instructions call (git and python3). Our summary lists: Python 3.
Does Create Release Tags access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Create Release Tags 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 Create Release Tags use?
Create Release Tags 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 Create Release Tags use?
About 574 tokens (SKILL.md is roughly 2.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 Create Release Tags?
Skills that share tags, products or a category with Create Release Tags: Kubeshark Installer (kubeshark/kubeshark, 12k stars), KubeSphere Multi-Tenant Management (kubesphere/kubesphere, 17k stars), Sim Helm (simstudioai/sim, 30k stars) and Helm Chart Scaffolding (Cybereason-Public/owLSM, 280 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create Release Tags?
kubernetes-sigs (a GitHub organization, an official publisher) maintains it in kubernetes-sigs/cloud-provider-azure, which has 294 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: kubernetes-sigs/cloud-provider-azure on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.