Kubernetes Skills
Analysis
The skill is clearly about Kubernetes cluster management, but it guides high-impact cluster changes and kubeconfig retrieval without explicit scope or approval safeguards.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
kubectl_apply(manifest=""" ... kind: Cluster ... infrastructureRef: ... kind: AWSCluster ... """)
The skill instructs use of a raw Kubernetes apply operation to create Cluster API infrastructure resources. That is purpose-aligned, but it is high-impact and not bounded by approval, dry-run, kube-context, namespace, or rollback requirements.
Manage Kubernetes clusters using kubectl-mcp-server's Cluster API tools (11 tools).
The skill depends on an external MCP tool server. This is disclosed and central to the purpose, but the artifact set does not include or verify that external server.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
capi_cluster_kubeconfig_tool(name="my-cluster", namespace="default") # Returns kubeconfig to access the cluster
The skill includes a workflow to retrieve kubeconfig access material for workload clusters, but does not state how that credential-like output should be scoped, displayed, stored, or protected.
