mise-expert_skill

This skill helps you manage tool versions, per-directory environments, and custom tasks with mise for reproducible dev setups.

Python

12

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill samhvw8/dotfiles --skill mise-expert

SKILL.md25.0 KB

Overview

This skill is mise-expert, a focused guide and assistant for the Mise development environment manager. It helps teams install and manage runtime versions, configure per-project environments, and design task runners using mise.toml. Use it to replace and consolidate asdf, direnv, and Make/npm scripts into a single, reproducible workflow.

How this skill works

The skill inspects project files (mise.toml, .env, .tool-versions, Makefile) and recommends or generates mise configurations. It guides tool installation (node, python, go, ruby, rust, etc.), creates task definitions with caching and dependencies, and configures per-directory environment variables. It also provides migration steps, CI integration patterns, and troubleshooting tips for version conflicts and task failures.

When to use it

Bootstrapping a new project or onboarding new developers
Pinning and installing language/runtime versions for reproducible builds
Replacing asdf, direnv, Makefiles, or npm scripts with a single config
Designing cacheable, parallel task workflows and watch-mode development loops
Integrating consistent environments into CI/CD pipelines

Best practices

Declare exact tool versions in [tools] for reproducibility; use file references for existing version files
Define sources and outputs for cacheable tasks and prefer idempotent single-purpose tasks
Group related tasks with namespacing and add aliases for common workflows
Use depends arrays to enable parallel execution and set platform-specific run variants when needed
Keep secrets out of mise.toml: load them from a gitignored .env and reference via vars

Example use cases

Migrate .tool-versions or asdf setups into a root mise.toml and run mise install to provision runtimes
Create a monorepo configuration where root tasks bootstrap frontend and backend and each package has its own mise.toml
Replace a Makefile with explicit mise tasks that include sources/outputs for caching and parallel test runs
Configure per-directory environment switching and secrets management for local/staging/production
Add mise to CI (GitHub Actions/GitLab CI) to ensure the same tool versions and cached build artifacts in pipelines

FAQ

Yes. Declare required runtimes under [tools] (node, python, go, rust, ruby, etc.) and use mise install to provision them, or use mise use to temporarily switch versions.

How do I keep secrets out of version control?

Store non-sensitive defaults in mise.toml and load secrets from a gitignored .env via vars (_.file = ".env"). Reference those vars in [env] so secrets remain local.