Chin K

Kubernetes Agent Swarm

AI Agentv2.1.0
By Chin KUpdated 2026-05-1811 versions · latest released 2026-04-15kubernetes@clawhub_kcns008/kubernetes
Multi-Agent Collaboration#Kubernetes#Multi Agent#Observability#Developer

According to AlphaMoat, as of 2026-10, Kubernetes Agent Swarm has 30,662 downloads and 7 stars — ranked by downloads #897 among 10,914 AI skills in this ranking, and #139 of 1,632 in AI Agent.

The list defaults to total downloads and can also be sorted by stars; detail-page rankings use total downloads.

Downloads
30.7K
Stars
7
Overall download rank
#897
Top 9% overall · Top 9% in AI Agent
PlatformDownloadsStarsComments
ClawHub ↗9.7K6-
SkillHub ↗30.7K7—

Platforms count differently and update at different times.

What this skill does

The agents: Orchestrator (Jarvis — task routing and coordination), Cluster Ops (Atlas — cluster lifecycle and nodes), GitOps (Flow — ArgoCD/Helm/Kustomize deploys), Security (Shield — RBAC/policies/secrets/scanning), Observability (Pulse — metrics/logs/alerts), Artifacts (Cache — registries/SBOM/CVEs) and Developer Experience (Desk — namespaces and support). This is an instruction-only skill: it bundles no executable scripts; agents follow markdown instructions using the host's kubectl (required), oc/helm/jq (optional) and require KUBECONFIG. Heartbeats run at 5/10/15-minute cadences; agents collaborate via @mentions with an escalation path. Boundaries: agents can read cluster state, deploy via GitOps and triage incidents; they cannot delete production resources, modify cluster-wide policies, change secrets directly, perform irreversible upgrades, or approve production deployments (humans approve).

Profile published 2026-10-27

What you can do with it

  • Coordinate platform operations with seven role-specialized agents
  • Read cluster state, triage incidents and prepare GitOps deploys
  • Keep humans in the loop via @mentions and escalation paths

When to use it

  • When a platform team needs coordinated K8s/OpenShift operations
  • When GitOps, security and observability work must be split by role
  • When critical actions must retain human approval

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

@Pulse check whether this CPU spike is from the deploy or external traffic.
@Atlas review the node status of the staging cluster.
Summarize the current cluster health checks.

Monthly Trend

Downloads30.7K
16.1K23.9K31.7K2026-09 · Downloads 17.2K2026-10 · Downloads 30.7K26-0926-10
Stars7
6782026-09 · Stars 72026-10 · Stars 726-0926-10
MonthDownloadsMoMStars
2026-1030.7K—7
2026-0917.2K—7

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

5.8 KB · ClawHub v2.1.0
---
name: kubernetes
description: >
  Kubernetes & OpenShift Platform Agent Swarm — A coordinated multi-agent system for
  cluster operations. Includes Orchestrator (Jarvis), Cluster Ops (Atlas), GitOps (Flow),
  Security (Shield), Observability (Pulse), Artifacts (Cache), and Developer Experience (Desk).
  Pure instruction-based skill — no executable scripts.
metadata:
  author: kcns008
  version: 2.1.0
Show all (181 lines)
  agent_name: Swarm
  agent_role: Platform Agent Swarm (All Agents)
  session_key: "agent:platform:swarm"
  heartbeat: "*/5 * * * *"
  platforms:
    - openshift
    - kubernetes
    - eks
    - aks
    - gke
    - rosa
    - aro
  install_type: "instruction-only"
  always: false
  model_invocation: false
  requires:
    env:
      - KUBECONFIG
    binaries:
      - kubectl
  optional_binaries:
    - oc
    - helm
    - jq
  optional_env:
    - AWS_ACCESS_KEY_ID
    - AWS_SECRET_ACCESS_KEY
    - AZURE_CLIENT_ID
    - AZURE_CLIENT_SECRET
    - AZURE_TENANT_ID
    - GOOGLE_APPLICATION_CREDENTIALS
  credentials:
    - kubeconfig: "KUBECONFIG path or ~/.kube/config for cluster access"
    - cloud: "Optional cloud provider credentials for managed clusters (AWS/Azure/GCP)"
    - registry: "Optional container registry credentials for image operations"
---

# Kubernetes Agent Swarm — Platform Operations

A multi-agent system for Kubernetes and OpenShift platform operations. Seven specialized agents work together as a coordinated swarm.

## Runtime Requirements

| Requirement | Required | Description |
|-------------|----------|-------------|
| `kubectl` | ✅ Yes | Kubernetes CLI — must be in PATH |
| `oc` | Optional | OpenShift CLI — needed for OCP/ROSA/ARO |
| `helm` | Optional | For GitOps agent Helm operations |
| `jq` | Optional | For JSON output parsing |
| `KUBECONFIG` | ✅ Yes | Cluster access via env var or `~/.kube/config` |

Optional cloud CLIs (`aws`, `az`, `gcloud`, `rosa`) — only needed for managed cluster operations.

## Installation

```bash
clawhub install kubernetes
```

Or install individual agents:
```bash
clawhub install orchestrator
clawhub install cluster-ops
clawhub install gitops
clawhub install security
clawhub install observability
clawhub install artifacts
clawhub install developer-experience
```

## The Swarm — Agent Roster

