Agent skill

Installing Cockroachdb With Helm

by cockroachdb in cockroachdb/helm-charts

Guides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources.

Apache-2.0Auto-check passedDevOps & Cloud

Install Installing Cockroachdb With Helm

skills CLI
$ npx skills add cockroachdb/helm-charts --skill installing-cockroachdb-with-helm -a claude-code

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

GitHub CLI
$ gh skill install cockroachdb/helm-charts installing-cockroachdb-with-helm --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/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-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
installing-cockroachdb-with-helm
GitHub stars
105
Token cost
~3.4k tokens
SKILL.md length
883 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources.

  • Works in 4 steps: Preflight the Kubernetes Context → Choose the Install Path → Create a Minimal Values File → …
  • Installing CockroachDB with Helm
  • SKILL.md covers When to Use This Skill, Inputs, Safety Considerations and Execution Discipline, plus 7 more sections
  • Calls kubectl, helm and jq; reaches charts.cockroachdb.com

What it does

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.

When your agent uses it

  • Installing CockroachDB with Helm
  • Choosing between published and local split charts
  • Verifying a new install
  • Helping an agent complete first-time Kubernetes onboarding

Example prompts

  • “Use the installing-cockroachdb-with-helm skill to guide customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm…”
  • “/installing-cockroachdb-with-helm”

Requirements

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

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Preflight the Kubernetes Context
  2. Choose the Install Path
  3. Create a Minimal Values File
  4. Verify the Install

What it can do on your machine

Read from SKILL.md and the folder at commit 26e44ff. 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:

    • kubectl
    • helm
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • charts.cockroachdb.com

    Also links to:

    • cockroachlabs.com
    • helm.sh

    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.

  • Compatibility

    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.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k

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 cockroachdb/helm-charts at commit 26e44ff, republished under its Apache-2.0 licence (© cockroachdb). 883 words, ~3,413 tokens.

Download SKILL.mdSave it as .claude/skills/installing-cockroachdb-with-helm/SKILL.md (or your agent's skills folder).
name
installing-cockroachdb-with-helm
description
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.
compatibility
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.
metadata.author
cockroachdb
metadata.version
1.1

Installing CockroachDB with Helm

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.

When to Use This Skill

  • A customer asks to install CockroachDB on Kubernetes using Helm
  • An agent needs to decide whether to install the published split charts or local split charts
  • A first install needs structured preflight, chart values, and post-install verification
  • A deployment has partially completed and needs the next Helm step

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.

Inputs

Collect these before changing the cluster:

InputExampleWhy It Matters
Kubernetes context and namespaceprod-us-east1, cockroachdbAvoids installing into the wrong cluster or namespace
Install pathPublished split charts or local split chartsDetermines Helm commands and dependency order
Operator release and CockroachDB release namescrdb-operator, crdbResource names and generated services depend on release names
Region and cloud providerus-east1, gcpoperator.cloudRegion must match the region reconciled by this operator
TLS modeself-signer, cert-manager, external certificates, insecure non-prodDetermines chart values and required secrets
Topologysingle-region or multi-regionMulti-region requires complete regions entries and cross-region DNS/networking

Safety Considerations

  • Confirm the target Kubernetes context with the user before running helm install, helm upgrade, or kubectl apply.
  • Do not toggle cockroachdb.tls.enabled on an existing cluster. The chart documents this as unsafe and unrecoverable for a running cluster.
  • Do not configure multiple operators with overlapping watchNamespaces; both can reconcile the same CrdbCluster resources.
  • If the customer cannot create ClusterRoles or ClusterRoleBindings, coordinate split-chart node-reader RBAC with the platform team before installing the CockroachDB chart.
  • Do not use unsupported parent or umbrella chart installs for customer-facing deployment guidance.

Execution Discipline

  • Execute one step at a time and inspect the output before moving on. Preflight output determines whether installation can continue.
  • Run every step in the same shell session. Verification depends on 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.
  • During verification, never infer a CrdbCluster object name from the Helm release or CockroachDB image/version. List CrdbCluster objects and use the exact metadata.name.
  • Before reading CrdbCluster status fields, save the live CRD YAML and derive field paths from the served CRD schema for the object's apiVersion.
  • Do not run helm install, helm upgrade, kubectl apply, or any mutating command unless the user explicitly approves it for the target Kubernetes context and namespace.
  • Stop before installing if cluster-scoped RBAC, node labels, storage class, TLS mode, registry access, or multi-region prerequisites are unclear.
  • In production or restricted environments, involve TSE, the platform team, or the operator team before changing RBAC, webhook, operator, certificate, storage, or network configuration.

Step 1: Preflight the Kubernetes Context

Run read-only checks first:

bash
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)' || true

Interpretation:

  • Kubernetes must be 1.30 or newer for the current v2 chart line.
  • Helm must be v3.
  • Node labels topology.kubernetes.io/region and topology.kubernetes.io/zone should exist before relying on default locality behavior.
  • Missing cluster-scoped RBAC is not automatically fatal, but it changes the install path. Use operator-chart nodeReader values or have a platform team pre-create the required bindings.
