mise
Skill16 starsChanged 3 days agoISCView on GitHub
Use when adding, updating, troubleshooting, or managing mise tool dependencies. Supplements /install with mise-specific context about backends, lockfiles, and the github-first policy.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- fmind/dottheir own version, first seen Nov 15, 2026
- fmind/dotfilestheir own version, first seen Nov 15, 2026
- petr-korobeinikov/skillstheir 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
- fmind/dot★ 13same name
- fmind/dotfiles★ 13same name
- akunzai/agent-skills★ 5same 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-local-mdSkill
- allowSkill
- label-issueSkill
- nvimSkill
- updateSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 98
Verify the tool runs. Check the binary name — it may differ from the repo name (e.g., BurntSushi/ripgrep installs rg).
- Distinctive: line 103
Check current vs latest:
- Very specific: line 143
If assets exist but use unusual naming, the github: backend may not auto-detect them.
- Very specific: line 157
Use the full tag string as the version (e.g., jq-1.8.1 not 1.8.1).
- Very specific: line 169
Never use latest — always pin to a specific version
- Distinctive: line 170
Always regenerate lockfile after config changes
- Distinctive: line 171
Always verify the tool runs after installing
“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 Tool Management
Mise-specific context for managing CLI tool dependencies. Use /install to add
a new tool end-to-end; use /mise when you need to understand backends,
troubleshoot failures, update versions, or regenerate lockfiles.
Arguments
$ARGUMENTSKey Files
| File | Purpose |
home/dot_config/mise/config.toml | User tool manifest — edit here, never ~/.config/mise/config.toml |
home/dot_config/mise/mise.lock | User lockfile (auto-generated); ~/.config/mise/mise.lock is a symlink to it |
home/dot_config/mise/.mise/locks/, .mise/locks/ | npm dependency graphs the lockfiles reference by path and digest (auto-generated) |
mise.toml | Project dev tool manifest (bats, shellcheck, hk, etc.) |
mise.lock | Project lockfile (auto-generated) |
home/run_onchange_00-install-mise-tools.sh.tmpl | Install trigger — runs on config/lock hash change |
Backend Priority
Per ADR-005:
| Priority | Backend | When to use |
| 1 | Native (python, node) | Runtimes |
| 2 | github:owner/repo | CLI tools with GitHub releases |
| 3 | cargo: | Rust tools without prebuilt binaries |
| 4 | pipx: | Python CLI tools |
| 5 | npm: | Node CLI tools |
Do NOT use aqua: backend. Registry lag and attestation mismatches break
chezmoi apply. The github: backend talks directly to GitHub Releases with
checksum, attestation, and SLSA verification.
Instructions
Adding a tool
- Find the GitHub repo and latest release tag:
gh release view --repo owner/repo --json tagName --jq '.tagName' - Determine version format — most use bare numbers (
0.18.2) orv-prefixed tags (mise strips thevautomatically). Some tools use non-standard tags (e.g., jq usesjq-1.8.1). If the tag doesn't followvX.Y.Z, use the full tag string as the version. - Edit
home/dot_config/mise/config.toml— add under the CLI tools section:"github:owner/repo" = "1.2.3" - Apply and regenerate lockfile:
chezmoi apply ~/.config/mise/config.toml mise install --yes mise --cd home/dot_config/mise lock - Verify the tool runs. Check the binary name — it may differ from the repo
name (e.g.,
BurntSushi/ripgrepinstallsrg).
Updating a tool
- Check current vs latest:
mise ls gh release view --repo owner/repo --json tagName --jq '.tagName' - Edit the version in
home/dot_config/mise/config.toml - Apply, install, and regenerate lockfile:
chezmoi apply ~/.config/mise/config.toml mise install --yes mise --cd home/dot_config/mise lock
Regenerating lockfiles
There are two lockfiles pinning checksums across 7 platforms (linux-arm64, linux-arm64-musl, linux-x64, linux-x64-musl, macos-arm64, macos-x64, windows-x64). Regenerate both after any config change:
mise lock # project-level (mise.toml)
mise --cd home/dot_config/mise lock # user-level (config.toml)~/.config/mise/mise.lock is a symlink to the user lockfile in this repository, so
there is no deployed copy to keep in step. Anything mise install or mise use
writes to the lockfile, or to the dependency graphs under .mise/locks/, shows up
as a change in the working tree. Commit the graphs with the lockfile; never
reformat them, because the lockfile records a digest of each.
Troubleshooting install failures
"No matching asset found" — The tool doesn't publish binaries matching the expected platform naming. Check available assets:
gh release view --repo owner/repo --json assets --jq '.assets[].name'If assets exist but use unusual naming, the github: backend may not auto-detect
them. Options:
- Install via
cargo:backend if it's a Rust tool - Pull source via
chezmoiexternalwith a wrapper script in~/.local/bin
"No GitHub attestations found" — This was the aqua failure mode. The
github: backend handles missing attestations gracefully — it verifies when
available but doesn't block when absent.
Non-standard release tags — If mise install returns 404, the tag format
likely doesn't match. Check the actual tag:
gh release view --repo owner/repo --json tagName --jq '.tagName'Use the full tag string as the version (e.g., jq-1.8.1 not 1.8.1).
Lockfile conflicts — Delete and regenerate both:
mise lock # project-level
mise --cd home/dot_config/mise lock # user-levelRules
- Edit
home/dot_config/mise/config.toml, never~/.config/mise/config.toml - Pin exact versions for all tools — Renovate handles updates
- Never use
latest— always pin to a specific version - Always regenerate lockfile after config changes
- Always verify the tool runs after installing
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.

