How do I install the Install skill?

Run npx skillmds@latest add tomevault-io/install in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Install skill do?

Use when the user asks to install, add, or set up a package, tool, CLI, or application It is listed under Coding & Dev Tools on SkillMD.

Is Install safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Install?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Install free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Install?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Install by tomevault-io — Agent Skill

Name: Install
Author: tomevault-io

File contents

Package Installation Skill

Arguments

$ARGUMENTS: Space-separated package names to install.

Workflow

When to escalate: For complex backend decisions, version conflicts, or security concerns, consult the Package Manager subagent.

For each package in $ARGUMENTS:

1. Identify Package Type

Check in order:

Mise registry:
```
mise registry | grep -i <package>
```
Known GUI/system apps: GUI applications → cask, system utilities → brew

Package type mapping:

Package Type	Format
Aqua registry	`"aqua:owner/repo" = "version"`
GitHub releases	`"github:owner/repo" = "version"`
Python CLI	`"pipx:package" = "version"`
Node.js CLI	`"npm:package" = "version"`
GUI app	Add to casks list
System utility	Add to brews list

2. Discover Latest Version

GitHub tools (aqua/github):

gh release view --repo <owner>/<repo> --json tagName --jq .tagName

npm:

npm view <package> version

PyPI:

pip index versions <package> 2>/dev/null | head -1

Native mise:

mise ls-remote <tool> | tail -1

3. Add to Manifest

Mise tools → home/dot_config/mise/config.toml:

Add under [tools] section
Use backend prefix
Pin exact version
Follow comment organization (Runtimes, Aqua, GitHub, Python, Node)

Homebrew → home/.chezmoidata/packages.yaml:

Add to packages.darwin.brews or packages.darwin.casks
Follow alphabetical order

4. Verify

chezmoi diff

Expected: Only the intended manifest file changed. If unrelated changes appear, investigate.

5. Apply

Requires user approval:

chezmoi apply

CRITICAL: Always run chezmoi apply with no arguments. This triggers run_onchange_00-install-mise-tools.sh.tmpl which runs mise install. Targeted apply (chezmoi apply <file>) skips this script.

If the diff shows unrelated changes, ask the user how to proceed - do NOT attempt a partial apply.

6. Commit

git add <manifest-file>
git commit -m "feat: add <package-name>"

After all packages: Ask user "All packages installed and committed. Push to origin?"

Rules

Mise > Homebrew for dev tools; aqua > other mise backends
Exact versions only (no latest, ranges, wildcards)
One commit per package
Edit source files in home/ only

Reference

See docs/package-management.md for complete backend documentation.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: installdescription: Use when the user asks to install, add, or set up a package, tool, CLI, or application---# Package Installation Skill## Arguments`$ARGUMENTS`: Space-separated package names to install.## Workflow**When to escalate:** For complex backend decisions, version conflicts, or security concerns, consult the Package Manager subagent.For each package in `$ARGUMENTS`:### 1. Identify Package TypeCheck in order:1. **Mise registry:** ```bash mise registry | grep -i <package> ```2. **Known GUI/system apps:** GUI applications → cask, system utilities → brew**Package type mapping:**| Package Type | Format ||-------------|---------|| Aqua registry | `"aqua:owner/repo" = "version"` || GitHub releases | `"github:owner/repo" = "version"` || Python CLI | `"pipx:package" = "version"` || Node.js CLI | `"npm:package" = "version"` || GUI app | Add to casks list || System utility | Add to brews list |### 2. Discover Latest Version**GitHub tools (aqua/github):**```bashgh release view --repo <owner>/<repo> --json tagName --jq .tagName```**npm:**```bashnpm view <package> version```**PyPI:**```bashpip index versions <package> 2>/dev/null | head -1```**Native mise:**```bashmise ls-remote <tool> | tail -1```### 3. Add to Manifest**Mise tools** → `home/dot_config/mise/config.toml`:- Add under `[tools]` section- Use backend prefix- Pin exact version- Follow comment organization (Runtimes, Aqua, GitHub, Python, Node)**Homebrew** → `home/.chezmoidata/packages.yaml`:- Add to `packages.darwin.brews` or `packages.darwin.casks`- Follow alphabetical order### 4. Verify```bashchezmoi diff```Expected: Only the intended manifest file changed. If unrelated changes appear, investigate.### 5. Apply**Requires user approval:**```bashchezmoi apply```**CRITICAL:** Always run `chezmoi apply` with no arguments. This triggers `run_onchange_00-install-mise-tools.sh.tmpl` which runs `mise install`. Targeted apply (`chezmoi apply <file>`) skips this script.If the diff shows unrelated changes, ask the user how to proceed - do NOT attempt a partial apply.### 6. Commit```bashgit add <manifest-file>git commit -m "feat: add <package-name>"```---After all packages: Ask user "All packages installed and committed. Push to origin?"## Rules- Mise > Homebrew for dev tools; aqua > other mise backends- Exact versions only (no `latest`, ranges, wildcards)- One commit per package- Edit source files in `home/` only## ReferenceSee `docs/package-management.md` for complete backend documentation.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/ivy) — claim your Tome and manage your conversions.

Frequently asked questions

Install