agentleFS
vibe-cokitvibe-cokit/claude-code/skills/kubernetes/SKILL.md

kubernetes

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Operate a cluster with kubectl and helm. Triggers on: inspecting or restarting pods/deployments/services, reading pod logs, scaling or rolling out a workload, managing Helm releases, diagnosing CrashLoopBackOff or pending pods, checking RBAC.

  • Reads credentials

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gitops, documentation-site and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kcns008Skill

    gitops

    GitOps Agent (Flow) — manages ArgoCD applications, Helm charts, Kustomize overlays, deployment strategies (canary, blue-green, rolling), multi-cluster GitOps, and drift detection for Kubernetes and OpenShift clusters.

    Also in 4 projects that use this

  • KMaruthi2002Skill

    documentation-site

    Plan, build and maintain a documentation website for a product, API, library, platform or internal system: information architecture (tutorials, how-to guides, reference, explanation), choosing a static site generator or hosted docs platform, navigation and search, versioning for multiple releases, generated API reference, code samples that are tested and actually run, docs-as-code workflow with review, previews, link checking and CI, plus accessibility, internationalisation and analytics. Use when someone asks to create a docs site, developer portal, knowledge base, handbook site, migrate docs to a new generator, add versioning or search to docs, or fix docs that users cannot navigate or that have drifted from the product.

    Also in 3 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 3 projects that use this

  • ihiteshguptaSkill

    terraform

    Expert in Infrastructure as Code with Terraform. Use for creating, managing, and versioning infrastructure across cloud providers.

    Also in 5 projects that use this

  • ddehartSkill

    process

    Process work sessions into the claude-code-plugins knowledge graph — preserves the session transcript, writes or links its chronicle entry as the session's synthesis, turns the transcript into observations, updates the patterns and decisions they support, folds in named plugins and skills, and proposes promotions to the personal commons. Also resolves-and-preserves an on-demand Claude Code docs URL when one comes up. Use when the user says "process this session", "run /process", names a session transcript or UUID, names a chronicle entry whose session should be processed, asks what's in the processing queue, or points at a Claude Code release-notes / docs page to capture.

    Also in 3 projects that use this

  • third-order-labsSkill

    project-scaffolding

    Templates, directory conventions, and document structure for long-form fiction projects. Contains the full template library — documents are created as the project needs them, not all at once.

    Also in 3 projects that use this

The file

Files
SKILL.md

Kubernetes Cluster Management

Overview

Script-based Kubernetes interaction via kubectl and helm. Execute commands, parse JSON output, manage resources, debug issues — zero external dependencies.

Quick Start

# List pods
node scripts/kubernetes.js get pods -n default

# Get pod logs
node scripts/kubernetes.js logs my-pod --tail 100

# Scale deployment
node scripts/kubernetes.js scale deployment web --replicas=3

# Helm list
node scripts/kubernetes.js helm list -A

# Troubleshoot pod
node scripts/kubernetes.js troubleshoot pod crash-pod -n default

Commands

CategoryCommands
Resourcesget, describe, apply, create, delete, patch
Podslogs, exec, cp, port-forward
Deploymentsscale, rollout status|history|undo|restart
Clustercluster-info, get-contexts, use-context, get-namespaces
Helmhelm list|install|upgrade|uninstall|show-values|template|status|history
Debugevents, top, troubleshoot, auth can-i

Global Flags

FlagPurpose
-n, --namespaceTarget namespace
--contextKubernetes context
--dry-runValidate without applying
--show-secretsShow secret values unmasked
-AAll namespaces
-lLabel selector

Safety

  • Secret values masked by default (***MASKED***)
  • Input sanitization prevents command injection
  • Dry-run mode for validation

References

  • architecture.md — Module design and data flow
  • commands-reference.md — Full command reference
  • troubleshooting-guide.md — K8s debugging patterns

Environment

  • KUBECONFIG — Kubeconfig path (default: ~/.kube/config)
  • KUBE_CONTEXT — Default context
  • KUBE_NAMESPACE — Default namespace

Scripts load .env: process.env > kubernetes/.env > skills/.env > .claude/.env

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.