kubernetes
Skill4 starsChanged 9 months agoMITView on GitHub
Manage Kubernetes clusters via kubectl
- Installs packages
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 107
Use -o yaml or -o json for detailed output
- Very specific: line 108
Use --watch to monitor changes in real time
- Very specific: line 109
Use -l app=myapp to filter by labels
- Very specific: line 110
Always specify -n <namespace> to avoid surprises
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kubernetes
Manage Kubernetes clusters via kubectl.
Setup
- Check if installed:
command -v kubectl && kubectl version --client - Install:
# macOS brew install kubectl # Ubuntu / Debian curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl" chmod +x kubectl && sudo mv kubectl /usr/local/bin/ # Or via apt (see https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/) sudo apt update && sudo apt install -y kubectl
Basics
# Pods
kubectl get pods -A # all namespaces
kubectl get pods -n <ns> -o wide # with IPs and nodes
kubectl describe pod <pod> -n <ns>
kubectl logs <pod> -n <ns> --tail=100
kubectl logs <pod> -n <ns> -c <container> # multi-container
kubectl exec -it <pod> -n <ns> -- sh
# Deployments
kubectl get deployments -n <ns>
kubectl describe deployment <name> -n <ns>
kubectl scale deployment <name> --replicas=3 -n <ns>
kubectl rollout status deployment <name> -n <ns>
kubectl rollout restart deployment <name> -n <ns>
kubectl rollout undo deployment <name> -n <ns>
# Services
kubectl get svc -n <ns>
kubectl describe svc <name> -n <ns>
kubectl port-forward svc/<name> 8080:80 -n <ns>
# ConfigMaps and Secrets
kubectl get configmap -n <ns>
kubectl get secret -n <ns>
kubectl get secret <name> -n <ns> -o jsonpath='{.data}'Diagnostics
# Events (useful for debug)
kubectl get events -n <ns> --sort-by='.lastTimestamp'
# Top (metrics)
kubectl top pods -n <ns>
kubectl top nodes
# Nodes
kubectl get nodes -o wide
kubectl describe node <name>
kubectl cordon <node> # mark unschedulable
kubectl drain <node> --ignore-daemonsets --delete-emptydir-dataApply & Delete
# Apply manifest
kubectl apply -f <file.yaml>
kubectl apply -f <directory>/
# Dry run
kubectl apply -f <file.yaml> --dry-run=client
# Delete
kubectl delete -f <file.yaml>
kubectl delete pod <pod> -n <ns>Contexts
# List contexts
kubectl config get-contexts
# Switch context
kubectl config use-context <name>
# View current context
kubectl config current-contextTips
- Use
-o yamlor-o jsonfor detailed output - Use
--watchto monitor changes in real time - Use
-l app=myappto filter by labels - Always specify
-n <namespace>to avoid surprises
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- notque/vexjoy-agent★ 444same name
- notque/claude-code-toolkit★ 442same name
- Mindrally/skills★ 275same name
- OpenHands/extensions★ 167same name
- magnus919/agent-skills★ 162same name
- nitinjain999/platform-skills★ 71same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- mjunaidca/mjs-agent-skills★ 27same name
- kcns008/cluster-agent-swarm-skills★ 25same name
- last9/mithai★ 20same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use documentation-site, gitops and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
fmindSkilldocumentation-site
Build Zensical docs and course sites: navigation, API docs, Pages, MkDocs/Hugo migration.
Also in 3 projects that use this
kcns008Skillgitops
GitOps Agent (Flow) — manages ArgoCD applications, Helm charts, Kustomize overlays, deployment strategies (canary, blue-green, rolling), multi-cluster GitOps, and drift detection for Kubernetes and OpenShift clusters.
Also in 3 projects that use this
cashew-labsSkillcli-development
Design and implement command-line interfaces with subcommand-scoped help, actionable success output, and debuggable failure output. Use when creating or modifying CLI commands, argument parsing, help and usage text, exit codes, or command UX for humans and agents.
Also in 4 projects that use this
Consortium-teamSkillprocess
Use when the user has external inputs to analyze — transcripts, documents, notes, or pasted text. Extracts structured information (requirements, constraints, decisions, questions) and updates companion context files.
Also in 3 projects that use this
SentrySkilldatadog
Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.
Also in 3 projects that use this
third-order-labsSkillproject-scaffolding
Templates, directory conventions, and document structure for long-form fiction projects. Contains the full template library — documents are created as the project needs them, not all at once.
Also in 3 projects that use this
In this repository83 other files it gives its agents.
- a11y-axeSkill
- airtableSkill
- asanaSkill
- audio-ttsSkill
- aws-cliSkill
- azure-cliSkill
- backupSkill
- bookmarksSkill
- browser-automationSkill
- bundler-analyzeSkill
- calculatorSkill
- calendarSkill
- cargoSkill
- changelog-genSkill
- claude-codeSkill
- clickupSkill
- color-contrastSkill
- crypto-walletSkill
- databaseSkill
- discordSkill
- docker-composeSkill
- dockerSkill
- dora-metricsSkill
- emailSkill
- ffmpegSkill
- filesystemSkill
- gcloudSkill
- githubSkill
- gmailSkill
- gogSkill
- google-calendarSkill
- habitsSkill
- healthSkill
- hubspotSkill
- image-genSkill
- imagemagickSkill
- image-toolsSkill
- jiraSkill
- journalSkill
- lighthouseSkill
- linearSkill
- locationSkill
- media-configSkill
- meeting-notesSkill
- nginxSkill
- notesSkill
- notionSkill
- obsidianSkill
- ocrSkill
- pandocSkill
- paymentsSkill
- pdf-toolsSkill
- pip-poetrySkill
- pm2Skill
- pomodoroSkill
- project-managerSkill
- qr-codeSkill
- railway-deploySkill
- redis-cliSkill
- release-notesSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

