KubeShark for Kubernetes
LukasNiessen/kubernetes-skill
Keeps Kubernetes manifests, Helm charts and policies grounded by diagnosing six failure modes, such as insecure defaults and API drift, and loading only matching references.
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump…
Install Release Chart
$ npx skills add zabbix-community/helm-zabbix --skill release-chart -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zabbix-community/helm-zabbix release-chart --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/zabbix-community/helm-zabbix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-chart .claude/skills/release-chart && 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-chart" agent skill from https://github.com/zabbix-community/helm-zabbix/tree/main/.agents/skills/release-chart into .claude/skills/release-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-chart", 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/zabbix-community/helm-zabbix/tree/main/.agents/skills/release-chartType 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 zabbix-community/helm-zabbix --skill release-chart -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zabbix-community/helm-zabbix release-chart --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zabbix-community/helm-zabbix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-chart .agents/skills/release-chart && 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-chart" agent skill from https://github.com/zabbix-community/helm-zabbix/tree/main/.agents/skills/release-chart into .agents/skills/release-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-chart", 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 zabbix-community/helm-zabbix --skill release-chart -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zabbix-community/helm-zabbix release-chart --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zabbix-community/helm-zabbix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-chart .cursor/skills/release-chart && 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-chart" agent skill from https://github.com/zabbix-community/helm-zabbix/tree/main/.agents/skills/release-chart into .cursor/skills/release-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-chart", 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/zabbix-community/helm-zabbix.git --path .agents/skills/release-chart--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 zabbix-community/helm-zabbix --skill release-chart -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zabbix-community/helm-zabbix release-chart --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zabbix-community/helm-zabbix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-chart .gemini/skills/release-chart && 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-chart" agent skill from https://github.com/zabbix-community/helm-zabbix/tree/main/.agents/skills/release-chart into .gemini/skills/release-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-chart", 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 zabbix-community/helm-zabbix release-chartInstalls 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 zabbix-community/helm-zabbix --skill release-chart -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zabbix-community/helm-zabbix.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-chart .github/skills/release-chart && 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-chart" agent skill from https://github.com/zabbix-community/helm-zabbix/tree/main/.agents/skills/release-chart into .github/skills/release-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-chart", 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 zabbix-community/helm-zabbix --skill release-chart -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zabbix-community/helm-zabbix release-chart --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zabbix-community/helm-zabbix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-chart .opencode/skills/release-chart && 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-chart" agent skill from https://github.com/zabbix-community/helm-zabbix/tree/main/.agents/skills/release-chart into .opencode/skills/release-chart/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-chart", 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-chart- GitHub stars
- 132
- Token cost
- ~1.5k tokens
- SKILL.md length
- 688 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump…
- Works in 8 steps: Preconditions → Create the release branch → Run local tests → …
- Requests like release a new chart version
- SKILL.md covers Installing and invoking this…, 0. Preconditions, 1. Create the release branch and 2. Run local tests, plus 6 more sections
- Calls git and make
What it does
Release Chart is an agent skill from zabbix-community/helm-zabbix. Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump Chart.yaml/artifacthub-pkg.yml/values.yaml, regenerate docs, tag the release so CI publishes it). Trigger on requests like "release a new chart version", "cut a release", "bump the chart version", "publish v7.1.0", "prepare the next Zabbix chart release".
Its SKILL.md is about 1.5k 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 Container orchestration and Deployment. It works with Helm and Kubernetes. The repository describes itself as: Helm chart for Zabbix. The licence is Apache-2.0.
When your agent uses it
- Requests like release a new chart version
- Bump the chart version
- Prepare the next Zabbix chart release
Example prompts
- “release a new chart version”
- “cut a release”
- “bump the chart version”
- “/release-chart”
Workflow steps
8 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 be2dc44. 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:
gitmake
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
Release Chart loads about 1.5k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 688 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 zabbix-community/helm-zabbix at commit be2dc44, republished under its Apache-2.0 licence (© zabbix-community). 688 words, ~1,542 tokens.
Download SKILL.mdSave it as
.claude/skills/release-chart/SKILL.md (or your agent's skills folder).- name
- release-chart
- description
- Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump Chart.yaml/artifacthub-pkg.yml/values.yaml, regenerate docs, tag the release so CI publishes it). Trigger on requests like "release a new chart version", "cut a release", "bump the chart version", "publish v7.1.0", "prepare the next Zabbix chart release".
Release a new version of the helm-zabbix chart
This skill walks through the maintainer-only release process documented in CONTRIBUTING.md ("For code mainteners only") and CLAUDE.md ("Versioning and release rules"). Its final steps are hard to reverse — pushing a git tag triggers a public GitHub Release via CI — so always confirm the version number and each push/tag/PR action with the user before running it. Do not skip confirmation because a step "seems obvious".
Installing and invoking this skill
This repo keeps skills under .agents/skills/ rather than .claude/skills/ so the same file can be reused by any AI assistant that supports a skills convention, not just Claude Code. To get Claude Code's native /release-chart invocation, symlink this directory in:
- Project-level (this repo only):
bash mkdir -p .claude/skills ln -s ../../.agents/skills/release-chart .claude/skills/release-chart - Personal (available in every repo you work in):
bash mkdir -p ~/.claude/skills ln -s /absolute/path/to/helm-zabbix/.agents/skills/release-chart ~/.claude/skills/release-chart
Once linked, run it with /release-chart, or just describe the task in natural language — e.g. "release a new chart version", "cut a release", "bump the chart version", "prepare the next Zabbix chart release" (these phrases match the description frontmatter above).
No symlink is strictly required to benefit from this file: CLAUDE.md already tells Claude Code to read and follow it whenever a maintainer asks to cut/publish a release, so it works out of the box in this repo. The symlink is only needed for the formal /release-chart slash invocation or to reuse the skill from other repositories.
0. Preconditions
- Confirm with the user (if not already given):
- The new chart
version(and whetherappVersion/zabbixImageTag— the Zabbix version — is also changing). - Whether this is a major bump (the middle digit, e.g.
7.0.12→7.1.0— signals a change that may require users to update theirvalues.yaml) or a minor bump (the last digit, e.g.7.0.12→7.0.13— no API/interface changes).
- The new chart
- Verify all PRs intended for this release are already merged into
main, and localmainis up to date. - Never bump versions or tag directly on
main— always use a release branch.
1. Create the release branch
git checkout main
git pull upstream main
git checkout -b BRANCH_NAME2. Run local tests
cd charts/zabbix
make help # lists all available targets with descriptions
make lintFix any lint errors before continuing.
Show full SKILL.md (356 more words)Show less
3. Bump versions — exact files, nothing else
charts/zabbix/Chart.yaml—version:(chart version) andappVersion:(Zabbix version, only if it's changing).charts/zabbix/artifacthub-pkg.yml— three separate spots, all must matchChart.yaml:version:andappVersion:fields near the top.createdAt:— set to the output ofdate +%Y-%m-%dT%TZ.- The hardcoded
export ZABBIX_CHART_VERSION='...'line inside theinstall:block. This file is plain YAML (not Go-templated), so this string must be edited by hand.
charts/zabbix/values.yaml—zabbixImageTag:if the Zabbix version (appVersion) changed.- If this is a major release: add a new subsection under "Breaking changes of this helm chart" in
charts/zabbix/README.md.gotmpl, explaining what changed and what users need to check in their ownvalues.yaml.
Do not hand-edit charts/zabbix/README.md, and do not touch the export ZABBIX_CHART_VERSION=... line inside README.md.gotmpl — that one is templated from Chart.yaml's version via {{ template "chart.version" . }} and regenerates automatically in the next step. Only artifacthub-pkg.yml's copy of that line is a plain hardcoded string.
4. Regenerate chart docs
cd charts/zabbix
make gen-docsConfirm the resulting diff to charts/zabbix/README.md only touches the version number and (if values.yaml changed) the values table — nothing else should move.
5. Commit, push, and open a PR
Confirm with the user before pushing or opening the PR (visible, shared-state actions):
git add charts/zabbix/Chart.yaml charts/zabbix/artifacthub-pkg.yml charts/zabbix/values.yaml charts/zabbix/README.md charts/zabbix/README.md.gotmpl
git commit -m "Release x.y.z"
git push --set-upstream origin BRANCH_NAMEOpen a PR to main, address review feedback, then merge.
6. Tag and publish — confirm explicitly before this step
After the release PR is merged into main:
git checkout main
git pull upstream main
git tag -a x.y.z -m "New release"
git push upstream --tagsPushing the tag triggers .github/workflows/helm-chart-releaser.yml, which packages the chart and publishes a GitHub Release named zabbix-x.y.z. This is the point of no easy return for this process — do not run it without the user explicitly confirming the exact tag/version first.
7. Finalize release notes
Edit the auto-generated GitHub Release notes to match the style of previous releases (see the repo's Releases page). If this was a major release, make sure the breaking-changes write-up from step 3.4 is reflected in the release notes.
Reference
- Full command-by-command detail:
CONTRIBUTING.md→ "For code mainteners only". - Version semantics and cross-doc consistency notes:
CLAUDE.md→ "Versioning and release rules". - A visual summary (Mermaid flowchart) of this same process: root
README.md→ "Release process".
Keep this file, CONTRIBUTING.md, and CLAUDE.md in sync — if the release steps change, update all three.
© zabbix-community, 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 .agents/skills/release-chart of zabbix-community/helm-zabbix.
Open the folder on GitHubat commit be2dc44
Compare with similar skills
Release Chart 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 Chart this skillzabbix-community/helm-zabbix | 132 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| KubeShark for KubernetesLukasNiessen/kubernetes-skill | 444 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Aks Deployment Skilltimothywarner/chatgptclass | 143 | — | ~916 | Automated safety check: Pass | Custom licence | |
| Securing Helm Chart Deploymentsmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.9k | Automated safety check: Warn | Apache-2.0 | |
| Kubernetes Deploymentseb1n/awesome-ai-agent-skills | 206 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Aks Deployment Skill
timothywarner/chatgptclass
Deploy and operate workloads on Azure Kubernetes Service (AKS) the safe way.
Securing Helm Chart Deployments
mukul975/Anthropic-Cybersecurity-Skills
Secures Helm chart deployments by verifying chart signatures and provenance, rendering and linting templates for misconfiguration, enforcing pod security contexts through values.yaml, moving secrets…
Kubernetes Deployment
seb1n/awesome-ai-agent-skills
Deploy, manage, and scale applications on Kubernetes clusters using manifests, Helm charts, and autoscaling configurations.
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.
KubeSphere Gateway Management
kubesphere/kubesphere
Installs, uninstalls, checks and troubleshoots the KubeSphere Gateway extension built on ingress-nginx, including gateways stuck in bad states and Helm or pod failures.
Related
Works with
Categories
Questions about Release Chart
What does Release Chart do?
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump…. Release Chart is an agent skill from zabbix-community/helm-zabbix.yaml, regenerate docs, tag the release so CI publishes it).
When should I use Release Chart?
Release Chart fits situations like: requests like release a new chart version; bump the chart version; prepare the next Zabbix chart release.
How do I install Release Chart in Claude Code?
Run `npx skills add zabbix-community/helm-zabbix --skill release-chart -a claude-code`. Or copy the skill folder (.agents/skills/release-chart in zabbix-community/helm-zabbix) into .claude/skills/release-chart in your project. Claude Code loads it when a task matches its description.
How do I install Release Chart in Codex?
Run `npx skills add zabbix-community/helm-zabbix --skill release-chart -a codex`. Or copy the skill folder (.agents/skills/release-chart in zabbix-community/helm-zabbix) into .agents/skills/release-chart in your project. Codex loads it when a task matches its description.
Can I use Release Chart 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 zabbix-community/helm-zabbix --skill release-chart -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-chart, .gemini/skills/release-chart, .github/skills/release-chart and .opencode/skills/release-chart in your project.
What does Release Chart need to run?
Going by SKILL.md and its folder, Release Chart needs the command-line tools its instructions call (git and make).
Does Release Chart 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 Release Chart 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 Chart use?
Release Chart 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 Release Chart use?
About 1.5k tokens (SKILL.md is roughly 6.2k 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 Chart?
Skills that share tags, products or a category with Release Chart: KubeShark for Kubernetes (LukasNiessen/kubernetes-skill, 444 stars), Aks Deployment Skill (timothywarner/chatgptclass, 143 stars), Securing Helm Chart Deployments (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Kubernetes Deployment (seb1n/awesome-ai-agent-skills, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Chart?
zabbix-community (a GitHub organization) maintains it in zabbix-community/helm-zabbix, which has 132 GitHub stars. The repository was last updated on July 6, 2026.
Source: zabbix-community/helm-zabbix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.