From favorite-plugins-installers
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.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin favorite-plugins-installersThis skill uses the workspace's default tool permissions.
Install all plugins listed in one batch JSON file.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Install all plugins listed in one batch JSON file.
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.${CLAUDE_PLUGIN_ROOT}/batches/<batch_name>.json. If missing, list available batches and stop.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.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).claude plugins marketplace update <owner>
for each unique owner referenced.plugins[], run:
claude plugins install <plugin-name>@<marketplace> [--scope project]
Continue on individual failure — collect failures and report them at the end.~/.claude/plugins/<this-plugin>/ — batches are read-only repo content.add-batch skill.