Token导航 LogoToken导航TokenDH.com
运维和基础设施执行命令github未标认证来源可访问clear审计提醒

kubectlkubectl 命令行

Agent Skill

kubectl 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,656

周安装

67

GitHub Stars

3

下载量

520
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:kubectl(kubectl 命令行)
来源仓库:https://github.com/oldwinter/skills
仓库路径:skills/kubectl
安装命令:
npx skills add https://github.com/oldwinter/skills --skill kubectl
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill kubectl

简介

kubectl 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。
  • 通过 npx skills add 命令从指定仓库安装并使用该技能。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • kubectl 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Kubectl Skill

This skill enables comprehensive Kubernetes cluster management using kubectl and related tools.

Environment

Cluster Aliases

Three cluster/namespace combinations are pre-configured:

AliasClusterNamespacePurpose
k1AWS EKS Productionproduction生产环境
k2AWS EKS Productionstaging预发布环境
kK3s (192.168.10.117)simplex本地开发环境

Usage:

k1 get pods          # 查看生产环境 pods
k2 get pods          # 查看预发布环境 pods
k get pods           # 查看本地环境 pods

Additional Tools

  • kubectx - Switch between clusters
  • kubens - Switch between namespaces
  • argocd - GitOps deployments (see separate skill)
  • kargo - Progressive delivery (see separate skill)

Safety Protocol

Dangerous Operations Requiring Confirmation

Before executing any of the following operations, explicitly confirm with the user:

  • Delete operations: delete pod, delete deployment, delete service, delete pvc
  • Scale to zero: scale --replicas=0
  • Production modifications: Any k1 command that modifies resources
  • Drain/cordon nodes: drain, cordon, uncordon
  • Apply/patch: Changes to production resources

Confirmation Format

⚠️ 危险操作确认

环境: [Production/Staging/Local]
操作: [具体操作描述]
资源: [受影响的资源]
影响: [潜在影响说明]

是否继续执行?

Common Operations Reference

Resource Viewing

Pods

# List pods with status
k1 get pods
k1 get pods -o wide                    # Include node and IP info
k1 get pods --show-labels              # Show labels
k1 get pods -l app=simplex-api         # Filter by label

# Pod details
k1 describe pod <pod-name>

# Watch pods in real-time
k1 get pods -w

Deployments

# List deployments
k1 get deployments
k1 get deploy -o wide

# Deployment details
k1 describe deployment <name>

# Rollout status
k1 rollout status deployment/<name>

# Rollout history
k1 rollout history deployment/<name>

Services & Endpoints

# List services
k1 get services
k1 get svc

# Service details with endpoints
k1 describe svc <name>
k1 get endpoints <name>

All Resources

# Get all common resources
k1 get all

# Get specific resource types
k1 get pods,svc,deploy

# Get all resources with labels
k1 get all -l app=simplex-api

Logs & Debugging

Viewing Logs

# Basic logs
k1 logs <pod-name>

# Follow logs (streaming)
k1 logs -f <pod-name>

# Last N lines
k1 logs --tail=100 <pod-name>

# Logs since time
k1 logs --since=1h <pod-name>
k1 logs --since=10m <pod-name>

# Previous container logs (after restart)
k1 logs --previous <pod-name>

# Multi-container pod
k1 logs <pod-name> -c <container-name>

# All containers in pod
k1 logs <pod-name> --all-containers=true

Executing Commands

# Execute command in container
k1 exec <pod-name> -- <command>

# Interactive shell
k1 exec -it <pod-name> -- /bin/sh
k1 exec -it <pod-name> -- /bin/bash

# Specific container in multi-container pod
k1 exec -it <pod-name> -c <container> -- /bin/sh

Debugging

# Pod events and status
k1 describe pod <pod-name>

# Get pod YAML
k1 get pod <pod-name> -o yaml

# Debug with ephemeral container
k1 debug <pod-name> -it --image=busybox

# Check resource usage
k1 top pods
k1 top nodes

Deployment Management

Scaling

# Scale deployment
k1 scale deployment/<name> --replicas=3

# Autoscale
k1 autoscale deployment/<name> --min=2 --max=5 --cpu-percent=80

Rolling Updates

# Update image
k1 set image deployment/<name> <container>=<image>:<tag>

# Rollout status
k1 rollout status deployment/<name>

# Pause/resume rollout
k1 rollout pause deployment/<name>
k1 rollout resume deployment/<name>

# Rollback
k1 rollout undo deployment/<name>
k1 rollout undo deployment/<name> --to-revision=2

Restart

