Sim Helm
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
Guides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources.
$ npx skills add cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cockroachdb/helm-charts installing-cockroachdb-with-helm --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/cockroachdb/helm-charts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm .claude/skills/installing-cockroachdb-with-helm && 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 "installing-cockroachdb-with-helm" agent skill from https://github.com/cockroachdb/helm-charts/tree/master/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm into .claude/skills/installing-cockroachdb-with-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "installing-cockroachdb-with-helm", 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/cockroachdb/helm-charts/tree/master/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helmType 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 cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cockroachdb/helm-charts installing-cockroachdb-with-helm --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cockroachdb/helm-charts.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm .agents/skills/installing-cockroachdb-with-helm && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "installing-cockroachdb-with-helm" agent skill from https://github.com/cockroachdb/helm-charts/tree/master/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm into .agents/skills/installing-cockroachdb-with-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "installing-cockroachdb-with-helm", 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 cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cockroachdb/helm-charts installing-cockroachdb-with-helm --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cockroachdb/helm-charts.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm .cursor/skills/installing-cockroachdb-with-helm && 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 "installing-cockroachdb-with-helm" agent skill from https://github.com/cockroachdb/helm-charts/tree/master/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm into .cursor/skills/installing-cockroachdb-with-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "installing-cockroachdb-with-helm", 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/cockroachdb/helm-charts.git --path skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm--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 cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cockroachdb/helm-charts installing-cockroachdb-with-helm --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cockroachdb/helm-charts.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm .gemini/skills/installing-cockroachdb-with-helm && 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 "installing-cockroachdb-with-helm" agent skill from https://github.com/cockroachdb/helm-charts/tree/master/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm into .gemini/skills/installing-cockroachdb-with-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "installing-cockroachdb-with-helm", 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 cockroachdb/helm-charts installing-cockroachdb-with-helmInstalls 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 cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cockroachdb/helm-charts.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm .github/skills/installing-cockroachdb-with-helm && 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 "installing-cockroachdb-with-helm" agent skill from https://github.com/cockroachdb/helm-charts/tree/master/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm into .github/skills/installing-cockroachdb-with-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "installing-cockroachdb-with-helm", 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 cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cockroachdb/helm-charts installing-cockroachdb-with-helm --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cockroachdb/helm-charts.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm .opencode/skills/installing-cockroachdb-with-helm && 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 "installing-cockroachdb-with-helm" agent skill from https://github.com/cockroachdb/helm-charts/tree/master/skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm into .opencode/skills/installing-cockroachdb-with-helm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "installing-cockroachdb-with-helm", 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.
installing-cockroachdb-with-helmGuides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources.
Installing Cockroachdb With Helm is an agent skill from cockroachdb/helm-charts. Guides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources. Use when installing CockroachDB with Helm, choosing between published and local split charts, verifying a new install, or helping an agent complete first-time Kubernetes onboarding.
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: CockroachDB Helm v2 charts with crdb.cockroachlabs.com/v1beta1 CrdbCluster resources. Requires Kubernetes 1.30+, Helm 3+, and cluster permissions to install…
It sits in DevOps & Cloud, covering Container orchestration. It works with Kubernetes and Helm. The repository describes itself as: Helm charts for cockroachdb. The licence is Apache-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 26e44ff. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
kubectlhelmjqFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
charts.cockroachdb.comAlso links to:
cockroachlabs.comhelm.shFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
CockroachDB Helm v2 charts with crdb.cockroachlabs.com/v1beta1 CrdbCluster resources. Requires Kubernetes 1.30+, Helm 3+, and cluster permissions to install CRDs and cluster-scoped RBAC unless pre-provisioned by a platform team.
From compatibility in the SKILL.md frontmatter.
Installing Cockroachdb With Helm loads about 3.4k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 883 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.
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.
The full file from cockroachdb/helm-charts at commit 26e44ff, republished under its Apache-2.0 licence (© cockroachdb). 883 words, ~3,413 tokens.
.claude/skills/installing-cockroachdb-with-helm/SKILL.md (or your agent's skills folder).Guides an agent through a customer-facing CockroachDB install on Kubernetes using the CockroachDB split Helm charts. Prefer the published split charts for customers. Do not use the unsupported parent or umbrella chart path for customer installs.
Related skills: Use configuring-cockroachdb-helm-tls for TLS decisions, validating-cockroachdb-helm-multiregion before multi-region installs, debugging-cockroachdb-operator-migrations for StatefulSet or v1alpha1 migrations, and diagnosing-cockroachdb-helm-deployments when any step fails.
Collect these before changing the cluster:
| Input | Example | Why It Matters |
|---|---|---|
| Kubernetes context and namespace | prod-us-east1, cockroachdb | Avoids installing into the wrong cluster or namespace |
| Install path | Published split charts or local split charts | Determines Helm commands and dependency order |
| Operator release and CockroachDB release names | crdb-operator, crdb | Resource names and generated services depend on release names |
| Region and cloud provider | us-east1, gcp | operator.cloudRegion must match the region reconciled by this operator |
| TLS mode | self-signer, cert-manager, external certificates, insecure non-prod | Determines chart values and required secrets |
| Topology | single-region or multi-region | Multi-region requires complete regions entries and cross-region DNS/networking |
helm install, helm upgrade, or kubectl apply.cockroachdb.tls.enabled on an existing cluster. The chart documents this as unsafe and unrecoverable for a running cluster.watchNamespaces; both can reconcile the same CrdbCluster resources.CRDB_NAMESPACE, CRDB_VERIFY_DIR, and the CRDB_*_PATH exports set alongside the CRD schema helpers; a new shell drops them and downstream jq calls will emit empty or wrong values.CrdbCluster object name from the Helm release or CockroachDB image/version. List CrdbCluster objects and use the exact metadata.name.CrdbCluster status fields, save the live CRD YAML and derive field paths from the served CRD schema for the object's apiVersion.helm install, helm upgrade, kubectl apply, or any mutating command unless the user explicitly approves it for the target Kubernetes context and namespace.Run read-only checks first:
kubectl config current-context
kubectl version --short
helm version --short
kubectl auth can-i create customresourcedefinitions.apiextensions.k8s.io
kubectl auth can-i create clusterroles.rbac.authorization.k8s.io
kubectl auth can-i create clusterrolebindings.rbac.authorization.k8s.io
kubectl get nodes -o wide
kubectl get nodes --show-labels | grep -E 'topology.kubernetes.io/(region|zone)' || trueInterpretation:
topology.kubernetes.io/region and topology.kubernetes.io/zone should exist before relying on default locality behavior.nodeReader values or have a platform team pre-create the required bindings.Use this path for normal customer installs.
helm repo add cockroachdb-v2 https://charts.cockroachdb.com/v2 --force-update
helm repo update cockroachdb-v2
helm search repo cockroachdb-v2 --develInstall the operator first:
helm upgrade --install crdb-operator cockroachdb-v2/cockroachdb-operator-chart \
--namespace cockroach-operator-system \
--create-namespace \
--version <operator-chart-version> \
--set cloudRegion=<current-region>
kubectl -n cockroach-operator-system rollout status deploy/cockroach-operator --timeout=5m
kubectl get crd crdbclusters.crdb.cockroachlabs.com crdbnodes.crdb.cockroachlabs.comThen install CockroachDB:
helm upgrade --install crdb cockroachdb-v2/cockroachdb-chart \
--namespace cockroachdb \
--create-namespace \
--version <cockroachdb-chart-version> \
-f values.yamlUse this path when working from a checkout of this repository:
helm upgrade --install crdb-operator ./cockroachdb-operator/charts/operator \
--namespace cockroach-operator-system \
--create-namespace \
--set cloudRegion=<current-region>
kubectl -n cockroach-operator-system rollout status deploy/cockroach-operator --timeout=5m
helm upgrade --install crdb ./cockroachdb-operator/charts/cockroachdb \
--namespace cockroachdb \
--create-namespace \
-f values.yamlFor a single-region secure install using the chart self-signer:
cockroachdb:
clusterDomain: cluster.local
tls:
enabled: true
selfSigner:
enabled: true
certManager:
enabled: false
externalCertificates:
enabled: false
crdbCluster:
regions:
- code: us-east1
nodes: 3
cloudProvider: gcp
namespace: cockroachdb
dataStore:
volumeClaimTemplate:
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Gi
volumeMode: FilesystemAdjust code, cloudProvider, namespace, storage size, and storage class to the customer environment. The region code should match the Kubernetes node region label and the operator chart cloudRegion.
Check Kubernetes resources:
export OPERATOR_NAMESPACE=cockroach-operator-system
export CRDB_NAMESPACE=cockroachdb
export CRDB_VERIFY_DIR="${CRDB_VERIFY_DIR:-$(mktemp -d)}"
kubectl -n "$OPERATOR_NAMESPACE" get deploy cockroach-operator
kubectl -n "$OPERATOR_NAMESPACE" logs deploy/cockroach-operator --tail=100
kubectl -n "$CRDB_NAMESPACE" get crdbcluster,crdbnode,pods,svc
kubectl get crd crdbclusters.crdb.cockroachlabs.com -o yaml > "$CRDB_VERIFY_DIR/crdbclusters-crd.yaml"
kubectl get crd crdbclusters.crdb.cockroachlabs.com -o json > "$CRDB_VERIFY_DIR/crdbclusters-crd.json"
kubectl -n "$CRDB_NAMESPACE" get crdbcluster -o json | jq -r '
.items[]
| [.metadata.name, .apiVersion, (.metadata.labels["app.kubernetes.io/instance"] // ""), (.metadata.generation | tostring)]
| @tsv
'If no CrdbCluster rows are returned, stop the object-specific verification and report that no live CrdbCluster exists in the namespace. You may collect CrdbNode owner references and labels as teardown evidence, but do not treat those values as a replacement for a discovered CrdbCluster.
If multiple CrdbCluster rows are returned, choose the target by metadata.name; do not use the Helm release or CockroachDB version as a substitute.
export CRDBCLUSTER="<metadata.name-from-crdbcluster-list>"
test -n "$CRDBCLUSTER"
kubectl -n "$CRDB_NAMESPACE" get crdbcluster "$CRDBCLUSTER" -o yaml > "$CRDB_VERIFY_DIR/crdbcluster.yaml"
kubectl -n "$CRDB_NAMESPACE" get crdbcluster "$CRDBCLUSTER" -o json > "$CRDB_VERIFY_DIR/crdbcluster.json"
export CRDBCLUSTER_API_VERSION="$(jq -r '.apiVersion | split("/")[-1]' "$CRDB_VERIFY_DIR/crdbcluster.json")"
export CRDBCLUSTER_SCHEMA_JSON="$CRDB_VERIFY_DIR/crdbcluster-schema.json"
jq -e --arg version "$CRDBCLUSTER_API_VERSION" '
.spec.versions[] | select(.name == $version) | .schema.openAPIV3Schema
' "$CRDB_VERIFY_DIR/crdbclusters-crd.json" > "$CRDBCLUSTER_SCHEMA_JSON"
crdb_schema_has() {
jq -e --arg path "$1" '
def has_schema_path($schema; $parts):
if ($parts | length) == 0 then true
elif (($schema.properties? // {}) | has($parts[0])) then
has_schema_path($schema.properties[$parts[0]]; $parts[1:])
else false
end;
has_schema_path(.; $path | split("."))
' "$CRDBCLUSTER_SCHEMA_JSON" >/dev/null
}
crdb_first_schema_path() {
for schema_path in "$@"; do
if crdb_schema_has "$schema_path"; then
printf '%s\n' "$schema_path"
return 0
fi
done
printf '\n'
}
export CRDB_READY_NODES_PATH="$(crdb_first_schema_path status.readyNodes)"
export CRDB_RECONCILED_PATH="$(crdb_first_schema_path status.reconciled)"
export CRDB_STATUS_VERSION_PATH="$(crdb_first_schema_path status.version)"
jq \
--arg readyNodesPath "$CRDB_READY_NODES_PATH" \
--arg reconciledPath "$CRDB_RECONCILED_PATH" \
--arg statusVersionPath "$CRDB_STATUS_VERSION_PATH" \
'
def value($path): if $path == "" then null else getpath($path | split(".")) end;
{
apiVersion,
name: .metadata.name,
schemaPaths: {
readyNodes: $readyNodesPath,
reconciled: $reconciledPath,
statusVersion: $statusVersionPath
},
readyNodes: value($readyNodesPath),
reconciled: value($reconciledPath),
statusVersion: value($statusVersionPath)
}
' "$CRDB_VERIFY_DIR/crdbcluster.json"
kubectl -n "$CRDB_NAMESPACE" get crdbnodes -o json | jq '.items[] | {
name: .metadata.name,
nodeID: .status.nodeID,
decommission: .status.decommission,
conditions: .status.conditions,
topology: .status.topologyValues
}'Expected state:
cockroach-operator Deployment is available.crdbclusters.crdb.cockroachlabs.com and crdbnodes.crdb.cockroachlabs.com exist.CrdbCluster status shows reconciled=true and readyNodes equals the regional node count when those fields exist in the served CRD version.CrdbNode has a nodeID and Ready/Running conditions.For SQL verification, connect with the certificate mode selected by configuring-cockroachdb-helm-tls, then run:
SELECT version();
SHOW REGIONS;
SHOW JOBS;Return a concise install report:
CrdbCluster ready/reconciled status and node countIf any command fails, stop the install flow and use diagnosing-cockroachdb-helm-deployments. Preserve the exact command, stderr, namespace, release names, and values file path. If the failure remains unresolved or the operator appears stuck, gather the operator escalation packet before restarting or changing operator state.
© cockroachdb, 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
Just SKILL.md in skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm of cockroachdb/helm-charts.
Open the folder on GitHubat commit 26e44ff
Installing Cockroachdb With Helm 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 |
|---|---|---|---|---|---|---|
| Installing Cockroachdb With Helm this skillcockroachdb/helm-charts | 105 | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Sim Helmsimstudioai/sim | 30k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Helm Chart ScaffoldingCybereason-Public/owLSM | 280 | 12 repos | ~381 | Automated safety check: Pass | GPL-2.0 | |
| NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress | 5.1k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Kubernetes SpecialistJeffallan/claude-skills | 12k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| KubeShark for KubernetesLukasNiessen/kubernetes-skill | 444 | — | ~1.2k | Automated safety check: Pass | MIT |
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
Cybereason-Public/owLSM
Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.
nginx/kubernetes-ingress
Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.
Jeffallan/claude-skills
Creates and checks Kubernetes manifests, Helm charts, RBAC and network policies, and helps debug pod problems, with kubectl checks and rollback steps.
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.
NVIDIA/k8s-nim-operator
Install NVIDIA NIM Operator on Kubernetes with prerequisite checks, optional NVIDIA GPU Operator dependency installation, public or local Helm chart selection, optional Dynamo support, and optional…
cockroachdb/helm-charts
Collects a complete CockroachDB Operator escalation packet for TSC/TSE or operator-team handoff, including Helm state, Kubernetes resources, logs, operation-specific evidence, pprof goroutine dumps…
cockroachdb/helm-charts
Selects and validates TLS settings for CockroachDB Helm chart deployments, including self-signer, cert-manager, and external certificate modes.
cockroachdb/helm-charts
Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration.
cockroachdb/helm-charts
Diagnoses failed or unhealthy CockroachDB Helm chart deployments by checking Helm release state, operator health, CrdbCluster and CrdbNode status, pod readiness, RBAC, webhooks, TLS, upgrades…
cockroachdb/helm-charts
Validates CockroachDB Helm chart values and Kubernetes prerequisites for operator-managed multi-region deployments.
Works with
Categories
Guides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources. Installing Cockroachdb With Helm is an agent skill from cockroachdb/helm-charts. Guides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources.
Installing Cockroachdb With Helm fits situations like: installing CockroachDB with Helm; choosing between published and local split charts; verifying a new install; helping an agent complete first-time Kubernetes onboarding.
Run `npx skills add cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a claude-code`. Or copy the skill folder (skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm in cockroachdb/helm-charts) into .claude/skills/installing-cockroachdb-with-helm in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a codex`. Or copy the skill folder (skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm in cockroachdb/helm-charts) into .agents/skills/installing-cockroachdb-with-helm in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/installing-cockroachdb-with-helm, .gemini/skills/installing-cockroachdb-with-helm, .github/skills/installing-cockroachdb-with-helm and .opencode/skills/installing-cockroachdb-with-helm in your project.
Going by SKILL.md and its folder, Installing Cockroachdb With Helm needs the command-line tools its instructions call (kubectl, helm and jq). Compatibility (from SKILL.md): CockroachDB Helm v2 charts with crdb.cockroachlabs.com/v1beta1 CrdbCluster resources. Requires Kubernetes 1.30+, Helm 3+, and cluster permissions to install CRDs and cluster-scoped RBAC unless pre-provisioned by a platform team..
SKILL.md names 3 domains. In commands or code: charts.cockroachdb.com; the agent is likely to contact it when it follows the instructions. As links in the text: cockroachlabs.com and helm.sh. This is read from the text; nothing was executed.
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.
Installing Cockroachdb With Helm 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.
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Installing Cockroachdb With Helm: Sim Helm (simstudioai/sim, 30k stars), Helm Chart Scaffolding (Cybereason-Public/owLSM, 280 stars), NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars) and Kubernetes Specialist (Jeffallan/claude-skills, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cockroachdb (a GitHub organization) maintains it in cockroachdb/helm-charts, which has 105 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 1, 2026.
Source: cockroachdb/helm-charts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.