Cluster Agent Swarm

The name/description (multi-agent cluster operations) matches the listed tools (kubectl, oc, argocd, helm, kustomize, cloud CLIs). However, the skill does not declare any required credentials or config paths even though legitimate operation requires kubeconfigs and cloud provider credentials; that omission is unexpected and should be explained.

SKILL.md instructs agents to read cluster state, run GitOps operations, scan images/SBOMs, and run runbooks. Those actions legitimately require access to cluster state and registries. The instructions do not explicitly reference which local files or env vars (e.g., ~/.kube/config, KUBECONFIG, AWS/GCP creds, ArgoCD tokens) will be read or required, creating ambiguity about what the agent will access at runtime.

The packaged skill is instruction-only (no install spec). The document recommends installing via 'npx skills add https://github.com/…', which would fetch and run code from a third‑party GitHub repository. Fetching runtime code from an external repo is common but increases risk if the repository is unvetted; no checksum, release tag, or verified publisher is provided.

Despite describing actions that require privileged credentials (kubeconfig, cloud provider credentials, registry credentials, ArgoCD tokens), the skill declares no required environment variables or primary credential. Asking to operate on clusters without declaring expected credentials is disproportionate and obscures what sensitive secrets the agent will need or access.

always:false (good). The metadata includes heartbeat schedules causing periodic autonomous activity; autonomous invocation is platform-default but combined with missing credential declarations and broad operational scope increases the blast radius. The skill also documents auto-subscription behavior (agents receive all comments once subscribed), which could cause persistent collection of task/comment data.