How do I install the Add Package skill?

Run npx skillmds@latest add nwiizo/add-package 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.

Is Add Package safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add Package?

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 Add Package free to use?

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

Who published Add Package?

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

Add Package by nwiizo — Agent Skill

Name: Add Package
Author: nwiizo

Add Package

Add a package to this macOS dotfiles repo. Use when the user asks to install, add, or migrate a CLI package or GUI app, for example "add jq", "ripgrep を入れて", "lazygit 入れたい", "brew install foo を repo 管理に", "kubectl 追加して". Homebrew owns binaries here; update Brewfile, validate with brew bundle, apply with brew bundle, and verify the executable.

nwiizo bd29aa3 2.6 KB Updated Sep 17, 2026

File contents

add-package

Add packages through Homebrew. This repo's package management is the top-level Brewfile.

Decision Flow

Identify the package name and whether it is a formula, cask, or non-brew package.
Check Homebrew availability:

brew search <name>
brew info <name>

Edit Brewfile:
- CLI tools: brew "<formula>"
- GUI apps: cask "<cask>"
- Keep existing grouping and simple alphabetical order where practical.
- Keep package changes in Brewfile.
- If a repo config, validation command, or agent rule requires the binary, keep the Homebrew-owned package explicit even when it is already installed transitively or outside the Brewfile.
Check installed dependencies before applying:

brew bundle check --file Brewfile

If the check reports the newly requested package as missing, continue with its authorized installation. Distinguish that expected result from an invalid Brewfile or an unrelated dependency problem.

Apply:

brew bundle --file Brewfile

Verify:

command -v <binary>
<binary> --version
brew bundle check --file Brewfile

For casks, verify with brew list --cask <name> or by checking the app exists in /Applications.

Non-Homebrew Packages

Use non-brew installation only when Homebrew is unavailable or inappropriate, for example npm-only ACP adapters. In that case:

Install with the native package manager, e.g. npm install -g <package>.
Verify the exposed command with command -v.
State that it is not tracked by Brewfile unless a Homebrew formula/cask exists.

Validation

The install and verification results above cover package-only changes; do not run brew bundle again just to complete this section. If shell integration also changes, use the affected Fish checks in add-config.

Don't

Do not create unrelated package management files.
Do not run brew uninstall unless the user explicitly asks.
Do not use brew cleanup or uninstall unrelated local packages merely to make the machine match the Brewfile; report that drift separately.
Do not add a package twice under different names.
Do not edit generated target files under ~/.config; edit repo sources.
Do not reformat unrelated parts of Brewfile.

---name: add-packagedescription: Add a package to this macOS dotfiles repo. Use when the user asks to install, add, or migrate a CLI package or GUI app, for example "add jq", "ripgrep を入れて", "lazygit 入れたい", "brew install foo を repo 管理に", "kubectl 追加して". Homebrew owns binaries here; update Brewfile, validate with brew bundle, apply with brew bundle, and verify the executable.---# add-packageAdd packages through Homebrew. This repo's package management is the top-level`Brewfile`.## Decision Flow1. Identify the package name and whether it is a formula, cask, or non-brew package.2. Check Homebrew availability:```bashbrew search <name>brew info <name>```3. Edit `Brewfile`: - CLI tools: `brew "<formula>"` - GUI apps: `cask "<cask>"` - Keep existing grouping and simple alphabetical order where practical. - Keep package changes in `Brewfile`. - If a repo config, validation command, or agent rule requires the binary, keep the Homebrew-owned package explicit even when it is already installed transitively or outside the Brewfile.4. Check installed dependencies before applying:```bashbrew bundle check --file Brewfile```If the check reports the newly requested package as missing, continue with itsauthorized installation. Distinguish that expected result from an invalidBrewfile or an unrelated dependency problem.5. Apply:```bashbrew bundle --file Brewfile```6. Verify:```bashcommand -v <binary><binary> --versionbrew bundle check --file Brewfile```For casks, verify with `brew list --cask <name>` or by checking the appexists in `/Applications`.## Non-Homebrew PackagesUse non-brew installation only when Homebrew is unavailable or inappropriate,for example npm-only ACP adapters. In that case:- Install with the native package manager, e.g. `npm install -g <package>`.- Verify the exposed command with `command -v`.- State that it is not tracked by `Brewfile` unless a Homebrew formula/cask exists.## ValidationThe install and verification results above cover package-only changes; do notrun `brew bundle` again just to complete this section. If shell integrationalso changes, use the affected Fish checks in `add-config`.## Don't- Do not create unrelated package management files.- Do not run `brew uninstall` unless the user explicitly asks.- Do not use `brew cleanup` or uninstall unrelated local packages merely to make the machine match the Brewfile; report that drift separately.- Do not add a package twice under different names.- Do not edit generated target files under `~/.config`; edit repo sources.- Do not reformat unrelated parts of `Brewfile`.

Frequently asked questions