§ 00 — Productivity booster for dev tools
klim maps the tools a project depends on, turns the answer into a .klim.yaml contract, and runs install · audit · diff · upgrade · restore through the package managers your machine already trusts.
$ klim plan show
Planning changes for .klim.yaml (7 tools, 1 pack)
~ kubectl 1.29.4 → 1.30.1 brew confidence 98% low risk
~ terraform 1.6.6 → 1.8.2 brew confidence 71% review changelog
+ sops — → 3.9.1 brew confidence 99%
✓ gh 2.50.0 already matches contract
────────────────────────────────────────────────────────
summary +1 ~2 ·4 disk 142 MB ≈ 38s
checkpoint pre-apply-2026-06-15T11:42Z will be captured
$ klim plan apply --yes # or: klim plan diff teammate.yaml§ 01 — The idea
Most dev environments are a folk tradition — passed down in READMEs, Slack threads, and the dotfiles repo nobody dares to touch. klim makes the tradition literal.
Everything installed on this machine — version, source, binary path, supplier — collected into one local inventory you can actually grep.
$ klim tool list --output json
Turn the inventory into a versioned contract. One file. The same contract drives onboarding, CI, devcontainers, and Dockerfiles — generated from one source.
$ klim project generate --target github-actions
Install · upgrade · audit · diff · restore · share. klim never reinvents package management; it delegates to brew, winget, apt, scoop, choco, snap, npm.
$ klim plan apply && klim security score
klim is the layer above packages, scripts, and prompts — the contract they can all read from.
§ 02 — What it does
01 / contract
.klim.yaml lives next to your code.
Required tools, version ranges, a pack or two. klim project init
scaffolds it from what your repo already references.
.klim.yaml
project: api-gateway
requires:
go: "~1.22" # range
terraform: ">=1.6 <2.0"
kubectl: "^1.30"
sops: "3.9.x"
packs:
- platform/cloud-native
policy:
allowed_licenses: [MIT, Apache-2.0, BSD-3-Clause]
max_severity: high$ klim plan diff teammate.yaml
tool you they
go 1.22.4 1.22.4 match
terraform 1.6.6 1.8.2 differs
docker 25.0 via brew 26.1 via colima source differs
terraform-docs — 0.18.0 remote only
exit 1 // CI-friendly: nonzero on drift02 / diff
Diff your toolchain against a teammate's export, a share token, or the contract checked into the repo. Exits nonzero on drift, which is what CI wants to hear.
03 / plan · apply · rollback
Every change is previewed with a confidence score, applied through a native package manager, and bracketed by an auto-captured checkpoint you can roll back to with a single command.
$ klim plan apply — postcheck + auto checkpoint
capturing checkpoint pre-apply-2026-06-15T11:42Z ✓
+ sops 3.9.1 brew install sops ✓
~ terraform 1.8.2 brew upgrade terraform ✓
~ kubectl 1.30.1 brew upgrade kubectl ✓
postcheck:
✓ shell resolution ✓ binary validation
✓ PATH consistency ✓ manager integrity
to undo: klim plan rollback pre-apply-2026-06-15T11:42Z$ klim security score --badge
environment score 94 / 100 grade A
freshness 98 last update 2d ago
security 86 3 advisories (low / med)
PATH hygiene 100 no shadowed binaries
contract match 92 1 tool out of range
shields.io badge written to README.md ✓04 / score
A 0–100 health grade with a per-category breakdown — freshness, security, PATH hygiene, contract match. Embeds as a shields.io badge so the README has skin in the game.
05 / share
Compact klim:v1:… tokens encode the
essentials. The recipient runs klim share link open
and lands on the same setup.
$ klim share link → paste → klim share link open
you $ klim share link
klim:v1:eyJ0b29scyI6WyJnbyIsInRlcmYiLCJrdWJlIl0sInBhY2tzIjpb…
them $ klim share link open klim:v1:eyJ0b29scyI6...
reading 8 tools, 1 pack…
install plan ready — run klim plan apply to continueagent · stable JSON · deterministic exit codes
$ klim project check --output json
{
"project": ".klim.yaml",
"status": "needs_action",
"missing": ["terraform"],
"outdated": ["kubectl"],
"score": 94
}
exit 2 // 0=ok 1=drift 2=needs_action06 / agents
Same flags, same JSON, same exit codes — whether the caller is you, CI, or an LLM. Agents stop guessing brew commands and start calling a contract.
§ 03 — In motion
klim ships with an interactive TUI that mirrors what the CLI exposes — pick whichever fits the moment, the underlying data and operations are the same.
fig. 2 — klim TUI, recorded session
§ 04 — Install
klim ships as a single binary. No runtime, no daemon, no account.
~ $ — Homebrew (recommended)
$ brew install nassiharel/tap/klimor, via curl
$ curl -fsSL https://raw.githubusercontent.com/nassiharel/klim/main/install.sh | bash~ $ — curl (recommended)
$ curl -fsSL https://raw.githubusercontent.com/nassiharel/klim/main/install.sh | bashor, via Homebrew on Linux
$ brew install nassiharel/tap/klimPS > — winget (recommended)
> winget install nassiharel.klimor, via PowerShell installer
> irm https://raw.githubusercontent.com/nassiharel/klim/main/install.ps1 | iexScoop (Windows)
> scoop bucket add nassiharel
https://github.com/nassiharel/scoop-bucket
> scoop install klimGo install
$ go install github.com/nassiharel/klim/cmd/klim@latestPre-built binaries for macOS, Linux, and Windows (amd64 + arm64) on GitHub Releases.
§ 05 — Honest answers