Overview
RBA Skills is RBA’s central catalog of agentic tools — the prompts, agents, integrations, and workflows the company has standardized for the AI tools we use day-to-day. It exists in two places at once:
- An installable Claude Code plugin marketplace. One command in your terminal connects you to every plugin in the catalog. Each plugin bundles a related set of skills, agents, MCP servers, hooks, slash commands, and resources you can install with another command.
- This public catalog site. Every plugin and every artifact inside it has a page here. You can browse, read methodologies, copy SKILL.md content into another AI tool, or just see what RBA has built — without installing anything.
The two are kept in lockstep automatically. Whatever lives under plugins/ in the source repo shows up both as an installable plugin and as a page on this site.
Who this is for
Section titled “Who this is for”Primarily everyone at RBA — strategists, designers, engineers, security, PMs, BAs — anyone who wants to use AI to do their job better and faster, using patterns RBA has already validated.
You don’t have to write code or use Claude Code to get value from RBA Skills:
- If you use Claude Code, install plugins and invoke skills directly in your sessions.
- If you use another AI tool (web Claude, ChatGPT, Codex, internal tools), browse a skill’s page on this site, read its methodology, and apply it in your tool of choice. A well-written SKILL.md is a methodology — it carries over.
- If you’re new to AI tooling at RBA, start with AI Governance for the policies and guardrails that apply to every employee.
How it’s organized
Section titled “How it’s organized”Plugins aren’t sorted into a single hierarchy. Instead, every plugin is described by a handful of optional facets so you can find one along whichever axis matches how you think about your work.
| Facet | What it captures | Examples |
|---|---|---|
| Platform | Vendor- or product-specific (only makes sense in that stack) | sitecore, umbraco, azure, figma |
| Discipline | How a specific role works day-to-day | engineering, design, strategy, security |
| Outcome | Shaped by a deliverable or measurable result | seo, performance, accessibility-audit |
| Lifecycle | The phase of project work it applies to | plan, build, test-and-review, operate |
| Foundation primitive | A single optional flag for cross-cutting primitives every workflow leans on | research, rba-hub-mcp, document-templates |
Pick whichever facets fit your work. A Sitecore developer narrows by platforms=sitecore; an accessibility specialist by disciplines=design or outcomes=accessibility-audit; a project manager by disciplines=strategy and lifecycle=plan.
What’s inside a plugin
Section titled “What’s inside a plugin”Each plugin can ship up to seven kinds of artifact. You don’t need every kind in every plugin — a plugin can be a single skill, or a full bundle that wires together skills, agents, integrations, and hooks.
| Artifact | What it is | Where it shows up |
|---|---|---|
| Skill | A methodology Claude follows inside a conversation. Invoked with a slash command or auto-discovered from context. | /skills/ |
| Agent | A specialized subagent spawned for a contained task (review, audit, research). Has its own context, prompt, and tool allowlist. | /agents/ |
| MCP server | An integration that connects Claude to a system or data source over the Model Context Protocol. | /mcp/ |
| Hook | A deterministic shell command Claude runs in response to lifecycle events (pre-tool, post-tool, on-stop). Enforces guarantees prompts can’t. | /hooks/ |
| Slash command | A direct invocation shortcut. New work usually ships as a skill instead — commands are kept for cases where you want strictly user-triggered behavior. | /commands/ |
| Resource | A non-executable asset — project skeleton, reference architecture, template, runbook. The artifact work produces from or compares against. | /resources/ |
| Plugin (bundle) | The container. Each plugin is a plugins/<name>/ folder that packages one or more of the above with its install metadata. | /plugins/ |
Next steps
Section titled “Next steps”- Install & Use — Add the marketplace, install a plugin, and start invoking artifacts.
- The RBA Way — How the catalog connects to how RBA actually delivers work.
- Contributing — Submit a plugin, add a skill, or fix a typo. No git required.
- Plugins catalog — Browse every installable plugin in the catalog.
- AI Governance — Required reading for every RBA employee using AI on client work.