Menu
Installs tools on your environment such as java, npm, node, terraform, go,. Use when installing a new tool, updating an existing one or uninstalling one.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
An example custom skill.
An example custom skill version for demonstration.
Reviews the work just done and updates CLAUDE.md, agent memories, and subagent MD files to reflect any new conventions, packages, resources, or patterns discovered. Run after completing any significant implementation task.
Plans and scaffolds Anthropic API endpoints as Terraform resources/data sources without a task management tool. TRIGGER when: user says "implement GitHub issues", references a range of GitHub issues to implement (e.g. "issues 52 to 57"), asks to parallelize implementation of multiple resources/data sources, or says "implement all [API name] APIs" or "work on a new API" (e.g. /v1/skills, /v1/environments). Generates GitHub issues and branches if they to not already exist — one per resource/data source — ready for sequential or parallel implementation.
Plans and scaffolds Anthropic API endpoints as Terraform resources/data sources for Vibe Kanban. TRIGGER when: user says "implement GitHub issues", references a range of GitHub issues to implement (e.g. "issues 52 to 57"), asks to parallelize implementation of multiple resources/data sources, or says "implement all [API name] APIs". Creates Vibe Kanban issues, workspaces, and fires parallel agents — one per resource/data source.
Updates the GitHub PR description for the current branch based on the work done in the current Claude session. Use after any meaningful change to a PR (feature, fix, refactor, docs). Invoked automatically when Claude stops if an open PR exists for the current branch. Also works inside Vibe Kanban worktrees (vk/* branches) by resolving the PR via the VK issue context.
| name | install-tools |
| description | Installs tools on your environment such as java, npm, node, terraform, go,. Use when installing a new tool, updating an existing one or uninstalling one. |
| model | sonnet |
Installing mise:
curl https://mise.run | sh
By default, mise installs to ~/.local/bin, but it can go anywhere.
Verify the installation:
~/.local/bin/mise --version
# mise 2024.x.x
~/.local/bin does not need to be in PATH. mise will automatically add its own directory to PATH when activated.
Hook mise into your shell (pick the right one for your shell):
# note this assumes mise is located at ~/.local/bin/mise
# which is what https://mise.run does by default
echo 'eval "$(~/.local/bin/mise activate bash)"' >> ~/.bashrc
echo 'eval "$(~/.local/bin/mise activate zsh)"' >> ~/.zshrc
echo '~/.local/bin/mise activate fish | source' >> ~/.config/fish/config.fish
echo '~/.local/bin/mise activate pwsh | Out-String | Invoke-Expression' >> ~/.config/powershell/Microsoft.PowerShell_profile.ps1
$ mise exec node@24 -- node -v
mise node@24.x.x ✓ installed
v24.x.x
Always pin tools to exact versions in mise.toml to prevent unexpected upgrades. Never use major-only ("1") or minor-only ("1.26") constraints:
# Correct — exact version, no surprises
[tools]
go = "1.26.2"
terraform = "1.14.8"
# Wrong — allows patch or minor upgrades
[tools]
go = "1.26"
terraform = "1"
To find the currently installed version before pinning:
mise ls --current
$ mise use --global node@24 go@1
$ node -v
v24.x.x
$ go version
go version go1.x.x macos/arm64
See dev tools for more examples.
# mise.toml
[env]
SOME_VAR = "foo"
$ mise set SOME_VAR=bar
$ echo $SOME_VAR
bar
Note that mise can also load .env files.
# mise.toml
[tasks.build]
description = "build the project"
run = "echo building..."
$ mise run build
building...
See tasks for more information.