install-batch

name	install-batch
description	Install every plugin in a named batch from favorite-plugins-installers — adds any required marketplaces first, then runs `claude plugins install` for each plugin. Use when the user says "install the X batch", "set up my Y plugins", or names a batch defined in this plugin.

Install Batch

Install all plugins listed in one batch JSON file.

Inputs

• batch_name (required): filename stem under batches/ (e.g. dev-essentials for batches/dev-essentials.json).
• --scope user|project (optional, default user): scope to install plugins at. Project scope only works when invoked from inside a repo.

Steps

1. Resolve ${CLAUDE_PLUGIN_ROOT}/batches/<batch_name>.json. If missing, list available batches and stop.
2. Load the JSON. Show the user the batch description and the full list of plugins (with why notes) that will be installed. Wait for confirmation only if the batch has more than 5 plugins or pulls in marketplaces not yet added on this machine; otherwise proceed.
3. For each entry in marketplaces[], run:

   claude plugins marketplace add <owner>/<repo>
   

   Skip silently if the marketplace is already added (the CLI returns non-zero — check the error message rather than failing the whole batch).
4. Refresh marketplace caches:

   claude plugins marketplace update <owner>
   

   for each unique owner referenced.
5. For each entry in plugins[], run:

   claude plugins install <plugin-name>@<marketplace> [--scope project]
   

   Continue on individual failure — collect failures and report them at the end.
6. Print a summary: installed N, skipped (already present) M, failed K with reasons.

Notes

• Never write to ~/.claude/plugins/<this-plugin>/ — batches are read-only repo content.
• If the user wants to add a new batch, point them at the add-batch skill.