| Agent | Code Name | Domain |
|-------|-----------|--------|
| Orchestrator | Jarvis | Task routing, coordination, standups |
| Cluster Ops | Atlas | Cluster lifecycle, nodes, upgrades |
| GitOps | Flow | ArgoCD, Helm, Kustomize, deploys |
| Security | Shield | RBAC, policies, secrets, scanning |
| Observability | Pulse | Metrics, logs, alerts, incidents |
| Artifacts | Cache | Registries, SBOM, promotion, CVEs |
| Developer Experience | Desk | Namespaces, onboarding, support |

## How It Works

This is an **instruction-only** skill. Agents receive markdown instructions describing what commands to run and how to interpret output. No executable scripts are included — the agent translates instructions into actions using the host's installed CLI tools.

### Session Setup

Before using the swarm, establish cluster context:

```bash
# Verify access
kubectl cluster-info
kubectl get nodes

# For OpenShift
oc status
```

### Agent Communication

Agents communicate via @mentions in shared task comments:
```
@Shield Please review the RBAC for payment-service v3.2 before I sync.
@Pulse Is the CPU spike related to the deployment or external traffic?
@Atlas The staging cluster needs 2 more worker nodes.
```

### Escalation Path
1. Agent detects issue
2. Agent attempts resolution within guardrails
3. If blocked → @mention another agent or escalate to human
4. P1 incidents → all relevant agents auto-notified

## Heartbeat Schedule

```
*/5  * * * *  Atlas, Pulse, Shield     (fast response: incidents, alerts, CVEs)
*/10 * * * *  Flow, Cache              (scheduled: deploys, promotions)
*/15 * * * *  Desk, Orchestrator       (batch: onboarding, standups)
```

## Agent Capabilities

### What Agents CAN Do
- Read cluster state (`kubectl get`, `kubectl describe`, `oc get`)
- Deploy via GitOps (`argocd app sync`, Flux reconciliation)
- Create documentation and reports
- Investigate and triage incidents
- Provision standard resources (namespaces, quotas, RBAC)
- Run health checks and audits
- Query metrics and logs

### What Agents CANNOT Do (Human-in-the-Loop Required)
- Delete production resources
- Modify cluster-wide policies
- Make direct changes to secrets without rotation workflow
- Perform irreversible cluster upgrades
- Approve production deployments (can prepare, human approves)

## Key Principles

- **Roles over genericism** — Each agent has a defined domain
- **Files over mental notes** — Only files persist between sessions
- **Human-in-the-loop** — Critical actions require approval
- **Guardrails over freedom** — Define what agents can and cannot do
- **Audit everything** — Every action logged

## File Structure

```
kubernetes/
├── SKILL.md                    # This file — combined swarm
├── AGENTS.md                   # Swarm configuration and protocols
├── skills/
│   ├── orchestrator/SKILL.md   # Jarvis — task routing
│   ├── cluster-ops/SKILL.md    # Atlas — cluster operations
│   ├── gitops/SKILL.md         # Flow — GitOps
│   ├── security/SKILL.md       # Shield — security
│   ├── observability/SKILL.md  # Pulse — monitoring
│   ├── artifacts/SKILL.md      # Cache — artifacts
│   └── developer-experience/SKILL.md  # Desk — DevEx
├── memory/MEMORY.md            # Long-term agent memory
├── working/WORKING.md          # Session progress
└── logs/LOGS.md                # Action audit trail
```

## Detailed Agent Documentation

See individual SKILL.md files for each agent's full capabilities, personality, and workflow instructions.

Popular in AI Agent

self-improving agentAI Agent

Records learnings, errors and corrections as Markdown files for later reuse and promotion into workspace memory.

↓ 1.6M★ 4.5Kpskoett
技能发现·Find SkillsAI Agent

Finds skills in local and remote catalogs from a plain-language request and recommends what to install.

↓ 1.6M★ 1.8K桂皮
Agent BrowserAI Agent

A browser-automation command line skill for AI agents.

↓ 1.2M★ 1.0KNicolas Kleiber
Self-Improving + Proactive AgentAI Agent

Turns corrections and self-review into tiered memory and promotes or archives it by use.

↓ 696.4K★ 1.6KIván
Proactive AgentAI Agent

A workspace setup guide for planning proactive follow-up, working memory and review routines for an AI agent.

↓ 579.3K★ 916halthelobster
Skill CreatorAI Agent

A guide to creating and updating effective Claude skills.

↓ 477.3K★ 485chindden
Skill VetterAI Agent

Reviews a third-party skill's source, permissions, and danger patterns against a checklist before it is installed.

↓ 445.2K★ 1.3Kspclaudehome
唐朝诗仙李白 · Ai Agent SkillAI Agent

以李白(701—762,字太白,号青莲居士,世称诗仙)的诗学观、意象系统与口吻,进行唐诗赏析、文学评论、考据问答与拟体创作。触发词:李白、李太白、太白、青莲居士、诗仙、谪仙人、将进酒、静夜思、蜀道难、唐诗、盛唐诗人、浪漫主义诗人、拟李白风格、以李白视角、李白会怎么写、用李白口吻。能力:诗词鉴赏与风格DNA解析、诗学观与文学谱系评述、诗句出处考据与真伪边界标注、以李白口吻答问、拟李白体旧体诗(必显式标注非原作)。适用边界:仅用于唐代文学与古典诗歌相关话题,非此类话题不触发;本 skill 为文学普及与研究辅助,不代表李白本人立场,所拟之作均非李白原作;涉及生平佚事、篇目归属等内容不构成学术定论,皆标存疑或待考。

↓ 435.8K★ 4user_ff4d9420

Data as of 2026-10. Downloads and stars are aggregated monthly from public skill registries (ClawHub, SkillHub). See data methodology.