# Restart deployment (rolling restart)
k1 rollout restart deployment/<name>

Configuration Resources

ConfigMaps

# List ConfigMaps
k1 get configmaps
k1 get cm

# View ConfigMap content
k1 describe cm <name>
k1 get cm <name> -o yaml

# Create from file
k1 create configmap <name> --from-file=<path>

# Create from literal
k1 create configmap <name> --from-literal=key=value

Secrets

# List Secrets
k1 get secrets

# View Secret (base64 encoded)
k1 get secret <name> -o yaml

# Decode Secret value
k1 get secret <name> -o jsonpath='{.data.password}' | base64 -d

# Create Secret
k1 create secret generic <name> --from-literal=password=xxx

PersistentVolumeClaims

# List PVCs
k1 get pvc

# PVC details
k1 describe pvc <name>

Network Operations

Port Forwarding

# Forward local port to pod
k1 port-forward pod/<name> 8080:80

# Forward to service
k1 port-forward svc/<name> 8080:80

# Background port-forward
k1 port-forward pod/<name> 8080:80 &

Service Exposure

# Expose deployment as service
k1 expose deployment/<name> --port=80 --target-port=8080

# Get service external IP
k1 get svc <name> -o jsonpath='{.status.loadBalancer.ingress[0].hostname}'

Cluster Management

Nodes

# List nodes
k1 get nodes
k1 get nodes -o wide

# Node details
k1 describe node <name>

# Node resource usage
k1 top nodes

Namespaces

# List namespaces
k1 get namespaces

# Switch namespace (using kubens)
kubens <namespace>

# Create namespace
k1 create namespace <name>

Context Management

# List contexts
kubectx

# Switch context
kubectx <context-name>

# Show current context
kubectl config current-context

Resource Monitoring

# Pod resource usage
k1 top pods
k1 top pods --sort-by=cpu
k1 top pods --sort-by=memory

# Node resource usage
k1 top nodes

# HPA status
k1 get hpa
k1 describe hpa <name>

Output Formatting

For Status Checks

Provide concise summaries:

✅ Pod 状态 (production)
┌──────────────────────────┬─────────┬──────────┬─────────┐
│ Pod                      │ Status  │ Restarts │ Age     │
├──────────────────────────┼─────────┼──────────┼─────────┤
│ simplex-api-xxx-abc      │ Running │ 0        │ 2d      │
│ simplex-api-xxx-def      │ Running │ 0        │ 2d      │
└──────────────────────────┴─────────┴──────────┴─────────┘

For Troubleshooting

When investigating issues, gather:

  1. Pod status: k1 get pod <name>
  2. Pod events: k1 describe pod <name>
  3. Recent logs: k1 logs --tail=50 <name>
  4. Resource usage: k1 top pod <name>

Custom Output Formats

# JSON output
k1 get pods -o json

# YAML output
k1 get pod <name> -o yaml

# Custom columns
k1 get pods -o custom-columns=NAME:.metadata.name,STATUS:.status.phase

# JSONPath
k1 get pods -o jsonpath='{.items[*].metadata.name}'

Troubleshooting Workflows

Pod Not Starting

  1. Check pod status: k1 get pod <name>
  2. Check events: k1 describe pod <name> (look at Events section)
  3. Check logs: k1 logs <name> or k1 logs --previous <name>
  4. Common issues:

- ImagePullBackOff: Check image name and registry credentials - CrashLoopBackOff: Check application logs - Pending: Check resource requests and node capacity

High Resource Usage

  1. Check pod usage: k1 top pods --sort-by=memory
  2. Check node usage: k1 top nodes
  3. Check HPA status: k1 get hpa
  4. Consider scaling: k1 scale deployment/<name> --replicas=N

Service Not Accessible

  1. Check service: k1 get svc <name>
  2. Check endpoints: k1 get endpoints <name>
  3. Check pod labels match service selector
  4. Test from within cluster: k1 exec -it <pod> -- curl <service>:<port>

Integration Notes

For GitOps operations (deployments via git), use the ArgoCD and Kargo skills:

  • ArgoCD: Application sync, rollback, status
  • Kargo: Progressive delivery, freight promotion

For AWS infrastructure operations, use the AWS CLI skill.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenCode

28.15%
按下载量换算146

Claude Code

24.78%
按下载量换算129

Antigravity

16.91%
按下载量换算88

Codex

13.79%
按下载量换算72

Gemini CLI

8.33%
按下载量换算43

Cursor

3.62%
按下载量换算19

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/oldwinter/skills --skill kubectl;npx skills add oldwinter/skills --skill "kubectl" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills