kalpai's promise is simple: take a project from local dev to production and keep every signal — observability, CI, deploys — in The kalpai project released two command-line tools, sklp and skt, aimed at carrying a project from local development through CI/CD and deployment while keeping observability signals in one console. sklp orchestrates local dev stacks, pipelines, ephemeral spaces, daemonless OCI image builds and deploys, plus logs, issues and feature flags, while skt is a standalone rootless version manager that resolves and installs tool binaries as JSON, replacing the earlier mise fallback. skt ships 15 declarative TOML recipes for tools including kubectl, helm, trivy and golangci-lint, with checksum-verified downloads and a content cache. kalpai's promise is simple: take a project from local dev to production and keep every signal — observability, CI, deploys — in one console. Under the hood, that console rests on two small command-line tools built with the same rule: nothing invented, everything assembled from what already works. sklp is the entry point. It orchestrates the local dev stack, runs CI/CD pipelines, manages ephemeral spaces, builds images and deploys — and watches the whole thing. sklp dev / sklp run — local dev environment and pipelines from .sklp/ YAML files sklp space — ephemeral, closed environments from .sklp/space.yaml sklp deploy / sklp image — pilot a node, build OCI images daemonless sklp logs , sklp issue , sklp flag — logs, issues and feature flags from the terminal sklp macos manages the Linux VM it runs on under macOS Virtualization.framework One command, machine-readable, built to be usable by both an operator and an AI agent. Before any of that runs, you need the right binaries on the machine. That's skt : a standalone, rootless version manager. Give it