mise
Skill5 starsChanged 54 days agoMITView on GitHub
mise: set up a project's toolchain in mise.toml, migrate Makefile or npm scripts to tasks, or wire mise into CI or containers.
- Pipes a download into a shell
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
- moabualruz/fulcrum★ 4same name
- aaronflorey/agent-skills★ 2same 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-mdSkill
- agents-memorySkill
- agentsview-extractSkill
- agentsview-resumeSkill
- backfill-unit-testsSkill
- dotnet-upgradeSkill
- github-epicSkill
- gitlab-epicSkill
- pr-workflowSkill
- record-walkthroughSkill
- setup-agent-ready-repoSkill
- tech-leadSkill
- tidy-commitsSkill
- write-e2e-testsSkill
The file
Files
mise
One committed mise.toml is the single source for tools, runtimes, and
tasks. Official surface: https://mise.jdx.dev/. This skill is the
conventions.
Host
- Author repo-root
mise.tomlwith[tools]and[tasks.*]. That filename is the default; other mise config paths (.mise.toml,mise/config.toml, …) only when the user names the file. Edit an existing mise config in place rather than adding a second one. Versions live only there — after a migrate, droppackage.jsonpackageManager/ corepack. Preferaqua:andgithub:(built in, provenance-verified);ubi:owner/repobecomesgithub:owner/repo. Enable idiomatic files only for interop:mise settings add idiomatic_version_file_enable_tools node. Done when the file is repo-rootmise.toml(unless the user named another path) and tool versions are declared only there, except idiomatic files enabled for interop. - Prefix runtimes;
latestfor linters.go = "1.27",python = "3.14",java = "temurin-25",node = "lts",dotnet = "10"install the newest matching release. Exact patches stay frozen. Go ≤1.20 needsprefix:1.20because1.20is an exact tag (Go). npm ranges (1.27.x,^1.27) are rejected. .NET sharesDOTNET_ROOT(global.jsonselects SDK); side-by-side runtimes use tool options (dotnet = ["10", { version = "8.0.14", runtime = "aspnetcore" }]), whereruntimeneeds an exact patch.
[tools]
shellcheck = "latest"
actionlint = "latest"
uv = "latest"
go = "1.27"
node = "lts"
java = "temurin-25"
python = "3.14"
[tasks.test]
description = "Run all test scripts"
run = "..."
[tasks.lint]
description = "Run all linters"
depends = ["lint-shell", "lint-actions"]- Translate Makefile or npm script targets into
[tasks]verbatim: same names, same shell (pipes, loops,$()),dependsfor the old order. Drive work withmise run <task>. - First checkout:
mise trust, thenmise install. Done whenmise run <task>runs on the declared tools. Untrusted configs make install and tasks silently no-op;jdx/mise-actiontrusts in CI. On a Gatekeeper warning for a precompiled binary (e.g. PHP):xattr -d com.apple.quarantine ~/.local/share/mise/installs/<tool>/<version>/....
CI
jdx/mise-action@v4 reads mise.toml and replaces per-tool setup
actions (actions/setup-python, astral-sh/setup-uv, …). Run work
through tasks:
- uses: jdx/mise-action@v4
- run: mise run test
- run: mise run lintScope a job with install_args (node bun) so versions still come
only from mise.toml and a JS job does not pull unrelated SDKs. Done
when the job has no duplicate setup action for a tool already in
mise.toml.
Containers
Pin the mise binary by version and sha256 (curl | bash is not a pin).
mise install --system lands in /usr/local/share/mise; make it
world-readable so a uid-dropped runtime user sees the tools. Done when
that user can run the declared binaries.
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.

