mise

Manage polyglot tool versions, environment variables, and tasks via mise.toml.

14|5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/oakoss/agent-skills --skill mise-oakoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise
Source: https://github.com/oakoss/agent-skills/tree/main/skills/mise
Command: npx skills add https://github.com/oakoss/agent-skills --skill mise-oakoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines your development environment by managing multiple tool versions, environment variables, and project tasks from a single configuration file, eliminating conflicts and simplifying setup.

Core Features & Use Cases

  • Polyglot Version Management: Install and switch between different versions of Node.js, Python, Rust, Go, and many other languages seamlessly.
  • Task Automation: Define and run project-specific tasks (build, test, lint, deploy) with dependencies and watch modes.
  • Environment Variable Management: Configure per-project environment variables and load them from .env files.
  • Use Case: When starting a new project that requires Node.js v20 and Python v3.11, you can define these versions in mise.toml and run mise install to set them up, along with defining a mise run build command for your project's build process.

Quick Start

Use the mise skill to install the Node.js version specified in the project's mise.toml file.

Frequently Asked Questions about mise

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

FAQPage Schema
How do I manage multiple programming language versions in one project?

You can manage multiple language versions by defining them in a single `mise.toml` file and running `mise install` to automatically download and pin the required Node.js, Python, or Rust toolchains for your project.

What is the best way to automate project-specific build and test tasks?

The best way to automate project-specific build and test tasks is to define them within a unified configuration file. This method supports task dependencies, watch modes, and incremental builds, allowing you to execute complex workflows efficiently without relying on external task runners.

Can I load environment variables from a .env file for my development setup?

Yes, you can configure per-project environment variables and load them directly from `.env` files. This is managed alongside your tool versions and tasks within the `mise.toml` configuration to streamline your development setup.

Does this dev environment manager work with package managers like npm, cargo, and pipx?

Yes, this dev environment manager integrates with backends like npm, cargo, pipx, and GitHub releases. This comprehensive toolchain management allows you to install and track tool versions across diverse programming languages seamlessly.

How do I set up a Node.js and Python development environment without version conflicts?

To set up a Node.js and Python development environment without version conflicts, specify the exact versions required, such as Node.js v20 and Python v3.11, in your `mise.toml` file. Running a single installation command sets up the isolated toolchain for your project.

When do I need a unified configuration file for my polyglot tool versions?

You need a unified configuration file for your polyglot tool versions when your project spans multiple programming languages and requires a reproducible setup. It eliminates the friction of installing and switching between different language versions manually across diverse environments.