mise-complete

Configure mise.toml to manage tool versions, tasks, and environment variables.

9|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/pantheon-org/tekhne --skill mise-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mise-complete
Source: https://github.com/pantheon-org/tekhne/tree/main/skills/package-mgmt/mise-complete
Command: npx skills add https://github.com/pantheon-org/tekhne --skill mise-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes and automates the setup and management of developer environments, ensuring consistency across projects and team members by leveraging the Mise tool manager.

Core Features & Use Cases

  • Tool Version Management: Pin and manage specific versions of languages and tools (Node.js, Python, Go, etc.) per project.
  • Task Automation: Define and run project-specific tasks (build, test, lint, deploy) consistently.
  • Environment Configuration: Manage environment variables and paths for reproducible development.
  • Migration: Facilitates migration from other tool managers like asdf, nvm, pyenv.
  • Use Case: A new developer joins a project. Instead of manually installing Node.js v20, Python 3.11, and setting up environment variables, they run a single mise install command, and Mise handles all tool installations and environment configurations based on the project's mise.toml.

Quick Start

Use the mise-complete skill to install all project-specific tools by running mise install.

Frequently Asked Questions about mise-complete

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

FAQPage Schema
How do I manage tool versions for a reproducible dev environment?

You can manage tool versions for a reproducible dev environment by pinning specific versions of languages like Node.js and Python per project in a mise.toml file, ensuring consistency across local shells and CI.

What is the best way to migrate from asdf, nvm, or pyenv to a new tool manager?

Migrating from asdf, nvm, or pyenv is handled by configuring your existing tool versions and environment variables into a single mise.toml file, allowing you to run a unified mise install command to restore your setup.

How do I define and run project-specific tasks consistently?

You define and run project-specific tasks consistently by declaring build, test, lint, and deploy actions within your mise.toml configuration, enabling automated task execution across different machines.

Can I manage environment variables and paths for deterministic builds?

Yes, you can manage environment variables and paths for deterministic builds by using layered environment configuration in mise.toml, which guarantees reproducible development conditions across local shells and CI pipelines.

Why is my mise.toml behavior not working correctly in CI?

Debugging mise.toml behavior in CI requires verifying your layered environment variables and pinned tool versions are precisely configured, as incorrect settings often break reproducibility in automated shells.