k9s

k9s terminal UI for Kubernetes. Use for K8s management.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

k9s is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

k9s terminal UI for Kubernetes. Use for K8s management.

Teams using k9s should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/k9s/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/tools/k9s/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/k9s/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How k9s Compares

Feature / Agent	k9s	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

k9s terminal UI for Kubernetes. Use for K8s management.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# K9s

K9s is a terminal UI (TUI) for Kubernetes. It is faster than clicking in a web dashboard and morediscoverable than raw `kubectl`.

## When to Use

- **Cluster Management**: Viewing Pods, Logs, and YAML in real-time.
- **Debugging**: Shell into a pod (`s`), view logs (`l`), delete pod (`Ctrl+d`).
- **Safety**: Read-only mode prevents accidental deletions in Prod.

## Core Concepts

### Views

Navigate by resource type (`:pods`, `:svc`, `:deploy`).

### XRay

`:xray RESOURCE` creates a dependency tree view (e.g., Service -> Pod -> Node).

### Pulses

`:pulse` gives a high-level health dashboard.

## Best Practices (2025)

**Do**:

- **Use Aliases**: Define aliases for commonly used CRDs.
- **Use Plugins**: Extend K9s with custom scripts (e.g., `kubectl neat` to clean YAML).
- **Context Awareness**: Use skins to color-code Prod (Red) vs Dev (Blue).

**Don't**:

- **Don't rely solely on it**: Know your `kubectl` commands for scripting/automation.

## References

- [K9s Documentation](https://k9scli.io/)