Show full SKILL.md (339 more words)Show less

Step 2: Choose the Install Path

Use this path for normal customer installs.

bash
helm repo add cockroachdb-v2 https://charts.cockroachdb.com/v2 --force-update
helm repo update cockroachdb-v2
helm search repo cockroachdb-v2 --devel

Install the operator first:

bash
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.com

Then install CockroachDB:

bash
helm upgrade --install crdb cockroachdb-v2/cockroachdb-chart \
  --namespace cockroachdb \
  --create-namespace \
  --version <cockroachdb-chart-version> \
  -f values.yaml
Local Split Charts

Use this path when working from a checkout of this repository:

bash
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.yaml

Step 3: Create a Minimal Values File

For a single-region secure install using the chart self-signer:

yaml
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: Filesystem

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

Step 4: Verify the Install

Check Kubernetes resources:

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

bash
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.
  • CRDs crdbclusters.crdb.cockroachlabs.com and crdbnodes.crdb.cockroachlabs.com exist.
  • Schema-grounded CrdbCluster status shows reconciled=true and readyNodes equals the regional node count when those fields exist in the served CRD version.
  • Each CrdbNode has a nodeID and Ready/Running conditions.
  • CockroachDB pods are Running and Ready.

For SQL verification, connect with the certificate mode selected by configuring-cockroachdb-helm-tls, then run:

sql
SELECT version();
SHOW REGIONS;
SHOW JOBS;

Outputs

Return a concise install report:

  • Kubernetes context, namespace, and chart path used
  • Operator release, CockroachDB release, and chart versions
  • Values file path or inline values that were applied
  • CRD registration status
  • Schema-grounded CrdbCluster ready/reconciled status and node count
  • SQL verification result or the exact blocker if SQL could not be verified

Troubleshooting Handoff

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

References

© 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

Files

Just SKILL.md in skills/cockroachdb-onboarding-and-migrations/installing-cockroachdb-with-helm of cockroachdb/helm-charts.

Open the folder on GitHubat commit 26e44ff

Compare with similar skills

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.

Installing Cockroachdb With Helm compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Installing Cockroachdb With Helm this skillcockroachdb/helm-charts105—~3.4kAutomated safety check: PassApache-2.0
Sim Helmsimstudioai/sim30k—~2.2kAutomated safety check: PassApache-2.0
Helm Chart ScaffoldingCybereason-Public/owLSM28012 repos~381Automated safety check: PassGPL-2.0
NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress5.1k—~1.4kAutomated safety check: PassApache-2.0
Kubernetes SpecialistJeffallan/claude-skills12k1 repos~2.1kAutomated safety check: PassMIT
KubeShark for KubernetesLukasNiessen/kubernetes-skill444—~1.2kAutomated safety check: PassMIT

Similar skills

  • Sim Helm

    simstudioai/sim

    Install, upgrade, and operate the Sim Helm chart on Kubernetes.

    30k GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Helm Chart Scaffolding

    Cybereason-Public/owLSM

    Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.

    280 GitHub starsUsed in 12 repos~381 tokens
    DevOps & CloudAuto-check passed
  • Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.

    5.1k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Kubernetes Specialist

    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.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    DevOps & CloudAuto-check passed
  • 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.

    444 GitHub stars~1.2k tokensUpdated 24 days ago
    DevOps & CloudAuto-check passed
  • Nim Operator Install

    NVIDIA/k8s-nim-operator

    Official

    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…

    159 GitHub stars~4.7k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

More from 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…

    105 GitHub stars~5.1k tokensUpdated 6 days ago
    Auto-check passed
  • Configuring Cockroachdb Helm Tls

    cockroachdb/helm-charts

    Selects and validates TLS settings for CockroachDB Helm chart deployments, including self-signer, cert-manager, and external certificate modes.

    105 GitHub stars~3.8k tokensUpdated 6 days ago
    Auto-check passed
  • Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration.

    105 GitHub stars~3.6k tokensUpdated 6 days ago
    Auto-check passed
  • 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…

    105 GitHub stars~6.8k tokensUpdated 6 days ago
    Auto-check passed
  • Validates CockroachDB Helm chart values and Kubernetes prerequisites for operator-managed multi-region deployments.

    105 GitHub stars~2k tokensUpdated 6 days ago
    Auto-check passed

Works with

Categories

Questions about Installing Cockroachdb With Helm

What does Installing Cockroachdb With Helm do?

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.

When should I use Installing Cockroachdb With Helm?

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.

How do I install Installing Cockroachdb With Helm in Claude Code?

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.

How do I install Installing Cockroachdb With Helm in Codex?

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.

Can I use Installing Cockroachdb With Helm 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 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.

What does Installing Cockroachdb With Helm need to run?

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

Does Installing Cockroachdb With Helm access the network?

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.

Is Installing Cockroachdb With Helm 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 Installing Cockroachdb With Helm use?

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.

How many tokens does Installing Cockroachdb With Helm use?

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.

What are the alternatives to Installing Cockroachdb With Helm?

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.

Who maintains Installing Cockroachdb With Helm?

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.