Source profileQuality 92/100Review permissions

laurigates/claude-plugins/configure-plugin/skills/configure-mise/SKILL.md

configure-mise

mise runtime/tool version manager - mise.toml, backends (pipx/aqua/npm/cargo/go), tasks, env, lockfile. Use when setting up, pinning runtimes/CLI tools, or migrating from asdf/nvm/pyenv/brew/Make.

Source repository stars
54
Declared platforms
0
Static risk flags
3
Last source update
2026-08-28
Source checked
2026-08-28

Decision brief

What it does: where it fits

Set up and audit mise as the unified manager for language runtimes, CLI tools, environment variables, and project tasks. mise replaces asdf/nvm/pyenv (runtimes), cargo install/brew install (CLI binaries), and Make/just (tasks) behind one mise.toml.

Best for

  • Use when setting up, pinning runtimes/CLI tools, or migrating from asdf/nvm/pyenv/brew/Make.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/laurigates/claude-plugins --skill "configure-plugin/skills/configure-mise"
Safe inspection promptEditorial

Inspect the Agent Skill "configure-mise" from https://github.com/laurigates/claude-plugins/blob/c056e44b978db58648ad20440dc1515cb09af09d/configure-plugin/skills/configure-mise/SKILL.md at commit c056e44b978db58648ad20440dc1515cb09af09d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Step 1: Detect current state

    From Context, classify the repo:

    No mise, has legacy version files (.tool-versions, .nvmrc, .python-version) → migration candidate.No mise, has Makefile/Brewfile → task/tool migration candidate.Has mise.toml → audit mode (Step 5).
  2. 02

    Step 2: Choose config target and naming

    Prefer the modern mise.toml name over legacy .mise.toml. Use mise.local.toml for machine-specific or secret-bearing overrides and ensure it is gitignored.

    Prefer the modern mise.toml name over legacy .mise.toml. Use mise.local.toml for machine-specific or secret-bearing overrides and ensure it is gitignored.
  3. 03

    Step 3: Build the [tools] block

    Pin runtimes the project needs, then add CLI tools by backend (table above). Pin as loosely as safe: python = "3.13" (allow patch upgrades) for libraries; exact pins (opentofu = "1.11.2") for tools where reproducibility matters. Detect latest stable versions with WebSearch/mise…

    Pin runtimes the project needs, then add CLI tools by backend (table above). Pin as loosely as safe: python = "3.13" (allow patch upgrades) for libraries; exact pins (opentofu = "1.11.2") for tools where reproducibility…
  4. 04

    Step 4: Add [env], [tasks], [settings] as needed

    [env] — project env vars and PATH; load secrets from a gitignored file with .file = ".env.local" (never inline secrets). See REFERENCE.md.

    [env] — project env vars and PATH; load secrets from a gitignored file with .file = ".env.local" (never inline secrets). See REFERENCE.md.[tasks] — migrate Makefile/just recipes here so mise run replaces make . Supports depends, alias, multi-line run. See REFERENCE.md for the full grammar.[settings] — set pipx.uvx = true whenever any pipx: tool is present (works around jdx/mise7477); experimental = true for newer backends; legacyversionfile = true to keep honoring .tool-versions/.nvmrc during migration.
  5. 05

    Step 5: Audit (always; the whole job when --check-only)

    Report a compliance table:

    Report a compliance table:Checks: every runtime pinned; CLI tools prefer aqua: over cargo:/source builds; pipx.uvx = true present if any pipx: tool; mise.lock committed; mise.local.toml gitignored if present; config trusted (mise trust). If --ch…

Permission review

Static risk signals and limitations

Reads files

low · line 90

The documentation asks the agent to read local files, directories, or repositories.

**`[env]`** — project env vars and PATH; load secrets from a gitignored file with `_.file = ".env.local"` (never inline secrets). See REFERENCE.md.

Runs scripts

medium · line 104

The documentation asks the agent to run terminal commands or scripts.

