add-batch

name	add-batch
description	Define a new curated batch of third-party Claude plugins and write it as a JSON file under batches/. Use when the user says "add a new batch", "I want to bundle these plugins", or proposes a new theme grouping.

Add Batch

Create a new batch definition file in this plugin's batches/ directory.

Inputs to gather

1. Batch name — kebab-case, becomes the filename stem (e.g. dev-essentials → batches/dev-essentials.json).
2. Description — one sentence on what this batch is for / when the user would install it.
3. Plugins — list of { name, marketplace, why? } entries. marketplace is the GitHub owner the plugin is published under.
4. Marketplaces to add — derived automatically from the unique marketplace values; for each, prompt the user for the marketplace repo name (e.g. owner=somebody, repo=Their-Plugins) so the JSON can include the marketplaces[] block.

Steps

1. Validate the batch name doesn't already exist as a file under batches/.
2. Write the JSON to ${CLAUDE_PLUGIN_ROOT}/batches/<batch_name>.json matching the schema in batches/README.md.
3. Validate with python3 -c "import json; json.load(open('<path>'))".
4. Tell the user the new batch is ready and remind them: this file lives inside the plugin repo, so to share the batch with others they should commit and push to Claude-Favorite-Plugins-Installers-Plugin (and bump the plugin version via publish-plugin-update).

Notes

• Local-only batches (private to this user, not for sharing): write to ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/favorite-plugins-installers/batches/<name>.json instead, and teach list-batches / install-batch to read from both locations. Default to repo-shipped batches unless the user specifies "private" or "local-only".