Plugins

Plugin bundles are the install unit for RBA's agentic tooling. Install a bundle and you get every artifact it ships — skills, agents, MCP servers, hooks, slash commands, resources — wired up in Claude Code in a single command.

Install

Plugins run on top of Claude Code, which is available everywhere Claude is: the terminal CLI, the desktop app on Mac and Windows, the web app at claude.ai/code, and the IDE extensions for VS Code and JetBrains. The slash commands below work identically on every surface.

Slash commands (any Claude Code surface)

Inside Claude Code — whether you're in the terminal, the desktop app, the web app at claude.ai/code, or an IDE extension — run these two commands. Add the marketplace once; then install any plugin by name.

1. Add the RBA Skills marketplace (one-time, per machine):

   /plugin marketplace add rbaconsulting/rba-skills-plugin

2. Install any plugin by name:

   /plugin install <plugin-name>@rba-ai-hub

3. Activate it without restarting:

   /reload-plugins

Plugin manager UI

Prefer to browse and click? Claude Code ships an interactive plugin manager. It looks the same in the desktop app, web app, terminal, and IDE extensions.

1. Open the plugin manager:

   /plugin

2. Press Tab to switch to the Marketplaces tab, choose Add, and enter rbaconsulting/rba-skills-plugin.
3. Press Tab again to reach Discover. Filter by name, press Enter on a plugin, and pick an install scope (User for yourself across every project, Project to share with collaborators, or Local for this repo only).
4. Run /reload-plugins to activate it.

Shell (terminal only)

If you have the Claude Code CLI installed and prefer to drive it from a regular shell prompt rather than from inside a Claude Code session:

$ claude plugin marketplace add rbaconsulting/rba-skills-plugin
$ claude plugin install <plugin-name>@rba-ai-hub

Next time you launch Claude Code, the plugin is loaded.

Don't have Claude Code yet?

The desktop apps for Mac and Windows are available at claude.com/download, and the web app is at claude.ai/code. For the terminal CLI, see code.claude.com/docs/en/setup.

How plugins are described

Plugins aren't sorted into a single hierarchy — they're described by multiple optional facets so you can find one by whatever axis matters to your work:

• Platform — vendor- or product-specific bundles (Sitecore, Umbraco, Optimizely, Azure).
• Discipline — how a specific role works day-to-day (frontend, backend, design, accessibility, BA, PM).
• Outcome — shaped by a deliverable or measurable result (an SEO-fast site, a launch, a passing audit).
• Lifecycle — the phase of work it applies to (plan, build, test-and-review, operate).
• Foundation primitive — a single optional flag for cross-cutting primitives every other workflow leans on (research, hub-meta tooling).

Browse the catalog Search every plugin alongside the skills, agents, MCP servers, hooks, commands, and resources they ship. 33

Contributing a plugin

Anyone at RBA can propose a new plugin. The fastest path is the guided wizard — answer a few plain questions and a bot scaffolds the bundle and opens a PR for review. To work in the repo directly, see Contributing.