mise
Mise (formerly rtx) polyglot tool version manager, environment variable manager, and task runner. Covers tool version management (install, use, pin across Node/Python/Rust/Go/Java and more), mise.toml task definitions (scripts, dependencies, watch mode, incremental builds), environment variable management (.env integration, per-directory env, redaction), project-level tool pinning, backend system (asdf, npm, pipx, cargo, GitHub releases), and comparison with alternatives (asdf, nvm, pyenv, Makefiles). Use when configuring development tool versions, defining project tasks in mise.toml, managing per-project environment variables, setting up polyglot dev environments, migrating from asdf or nvm, or automating build/test/lint/deploy workflows with mise run.
What this skill does
# Mise ## Overview Mise is a **polyglot development tool manager** that handles tool versions, environment variables, and task running in a single CLI. It replaces asdf, nvm, pyenv, direnv, and Makefiles with a unified `mise.toml` configuration per project. **When to use:** Managing multiple language runtimes per project, defining reproducible dev environments, running project tasks with dependencies, replacing scattered `.nvmrc`/`.python-version`/`.tool-versions` files, automating CI pipelines. **When NOT to use:** Container-only workflows where all tools live in Docker images, single-language projects already well-served by their native version manager, production runtime management (mise is a dev tool). ## Version Resolution Order Mise resolves tool versions by checking these sources in priority order: 1. `MISE_<TOOL>_VERSION` environment variable 2. `mise.toml` in current directory 3. `mise.toml` in parent directories (walks up the tree) 4. `.tool-versions` file (asdf compatibility) 5. Legacy files (`.nvmrc`, `.python-version`, `.ruby-version`) 6. `~/.config/mise/config.toml` (global default) ## Quick Reference | Pattern | Command / Config | Key Points | | --------------------- | ---------------------------------------- | ------------------------------------------- | | Install tools | `mise install` | Reads mise.toml, installs all listed tools | | Pin tool version | `mise use node@22` | Writes to mise.toml in current directory | | Pin globally | `mise use -g node@22` | Writes to ~/.config/mise/config.toml | | Run a task | `mise run build` | Runs task defined in mise.toml | | Run with args | `mise run test -- --watch` | Passes args after `--` to the task | | Watch mode | `mise watch build` | Re-runs task when sources change | | List tasks | `mise tasks` | Shows all available tasks | | Set env vars | `[env]` section in mise.toml | Per-directory, auto-activated on cd | | Load .env file | `_.file = ".env"` | Loads dotenv into environment | | Extend PATH | `_.path = ["./bin"]` | Prepends directories to PATH | | List installed | `mise ls` | Shows all installed tool versions | | Outdated tools | `mise outdated` | Shows tools with newer versions | | Upgrade tools | `mise upgrade` | Upgrades tools to latest within constraints | | Trust config | `mise trust` | Trusts mise.toml in current directory | | Tool backends | `"npm:prettier"` / `"cargo:cargo-watch"` | Install from npm, cargo, pipx, GitHub, etc. | | Task dependencies | `depends = ["lint", "test"]` | Prerequisite tasks run first | | Incremental build | `sources` + `outputs` on task | Skips task if outputs newer than sources | | Exec without activate | `mise exec -- node app.js` | Runs command with mise-managed tools | | Diagnostics | `mise doctor` | Check installation and config health | | Prune unused | `mise prune` | Remove tool versions not in any config | | Generate hook | `mise generate git-pre-commit` | Generate git pre-commit hook for tasks | | Env-specific config | `.mise.staging.toml` | Activated via `MISE_ENV=staging` | | Shims for IDEs | `mise settings set shims_on_path true` | PATH-based shims for IDE compatibility | ## Common Mistakes | Mistake | Correct Pattern | | ------------------------------------------------ | -------------------------------------------------------------------- | | Using `mise install node@22` without `mise use` | `mise use node@22` both installs and pins to mise.toml | | Editing `.tool-versions` manually with mise | Use `mise use` to update; mise.toml is preferred over .tool-versions | | Forgetting `mise trust` on new project clone | Run `mise trust` to activate untrusted config files | | Using `depends` key for task dependencies | Current key is `depends` (array), not `deps` | | Running `mise run` without activating mise | Run `mise activate` in shell profile or use `mise exec` | | Putting secrets directly in mise.toml | Use `_.file = ".env.local"` and gitignore the .env file | | Expecting env vars without `cd`-ing into project | Mise activates env on directory change; use `mise env` to debug | | Using `latest` version in shared projects | Pin specific major versions (`node = "22"`) for reproducibility | | Defining tasks in Makefile alongside mise | Consolidate all tasks in mise.toml for one tool | | Missing shebang in multi-line task scripts | Add `#!/usr/bin/env bash` for explicit interpreter | | Not using `sources`/`outputs` for slow tasks | Define source globs for incremental skipping and watch mode | | Using `mise activate` in non-interactive scripts | Use `mise exec` or `eval "$(mise env)"` in scripts and CI | ## Delegation - **Task pattern discovery**: Use `Explore` agent - **Configuration review**: Use `Task` agent - **CI pipeline integration**: Use `Task` agent > If the `rust` skill is available, delegate Rust toolchain management patterns to it. > If the `python-uv` skill is available, delegate Python version and virtual environment patterns to it. > If the `github-actions` skill is available, delegate CI workflow patterns to it. > If the `docker` skill is available, delegate containerized workflow patterns to it. > If the `pino-logging` skill is available, delegate logging configuration patterns to it. > If the `sentry` skill is available, delegate error monitoring setup patterns to it. ## References - [Tool version management and backends](references/tool-management.md) - [Task definitions, dependencies, and scripts](references/task-runner.md) - [Environment variables and dotenv integration](references/environment-variables.md) - [Configuration files and settings](references/configuration.md) - [Common task patterns for projects](references/task-patterns.md) - [Migration from asdf, nvm, and alternatives](references/migration.md)
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.