pipx.uvx setting true [SET | MISSING (pipx tools present)]

Writes files

medium · line 117

The documentation asks the agent to create, modify, or delete local files.

Write/patch the target config (Step 2 file).

Reads files

low · line 184

The documentation asks the agent to read local files, directories, or repositories.

**Untrusted config**: mise refuses to load an untrusted file — run `mise trust` after writing.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score92/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars54SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
laurigates/claude-plugins
Skill path
configure-plugin/skills/configure-mise/SKILL.md
Commit
c056e44b978db58648ad20440dc1515cb09af09d
License
MIT
Collected
2026-08-28
Default branch
main
View the original SKILL.md

/configure:mise

Set up and audit mise as the unified manager for language runtimes, CLI tools, environment variables, and project tasks. mise replaces asdf/nvm/pyenv (runtimes), cargo install/brew install (CLI binaries), and Make/just (tasks) behind one mise.toml.

When to Use This Skill

Use this skill when...Use another approach when...
Setting up mise.toml to pin a project's runtimes and CLI toolsInstalling one tool ad-hoc — run mise use <tool>@<ver> directly
Picking the right backend for a tool (core / pipx: / aqua: / npm: / cargo: / go:)The project only needs Python/JS libraries — use /configure:package-management (uv/bun)
Migrating from .tool-versions/asdf, .nvmrc, .python-version, Homebrew, or a MakefileDefining build/test recipes only, no version management — use /configure:justfile or /configure:makefile
Adding [tasks], [env], secret loading, or a mise.lock for reproducible installsRunning a specific runtime version once — mise exec <tool>@<ver> -- <cmd> (see global rule mise-stale-tool-copies / dependency-management)
Auditing an existing mise setup for pinning, lockfile, trust, and backend correctnessConfiguring CI runtime install — that consumes the mise.toml this skill produces (jdx/mise-action)

Context

  • Project root: !pwd
  • mise config (project): !find . -maxdepth 2 \( -name 'mise.toml' -o -name '.mise.toml' -o -path './.config/mise.toml' -o -name 'mise.local.toml' \)
  • Lockfile: !find . -maxdepth 1 -name 'mise.lock'
  • Legacy version files: !find . -maxdepth 2 \( -name '.tool-versions' -o -name '.nvmrc' -o -name '.python-version' -o -name '.ruby-version' -o -name '.go-version' \)
  • Things mise can absorb: !find . -maxdepth 1 \( -name 'Makefile' -o -name 'justfile' -o -name 'Brewfile' \)

Parameters

Parse from command arguments:

  • --check-only: Audit and report; make no changes (CI/review mode).
  • --fix: Apply the recommended config without prompting for each step.
  • --global: Target the global config (~/.config/mise/config.toml) instead of a project mise.toml.
  • --migrate <source>: Convert an existing setup into mise.toml. Sources: asdf (.tool-versions), nvm (.nvmrc), pyenv (.python-version), brew (Brewfile CLI tools), makefile (targets → [tasks]).

Backend Selection (the core decision)

mise installs every tool through a backend. Picking the right one mirrors the user's tool-install priority (dependency-management rule): mise first, with the most secure/fastest backend.

Tool kindBackendSyntaxWhy
Language runtimecorepython = ["3.12","3.13"], node = "lts", go = "1.23", rust = "latest"Native version switching, the reason mise exists
Python CLI toolpipx:"pipx:ruff" = "latest"Routed through uvx (fast); set pipx.uvx = true
Standalone CLI binaryaqua:"aqua:BurntSushi/ripgrep" = "latest"Checksums + SLSA provenance + Cosign — the secure default
Node globalnpm:"npm:typescript-language-server" = "latest"When no aqua entry exists
Rust tool (no aqua)cargo:"cargo:tokei" = "latest"Builds from source; prefer aqua if available
Go tool (no aqua)go:"go:golang.org/x/tools/gopls" = "latest"Installs via go install
GitHub release (no aqua)github:"github:starship/starship" = "latest"Direct release-asset fetch

