mise
Skill2 starsChanged 7 months agoMITView on GitHub
Configure and use `mise` for dev tool management, environment variables, and task running. Use this skill when the user mentions `mise`, `mise.toml`, `.mise.toml`, `mise use`, `mise install`, `mise run`, `mise x`, project tool versions like Node or Python, task definitions, env vars, hooks, backends, or asks how to configure mise in a project.
- Reads credentials
9 other projects use a version of this.
Adopted by
Most recently taken up by
- petr-korobeinikov/skillstheir own version, first seen Nov 8, 2026
- fmind/dottheir own version, first seen Nov 8, 2026
- fmind/dotfilestheir own version, first seen Nov 8, 2026
- mritd/skillstheir own version, first seen Oct 13, 2026
- Cosmian/kmstheir own version, first seen Oct 8, 2026
- dstotijn/agent-skillstheir own version, first seen Sep 21, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- Cosmian/kms★ 372same name
- ivy/dotfiles★ 15same name
- fmind/dot★ 13same name
- fmind/dotfiles★ 13same name
- akunzai/agent-skills★ 5same name
- moabualruz/fulcrum★ 4same name
- dstotijn/agent-skills★ 1same name
- mritd/skills★ 1same name
- petr-korobeinikov/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- other/AGENTS.mdAGENTS.md
- beamng-modsSkill
- bootstrap-vueSkill
- charmbraceletSkill
- depsdotdevSkill
- find-domainSkill
- github-cliSkill
- go-cobraSkill
- goreleaserSkill
- go-viperSkill
- kasettoSkill
- laravel-actionsSkill
- lefthookSkill
- pelican-panel-pluginsSkill
- php-monorepo-builderSkill
- php-saloonSkill
- prd-todo-slicerSkill
- prd-to-kandev-tasksSkill
- qodo-mergeSkill
- release-pleaseSkill
- rewrite-in-goSkill
- shieldsioSkill
- skill-researcherSkill
- skill-scoutSkill
- taskfileSkill
- website-visual-testingSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 127
Add to shell rc file to auto-activate mise:
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mise
Mise is a polyglot tool version manager and task runner. It manages dev tools, environment variables, and tasks for projects.
Core Concepts
Configuration: mise.toml in project root (or .mise.toml, .config/mise/config.toml). Config is hierarchical - child directories override parent settings.
Tools: Defined in [tools] section. Mise installs and activates correct versions per-directory.
Environment: Defined in [env] section. Set project-specific env vars that activate when entering directory.
Tasks: Defined in [tasks] section or as standalone scripts in mise-tasks/ directory.
Quick Reference
Basic mise.toml structure:
[tools]
node = "22"
python = "3.12"
[env]
NODE_ENV = "development"
[tasks.build]
run = "npm run build"Essential Commands
| Command | Description |
mise use node@22 | Install and set tool version in mise.toml |
mise use -g node@22 | Set global tool version |
mise install | Install all tools from config |
mise run <task> | Run a task |
mise x -- <cmd> | Execute command with mise environment |
mise ls | List installed tools |
mise doctor | Diagnose mise setup |
Tool Backends
Tools can be installed from various backends:
- Core:
node,python,go,ruby(built-in) - npm:
npm:prettier,npm:eslint - pipx:
pipx:black,pipx:ruff - cargo:
cargo:ripgrep - github:
github:BurntSushi/ripgrep - aqua:
aqua:hashicorp/terraform
When to Consult References
For detailed information, read the appropriate reference file:
- Configuration options (tool options, env directives, settings):
references/configuration.md - Task definition (toml tasks, file tasks, arguments, dependencies):
references/tasks.md - CLI commands (all command flags and examples):
references/cli.md - Installable overview (where to look first for all installable options):
references/installable-overview.md - Core tools (built-in first-party languages):
references/core-tools.md - Backends (supported package ecosystems and backend families):
references/backends.md - Registry aliases (tool shorthands accepted by
mise use):references/registry-tools.md - Hooks and advanced features:
references/advanced.md
Common Patterns
Project with Node.js and Python
[tools]
node = "lts"
python = "3.12"
[env]
NODE_ENV = "development"
PYTHONDONTWRITEBYTECODE = "1"
[tasks.dev]
run = "npm run dev"
[tasks.test]
run = ["npm test", "pytest"]Task with Dependencies
[tasks.build]
run = "npm run build"
sources = ["src/**/*.ts"]
outputs = ["dist/**/*.js"]
[tasks.deploy]
depends = ["build", "test"]
run = "./scripts/deploy.sh"File Task (mise-tasks/build)
#!/usr/bin/env bash
#MISE description="Build the project"
#MISE depends=["lint"]
npm run buildEnvironment from .env file
[env]
_.file = ".env"
_.path = "./bin"Shell Activation
Add to shell rc file to auto-activate mise:
# bash: ~/.bashrc
eval "$(mise activate bash)"
# zsh: ~/.zshrc
eval "$(mise activate zsh)"
# fish: ~/.config/fish/config.fish
mise activate fish | sourceWithout activation, use mise x -- <command> or mise run <task>.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

