mise-configuration

Centralize environment configuration in a `.mise.toml` `[env]` section.

62|10|Updated Dec 4, 2025

Search Tags:#configuration #mise #templating #virtualenv #env

Ready to run

npx skills add https://github.com/terrylica/cc-skills --skill mise-configuration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mise-configuration
Source: https://github.com/terrylica/cc-skills/tree/main/plugins/itp/skills/mise-configuration
Command: npx skills add https://github.com/terrylica/cc-skills --skill mise-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces a single source of truth for environment configuration by loading all values from a centralized .mise.toml [env] section. Scripts read values via standard environment variable patterns, ensuring consistent behavior whether mise is installed or not.

Core Features & Use Cases

Centralized configuration: define defaults and overrides in one place.
Cross-language compatibility: Python, Bash, JavaScript, Go, and Rust patterns supported.
Automatic Python venv creation: auto-create and activate a virtual environment on entry.
Templated and composable: supports special directives like _.file, _.path, and _.source.

Quick Start

Create a Python venv automatically and read an env var with a default:

[env]
_.python.venv = { path = ".venv", create = true }
FOO = "{{ env.FOO | default('bar') }}"

Frequently Asked Questions about mise-configuration

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

FAQPage Schema

How do I centralize environment configuration across multiple projects?▼

Centralize environment configuration by defining all variables in a single `.mise.toml` `[env]` section. Scripts read values via standard environment variable patterns, ensuring consistent behavior across Python, Bash, JavaScript, Go, and Rust projects without requiring mise to be installed.

Can I automatically create and activate a Python virtual environment when entering a project?▼

Yes. Use the `_.python.venv` directive in `.mise.toml` with `path` and `create = true` to auto-create and activate a virtual environment on mise activation, eliminating manual venv setup steps.

What's the best way to manage environment variables with defaults across scripts and deployments?▼

Define environment variables with template-based defaults in `.mise.toml` using syntax like `FOO = "{{ env.FOO | default('bar') }}"`. This provides fallback values while allowing overrides, ensuring consistent behavior in scripts, tests, and deployments.

Does mise support loading environment variables from .env files?▼

Yes. Mise loads environment variables from `.env` files and extends PATH using directives like `_.file` and `_.source`, enabling seamless integration with existing environment workflows and configuration patterns.

Can I pin specific tool versions for reproducible environments across a team?▼

Yes. Version pinning in `.mise.toml` `[env]` configuration ensures reproducible toolchains across team members and deployments, maintaining consistent tool versions without manual version management.

What happens if a required environment variable is missing?▼

Mise supports required and redacted variable directives in `.mise.toml`, allowing you to enforce mandatory environment values and mask sensitive data, preventing deployments with incomplete or unsafe configurations.