Rule of thumb: runtime → core; Python CLI → pipx:; everything else → aqua: first, falling back to npm:/cargo:/go:/github: only when the aqua registry lacks the tool. Verify aqua availability at https://github.com/aquaproj/aqua-registry.

Execution

Step 1: Detect current state

From Context, classify the repo:

  • No mise, has legacy version files (.tool-versions, .nvmrc, .python-version) → migration candidate.
  • No mise, has Makefile/Brewfile → task/tool migration candidate.
  • Has mise.toml → audit mode (Step 5).
  • Greenfield → fresh mise.toml.

Detect which runtimes the project already implies: pyproject.toml/.python-version → Python; package.json/.nvmrc → Node; go.mod → Go; Cargo.toml → Rust.

Step 2: Choose config target and naming

TargetFileCommitted?
Project (default)mise.toml at repo rootyes — pins the team to the same versions
Project, local overridesmise.local.tomlno — add to .gitignore
Global (--global)~/.config/mise/config.tomln/a (dotfiles)

Prefer the modern mise.toml name over legacy .mise.toml. Use mise.local.toml for machine-specific or secret-bearing overrides and ensure it is gitignored.

Step 3: Build the [tools] block

Pin runtimes the project needs, then add CLI tools by backend (table above). Pin as loosely as safe: python = "3.13" (allow patch upgrades) for libraries; exact pins (opentofu = "1.11.2") for tools where reproducibility matters. Detect latest stable versions with WebSearch/mise ls-remote <tool> before writing.

Minimal example:

[tools]
python = "3.13"
node = "lts"
"pipx:ruff" = "latest"
"pipx:pre-commit" = "latest"
"aqua:jqlang/jq" = "latest"
"aqua:cli/cli" = "latest"   # gh

