mise

Manage project tool versions and runtime configurations via mise.toml.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/nsheaps/ai-mktpl --skill mise-nsheaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise
Source: https://github.com/nsheaps/ai-mktpl/tree/main/plugins/mise/skills/mise
Command: npx skills add https://github.com/nsheaps/ai-mktpl --skill mise-nsheaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mise centralizes and simplifies managing runtime and tool versions across polyglot development projects so developers avoid "works on my machine" issues, inconsistent CI builds, and manual tool installation overhead.

Core Features & Use Cases

  • Unified version pinning: Declare node, python, go, rust, npm/pip/cargo packages, and binaries in a single mise.toml to ensure consistent runtimes.
  • Automated installation & activation: Install and activate pinned tools locally or in CI, resolve version conflicts, and surface environment variables needed by builds and tasks.
  • Backend and CI integration: Support for multiple backends (npm, pipx, cargo, ubi) and workflows like trusting configuration in CI and running mise exec for reproducible test runs.
  • Use case: Onboarding a new developer becomes one step—clone the repo, trust and install mise.toml, and start a shell with the project's exact toolchain available.

Quick Start

Create or update mise.toml to pin the required runtimes (for example node 22 and python 3.12), run the mise installer, and activate the shell so the project's declared tools are available.

Frequently Asked Questions about mise

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multiple tool versions for a polyglot development project?

Manage multiple tool versions by declaring required runtimes like node and python in a single mise.toml file, which ensures consistent environments and eliminates version conflicts across machines.

How do I automate tool installation and activation for CI/CD pipelines?

Automate tool installation and activation for CI/CD pipelines by trusting the mise.toml configuration, running the installer, and using mise exec to surface environment variables for reproducible test runs.

Can I pin npm, pipx, and cargo packages in the same configuration file?

Yes, you can pin npm, pipx, cargo, and ubi packages in the same configuration file, allowing unified version pinning for both runtimes and binaries within a single project setup.

What is the best way to onboard new developers to a complex runtime environment?

The best way to onboard developers is to centralize runtime configuration in a mise.toml file, reducing manual installation overhead to a single step of cloning the repo and activating the shell.

How do I resolve version conflicts between local shells and CI builds?

Resolve version conflicts between local shells and CI builds by using a centralized configuration file that automatically installs, activates, and pins exact tool versions for reproducible environments.