pickfit

BrowseDeveloper CLIs

kx

kubectl wrapper that references listed Kubernetes resources by index number.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • System packages: kubectl
  1. brew install jzills/tap/kx

    brew install jzills/tap/kx
  2. install kubectl prerequisite

    brew install kubectl

Check that it works

kx --help 2>&1

The output should contain “kubectl, indexed”.

Run kx with a kubectl-style command, such as listing pods, to see numbered rows you can refer to by index.

Linux x86_64

You need first

  • System packages: kubectl
  1. install kx via uv tool

    uv tool install kx-cli
  2. install kubectl prerequisite binary

    curl -fsSL -o "$HOME"/.local/bin/kubectl https://dl.k8s.io/release/v1.34.1/bin/linux/amd64/kubectl && chmod +x "$HOME"/.local/bin/kubectl && kubectl version --client
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

uv tool install kx-cli
curl -fsSL -o /home/sbx/.local/bin/kubectl https://dl.k8s.io/release/v1.34.1/bin/linux/amd64/kubectl && chmod +x /home/sbx/.local/bin/kubectl && kubectl version --client
kx --version
kx theme

Check that it works

kx --version

The output should contain “kx v0.11.0”.

First thing to try

kx theme

Run kx with a kubectl-style command, such as listing pods, to see numbered rows you can refer to by index.

What it does

  • Refer to listed resources by their index number
    Not tested
  • Triage a namespace and diagnose unhealthy resources
    Not tested
  • Scan workload images for vulnerabilities
    Not tested
  • Show the ownership graph for resources
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • list pods with numbered rows
  • fetch logs for third listed pod
  • diagnose why indexed resource is unhealthy
  • read indexed Secret value in plaintext
  • scan indexed workload images for CVEs

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

Installs and starts

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version v0.11.1

Differences the test machine hit

  • README: Requires kubectl on PATH
    In the test: brew install kubectl needed before kx is useful

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version v0.11.0

Differences the test machine hit

  • README: Requires kubectl on your PATH
    In the test: installed real kubectl v1.34.1 binary to ~/.local/bin via dl.k8s.io release artifact before kx could talk to a cluster; kx --version reported kubectl not found on PATH until then

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.