Step 4: Add [env], [tasks], [settings] as needed

  • [env] — project env vars and PATH; load secrets from a gitignored file with _.file = ".env.local" (never inline secrets). See REFERENCE.md.
  • [tasks] — migrate Makefile/just recipes here so mise run <task> replaces make <target>. Supports depends, alias, multi-line run. See REFERENCE.md for the full grammar.
  • [settings] — set pipx.uvx = true whenever any pipx: tool is present (works around jdx/mise#7477); experimental = true for newer backends; legacy_version_file = true to keep honoring .tool-versions/.nvmrc during migration.

Step 5: Audit (always; the whole job when --check-only)

Report a compliance table:

mise Configuration Report
=========================
Config file            mise.toml                 [PRESENT | MISSING]
Runtimes pinned        python, node              [PINNED | UNPINNED]
CLI backends           aqua / pipx               [SECURE | cargo-from-source | mixed]
pipx.uvx setting       true                      [SET | MISSING (pipx tools present)]
Lockfile               mise.lock                 [COMMITTED | MISSING]
Local overrides        mise.local.toml           [GITIGNORED | TRACKED ⚠ | n/a]
Trust                  trusted                    [TRUSTED | UNTRUSTED]
Legacy files remaining .tool-versions            [MIGRATED | STILL PRESENT]

Overall: [N issues]

Checks: every runtime pinned; CLI tools prefer aqua: over cargo:/source builds; pipx.uvx = true present if any pipx: tool; mise.lock committed; mise.local.toml gitignored if present; config trusted (mise trust). If --check-only, stop here.

Step 6: Apply (with --fix or on confirmation)

  1. Write/patch the target config (Step 2 file).
  2. mise trust the config (required before mise will use a new/edited file).
  3. mise install to materialize tools.
  4. mise lock to generate/refresh mise.lock, then track it (git add mise.lock).
  5. If mise.local.toml exists, ensure .gitignore covers it.
  6. mise doctor to verify the setup is healthy.

Step 7: Migrations (--migrate <source>)

SourceAction
asdfRead .tool-versions, map each line to a [tools] entry, keep legacy_version_file = true, then remove .tool-versions once verified. asdf plugin names usually match mise core/aqua names.
nvm.nvmrcnode = "<ver>".
pyenv.python-versionpython = "<ver>" (a list if multiple).
brewMove CLI tools (not casks/services/build-deps) from Brewfile to aqua:/core backends; leave GUI apps, fonts, daemons, and compilers in Homebrew.
makefileConvert each target to a [tasks.<name>] with run; map prerequisites to depends. See REFERENCE.md task grammar.

Always verify with mise install && mise doctor before deleting the source file. See REFERENCE.md for per-source mapping tables and worked examples.

Step 8: CI integration (mention, don't duplicate)

A committed mise.toml + mise.lock is consumed in CI by jdx/mise-action (mise install then mise run <task>), giving local↔CI parity (the local-ci-parity rule). Point the user to /configure:ci-workflows rather than writing the workflow here.

Agentic Optimizations

ContextCommand
Audit only/configure:mise --check-only
Auto-configure/configure:mise --fix
List installed tools (JSON)mise ls --json
Show active versionsmise current
Available versions of a toolmise ls-remote <tool>
Show outdatedmise outdated
Diagnosemise doctor
Generate lockfilemise lock

Flags

FlagDescription
--check-onlyReport status without modifying files
--fixApply the recommended config without per-step prompts
--globalTarget ~/.config/mise/config.toml instead of project mise.toml
--migrate <source>Convert asdf/nvm/pyenv/brew/makefile into mise.toml

Examples

# Audit an existing setup
/configure:mise --check-only

# Set up mise.toml for the current project
/configure:mise

# Auto-configure, no prompts
/configure:mise --fix

# Migrate an asdf project
/configure:mise --migrate asdf

# Convert Makefile targets into mise tasks
/configure:mise --migrate makefile

Error Handling

  • mise not installed: Offer the install one-liner (curl https://mise.run | sh) or note it is itself a Homebrew bootstrap tool; do not block the audit.
  • Untrusted config: mise refuses to load an untrusted file — run mise trust after writing.
  • pipx: tool fails to resolve: ensure uv is a mise-managed tool and pipx.uvx = true is set (jdx/mise#7477).
  • aqua package not found: the org/repo name must match an aqua-registry entry; fall back to github:/cargo:/go: or core.
  • Tool "keeps coming back" after removal: stale per-node-version copies + ~/.default-npm-packages re-seeding — see the global mise-stale-tool-copies rule.
  • node ≥26 on minimal Linux: prebuilt binaries link libatomic.so.1; gate node to platforms that have it (chezmoi-style os guard) or pin an older line.

See Also

  • /configure:package-management — uv/bun for Python/JS libraries (mise installs the runtimes; uv/bun manage deps)
  • /configure:justfile, /configure:makefile — task runners mise's [tasks] can replace
  • /configure:ci-workflows — CI that consumes mise.toml via jdx/mise-action
  • Global rules: dependency-management (tool-install priority, mise exec vs mise use), mise-stale-tool-copies (per-version cleanup)
  • REFERENCE.md — full [tasks]/[env]/[settings] grammar, backend cheat-sheet, migration mapping tables
  • mise docs: https://mise.jdx.dev/ · aqua registry: https://github.com/aquaproj/aqua-registry

Frequently asked questions

What to verify before installation and use

What does the configure-mise source document cover?

Set up and audit mise as the unified manager for language runtimes, CLI tools, environment variables, and project tasks. mise replaces asdf/nvm/pyenv (runtimes), cargo install/brew install (CLI binaries), and Make/just (tasks) behind one mise.toml.

How do I install configure-mise?

The source record exposes this install command: npx skills add https://github.com/laurigates/claude-plugins --skill "configure-plugin/skills/configure-mise". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged read-files, exec-script, write-files in the source; the page lists the matching lines and excerpts.

Alternatives

Compare before choosing

Computed 10045,960

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 10029,236

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

Computed 10025,136

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 1005,277

dotnet/skills

migrate-vstest-to-mtp

Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing