skt tools — supported toolchains

skt covers two classes of tool. Runtimes have bespoke resolvers because their version indices are richer than any single manifest; everything else is a declarative TOML recipe. This page lists what ships out of the box.

Runtimes

Language runtimes have hand-written resolvers, because their upstream version indices (nested LTS aliases, channel manifests, git tags) are richer than a declarative recipe can express. All support partial-version pins.

runtime	version source	partial pins
`go`	`go.dev/dl` JSON manifest	yes (`go@1.25`)
`node`	`nodejs.org/dist` index, LTS codename aliases	yes (`node@24`)
`rust`	`static.rust-lang.org` channel manifests (rustup-free)	yes (`rust@stable`, `rust@1.79`)
`python`	`python/cpython` git tags → python-build-standalone prebuilt archives	yes (`python@3.12`)

skt install go@1.25.5
skt install node@24
skt install rust@stable
skt install python@3.12

CLIs via TOML recipes

Fixed-release CLIs are described by a single embedded TOML recipe each — no Rust code per tool. These ship in the binary:

tool	source
`kubectl`	`dl.k8s.io`
`helm`	`get.helm.sh`
`bun`	GitHub `oven-sh/bun` releases
`trivy`	GitHub `aquasecurity/trivy` releases
`gitleaks`	GitHub `gitleaks/gitleaks` releases

skt install kubectl@1.31.0
skt install helm@3.16.0
skt install trivy@0.70.0

Most of these require a full version (the recipe pins an exact release asset). Adding a new CLI is just dropping in a recipe — see Recipes.

go-install modules

Go tools distributed only as modules (no prebuilt binary) are installed through the go install backend. They resolve a Go runtime first, then build the module at the pinned version:

tool	module
`swag`	`github.com/swaggo/swag/cmd/swag`
`oasdiff`	`github.com/oasdiff/oasdiff`
`govulncheck`	`golang.org/x/vuln/cmd/govulncheck`
`gotestsum`	`gotest.tools/gotestsum`
`migrate`	`github.com/golang-migrate/migrate/v4/cmd/migrate`

skt install swag@1.16.6
skt install govulncheck@1.1.3

These accept the module's own version tags.

pnpm via corepack

pnpm is installed through Node's bundled corepack, so a pnpm install implies a Node runtime and pins the package-manager version corepack activates:

skt install pnpm@11.0.0

Unsupported tools are an error

skt deliberately has no "guess the GitHub asset" fallback. Every installable tool has an explicit recipe with a pinned checksum source. An unrecognised tool fails with an actionable message telling you to write a recipe — precision and supply-chain verification over breadth. See Recipes to add one.