Run any Skill in Manus with one click

Get Started

kube

Stars2

Forks0

UpdatedMarch 28, 2026 at 06:54

Analyze Kubernetes cluster state via SSH. Usage: /kube <key> <user> <host_ip> <namespace>

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

incognia

incognia/rules

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	kube
description	Analyze Kubernetes cluster state via SSH. Usage: /kube <key> <user> <host_ip> <namespace>

Kubernetes cluster analysis

Arguments

Key: $0 (SSH key name in ~/.ssh/: incognia, faraday, kone, cad)
User: $1 (SSH user, e.g. ubuntu, root, admin)
Host IP: $2 (server IP address)
Namespace: $3 (Kubernetes namespace to analyze)

Instructions

Read the full CoT: Load and follow ~/rules/cot/kube.md from line 1 to end
Read the rules: Load ~/rules/rulesets/KUBE.md for conventions and commands
Connect via SSH: ssh -i ~/.ssh/$0 $1@$2 — check ~/.ssh/config for custom port
Cluster health:
- kubectl get nodes -o wide
- kubectl top nodes (skip if Metrics API unavailable)
Namespace analysis ($3):
- kubectl get pods -n $3 -o wide
- kubectl get svc -n $3
- kubectl get vs -n $3
- kubectl get events -n $3 --sort-by='.lastTimestamp' | tail -20
Istio status:
- kubectl get gateway -n $3
- istioctl analyze -n $3 (if available)
- istioctl proxy-status
ArgoCD:
- kubectl get app -n argocd | grep $3
Manifests on disk:
- ls /home/$1/kubernetes-$3/services/overlays/dev/
- ls /home/$1/kubernetes-$3/services/base/
Health checks:
- Get Gateway IP: kubectl get svc -n istio-system istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}'
- Test endpoints via Gateway
Observability:
- Kiali: port 20001
- Prometheus: port 9090
- Grafana: port 3000
Report: Summarize findings — nodes, problematic pods, services, VirtualServices, ArgoCD sync, recent events, observability

Examples

/kube kone ubuntu 192.168.10.70 stab — infra server, stab namespace
/kube kone ubuntu 30.30.40.90 sinaloa-qa — client server via kone
/kube cad admin 10.0.1.50 produccion — client server via cad

References

Detailed CoT: ~/rules/cot/kube.md
Rules: ~/rules/rulesets/KUBE.md

More from this repository

same repository

bmail

incognia/rules

Compose structured business-email drafts in English from curated templates and phrase banks from Business Email (book). Use this whenever the user asks for enquiry, informing, request, complaint, apology, order-status, or meeting-style business emails.

2026-06-222

aws-naming

incognia/rules

Normalize filenames for AWS S3 and CloudFront: lowercase, safe characters, extension normalization (.jpeg → .jpg), and .tsv audit log. Usage: /aws-naming <directory_or_file>

2026-06-012

styling

incognia/rules

Apply Kabat One Markdown styling to a file by platform. Usage: /styling <hedgedoc|gitlab|github> [mit|gpl] <file>

2026-05-252

changelogger

incognia/rules

Maintain CHANGELOG.md with correct CST dates, reverse chronological order, and Spanish Mexican language. Use this skill when updating the changelog.

2026-05-152

commit

incognia/rules

Full commit workflow with mandatory CHANGELOG validation, SSH validation, and conventional commits in English. Use this skill before making any git commit.

2026-05-152

git-init

incognia/rules

Initialize a git repo with SSH, identity and remote configured. Usage: /git-init <personal|laboral> <key_name> <remote_url> <branch>

2026-05-112

name	kube
description	Analyze Kubernetes cluster state via SSH. Usage: /kube <key> <user> <host_ip> <namespace>

Kubernetes cluster analysis

Arguments

Key: $0 (SSH key name in ~/.ssh/: incognia, faraday, kone, cad)
User: $1 (SSH user, e.g. ubuntu, root, admin)
Host IP: $2 (server IP address)
Namespace: $3 (Kubernetes namespace to analyze)

Instructions

Read the full CoT: Load and follow ~/rules/cot/kube.md from line 1 to end
Read the rules: Load ~/rules/rulesets/KUBE.md for conventions and commands
Connect via SSH: ssh -i ~/.ssh/$0 $1@$2 — check ~/.ssh/config for custom port
Cluster health:
- kubectl get nodes -o wide
- kubectl top nodes (skip if Metrics API unavailable)
Namespace analysis ($3):
- kubectl get pods -n $3 -o wide
- kubectl get svc -n $3
- kubectl get vs -n $3
- kubectl get events -n $3 --sort-by='.lastTimestamp' | tail -20
Istio status:
- kubectl get gateway -n $3
- istioctl analyze -n $3 (if available)
- istioctl proxy-status
ArgoCD:
- kubectl get app -n argocd | grep $3
Manifests on disk:
- ls /home/$1/kubernetes-$3/services/overlays/dev/
- ls /home/$1/kubernetes-$3/services/base/
Health checks:
- Get Gateway IP: kubectl get svc -n istio-system istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}'
- Test endpoints via Gateway
Observability:
- Kiali: port 20001
- Prometheus: port 9090
- Grafana: port 3000
Report: Summarize findings — nodes, problematic pods, services, VirtualServices, ArgoCD sync, recent events, observability

Examples

/kube kone ubuntu 192.168.10.70 stab — infra server, stab namespace
/kube kone ubuntu 30.30.40.90 sinaloa-qa — client server via kone
/kube cad admin 10.0.1.50 produccion — client server via cad

References

Detailed CoT: ~/rules/cot/kube.md
Rules: ~/rules/rulesets/KUBE.md