Manage development tool versions, project environments, and task execution with mise.
npx skills add https://github.com/telegraphic-dev/mise-skill --skill mise-telegraphic-dev
Please help me install this Agent Skill. Skill: mise Source: https://github.com/telegraphic-dev/mise-skill Command: npx skills add https://github.com/telegraphic-dev/mise-skill --skill mise-telegraphic-dev
mise.toml, with lockfile support for exact reproducibility. - Safe Agent Execution: Run commands with mise exec and tasks with mise run without mutating the shell, plus guidance on inspecting configs before trusting them. - Environment & Task Workflows: Manage [env] variables, .env loading, and declared project tasks, with troubleshooting for wrong versions, CI failures, and untrusted configs. - Use Case: A repository pins Node 24 and exposes a test task. An agent inspects mise config ls and mise tasks ls, then runs mise run test in CI without activating mise in any shell. ## Quick Start Ask the agent to inspect the repository's mise configuration and run the project's test task using mise exec or mise run.High-intent search queries and answers about installing and using this skill.
Use `mise exec -- <command>` to run a command inside the project's resolved environment, or `mise exec node@24 -- node --version` to select a tool explicitly for one command. This works without shell activation and installs missing declared tools when needed.
First list available tasks with `mise tasks ls` and inspect one with `mise tasks info <name>`. Then run it with `mise run <task>`; tasks inherit mise-managed tools and configured environment variables.
Use `mise exec` or `mise run` in CI and agent sessions; shell activation is only for interactive human shells. Activation mutates shell configuration and is unnecessary for one-shot automation commands.
Compare `mise exec -- node --version` with plain `node --version`. If mise exec is correct but the shell is wrong, activation or PATH ordering is broken; run `mise doctor` and check `mise which node` and `mise ls --current`.
No. A mise config can contain hooks, env files, and tasks with side effects, so read the file and its includes first. Only run `mise trust` after reviewing the config and getting explicit approval.
No. Never commit credentials to `mise.toml`, source-controlled `.env` files, or lockfiles. Use the project's secret store or CI secrets and keep local secret files git-ignored.
BaneeishaqueDetects, installs, and verifies CLI tools across macOS, Linux, and Windows.
taiidaniInstall and manage tool versions with mise configuration files.
4lermanAudit repositories for sensitive data and manage environment variables securely.
MadBomberDetect Ruby version managers and generate activation commands from project files.