From mise-toolkit
A 60-second pitch for mise aimed at zero-knowledge users — what it is, what it replaces, why it's better, what it isn't, and the smallest possible mise.toml. Use whenever the user asks "what is mise", "is mise worth it", "should I try mise", or seems unsure whether to adopt it.
npx claudepluginhub ray-manaloto/claude-code-marketplace --plugin mise-toolkitThis skill uses the workspace's default tool permissions.
mise is a single Rust CLI that replaces `nvm + pyenv + rbenv + asdf + tfenv + direnv + (parts of) make` — and works for any language, in one config file per project.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Share bugs, ideas, or general feedback.
mise is a single Rust CLI that replaces nvm + pyenv + rbenv + asdf + tfenv + direnv + (parts of) make — and works for any language, in one config file per project.
node, python, go, ruby, java, rust, cmake, terraform, … per directory. 700+ tools out of the box.cd into a directory. Unloads them when you leave. (Replaces direnv.)mise run test, with parallel deps, last-modified caching, and file-tasks-as-bash-scripts. (Replaces large parts of make.)All in one mise.toml at your project root.
mise.toml[tools]
node = "24"
python = "3.12"
[env]
NODE_ENV = "development"
[tasks.test]
run = "npm test && pytest"
That file gives you: pinned node 24, pinned python 3.12, NODE_ENV=development set in any shell that cds here, and mise run test runs both test suites with both tools on PATH.
| mise | the alternative | |
|---|---|---|
| Speed | ~5 ms shell-prompt overhead (Rust, no shims by default) | asdf bash + shims: ~120 ms per tool call |
| Languages | Every language, one config | nvm + pyenv + rbenv + tfenv = N tools, N configs |
| Reproducibility | mise.lock with checksums + provenance | pin-via-comment in package.json engines |
| Security | Cosign / SLSA / Minisign / GitHub attestations on aqua tools | asdf plugins = arbitrary bash from random GitHub users |
| Env management | [env] block — same file as tools | direnv .envrc = a separate tool |
| Tasks | First-class [tasks] with deps + caching | npm scripts (Node-only) or Makefile (1980s syntax) |
| CI | jdx/mise-action@v3 — install + cache in 3 lines | n-version-managers × m-languages |
brew / apt for dev toolsmise.lock.~/.local/share/mise/installs/.sudo ever needed.libssl or libpq with mise. Use apt/brew for system libraries.npm/pip/cargo. mise installs the runtime; the runtime's package manager handles your project deps.mise is built by Jeff Dickey (@jdx). Same author as usage (CLI spec), pitchfork (process manager), hk (git hooks), and fnox (secret manager). The mise ecosystem is a small set of focused tools.
curl https://mise.run | sh
~/.local/bin/mise use --global node@24
~/.local/bin/node -v # v24.x.x
Or run /mise-install for a guided install with shell activation.
mise-vs-alternatives — head-to-head comparisons (asdf, nvm, pyenv, direnv, volta, brew, apt)mise-overview — the deeper mental modelmise-deployment-models — host vs Docker vs devcontainermise-host-vs-mise-tools — the #1 newbie mistake (system libs vs dev tools)