How do I install the Kubectl Onprem skill?

Run npx skillmds@latest add arvo-ai/kubectl-onprem in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubectl Onprem safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubectl Onprem?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubectl Onprem free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubectl Onprem?

Arvo-AI (@arvo-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubectl Onprem by arvo-ai — Agent Skill

Name: Kubectl Onprem
Rating: 4.5 (4 reviews)
Author: Arvo-AI

File contents

On-Prem Kubernetes (kubectl) Integration

Overview

On-prem Kubernetes cluster integration for running kubectl commands on connected clusters. Commands are either relayed through the Aurora agent installed on the cluster, or executed directly using uploaded kubeconfig credentials.

IMPORTANT: Always call get_connected_clusters first to discover available clusters and their cluster_id before running any kubectl commands.

Note: For cloud-managed clusters (GCP GKE, AWS EKS, Azure AKS), use terminal_exec with kubectl commands instead.

Instructions

Tool: get_connected_clusters

Discover available on-prem clusters. Call this before using on_prem_kubectl.

Usage: get_connected_clusters()

Returns cluster names, IDs, connection status, and metadata.

Tool: on_prem_kubectl

Run kubectl commands on connected on-prem Kubernetes clusters.

Usage: on_prem_kubectl(cluster_id='CLUSTER_ID', command='get pods -n default')

Specify the cluster using the cluster_id returned by get_connected_clusters.

RCA Investigation Flow

Discover available clusters: get_connected_clusters()
List pods and check status: on_prem_kubectl(cluster_id='ID', command='get pods -n NAMESPACE')
Check pod logs for errors: on_prem_kubectl(cluster_id='ID', command='logs PODNAME -n NAMESPACE --tail=100')
Describe failing pods for events: on_prem_kubectl(cluster_id='ID', command='describe pod PODNAME -n NAMESPACE')
Check recent events in the namespace: on_prem_kubectl(cluster_id='ID', command='get events -n NAMESPACE --sort-by=.lastTimestamp')
Check node status: on_prem_kubectl(cluster_id='ID', command='get nodes -o wide')
Check resource usage: on_prem_kubectl(cluster_id='ID', command='top pods -n NAMESPACE')

Important Rules

Always specify cluster_id to target the correct cluster.
For cloud-managed clusters (GCP GKE, AWS EKS, Azure AKS), use terminal_exec with kubectl commands.
This tool is for on-prem/self-managed clusters connected via the Aurora kubectl agent or uploaded kubeconfigs.
Check pod status and events before diving into logs.

---name: kubectl-onpremdescription: On-prem Kubernetes cluster integration for running kubectl commands via Aurora agent relay or uploaded kubeconfig---# On-Prem Kubernetes (kubectl) Integration## OverviewOn-prem Kubernetes cluster integration for running kubectl commands on connected clusters. Commands are either relayed through the Aurora agent installed on the cluster, or executed directly using uploaded kubeconfig credentials.**IMPORTANT:** Always call `get_connected_clusters` first to discover available clusters and their `cluster_id` before running any kubectl commands.**Note:** For cloud-managed clusters (GCP GKE, AWS EKS, Azure AKS), use `terminal_exec` with kubectl commands instead.## Instructions### Tool: get_connected_clustersDiscover available on-prem clusters. Call this before using `on_prem_kubectl`.**Usage:**`get_connected_clusters()`Returns cluster names, IDs, connection status, and metadata.### Tool: on_prem_kubectlRun kubectl commands on connected on-prem Kubernetes clusters.**Usage:**`on_prem_kubectl(cluster_id='CLUSTER_ID', command='get pods -n default')`Specify the cluster using the `cluster_id` returned by `get_connected_clusters`.### RCA Investigation Flow1. Discover available clusters: `get_connected_clusters()`2. List pods and check status: `on_prem_kubectl(cluster_id='ID', command='get pods -n NAMESPACE')`3. Check pod logs for errors: `on_prem_kubectl(cluster_id='ID', command='logs PODNAME -n NAMESPACE --tail=100')`4. Describe failing pods for events: `on_prem_kubectl(cluster_id='ID', command='describe pod PODNAME -n NAMESPACE')`5. Check recent events in the namespace: `on_prem_kubectl(cluster_id='ID', command='get events -n NAMESPACE --sort-by=.lastTimestamp')`6. Check node status: `on_prem_kubectl(cluster_id='ID', command='get nodes -o wide')`7. Check resource usage: `on_prem_kubectl(cluster_id='ID', command='top pods -n NAMESPACE')`### Important Rules- Always specify `cluster_id` to target the correct cluster.- For cloud-managed clusters (GCP GKE, AWS EKS, Azure AKS), use `terminal_exec` with kubectl commands.- This tool is for on-prem/self-managed clusters connected via the Aurora kubectl agent or uploaded kubeconfigs.- Check pod status and events before diving into logs.

Frequently asked questions

Kubectl Onprem