Contribute

You don’t have to be a developer to contribute to RBA Skills. If you have a prompt that saves your team hours, an idea for a new tool, or you spotted a typo, we want it.

Start here: the guided wizard

Open the contribution wizard →

Answer a few plain-language questions — no jargon, no forms to choose between, no taxonomy decisions. The wizard figures out the right artifact type and category for you, then hands you a GitHub form that’s already filled in. You just press submit. A bot opens the pull request; a maintainer reviews and merges it.

This is the recommended path for everyone who isn’t editing the repo directly.

Or pick a form directly

Know exactly what you want? Skip the wizard and open the matching form:

What you want to do	Form
Submit a new plugin — a complete bundle (one or more skills, agents, or tools packaged together for installation)	Open form →
Submit a standalone artifact — one skill, agent, command, MCP server, hook, or resource on its own	Open form →
Add a tool to a plugin — add a skill, agent, slash command, MCP server, hook, or resource to a plugin that already exists	Open form →
Suggest an edit — improve any existing plugin or doc	Open form →
Report a problem — bug, broken link, typo, or anything else that isn’t right	Open form →

What you need

A free GitHub account. That’s it. No git, no terminal, no editor.

What happens after you submit

1. The form creates a GitHub issue.
2. A bot reads your answers and opens a pull request with the right files in the right places.
3. The bot comments on your issue with a link to the PR.
4. A maintainer reviews — they might ask a question or suggest a tweak in the issue thread.
5. Once approved, it merges and goes live on the site within a minute or two.

If something’s missing or invalid, the bot leaves a comment explaining what to fix. Edit the issue and the bot retries automatically.

See How submissions work for the technical details.

Edit any page from your browser

Every plugin and tool detail page has a Suggest a change on GitHub link at the bottom. Click it to open that exact file in GitHub’s web editor — no clone, no fork wizardry, no JSON. Make your change, write a one-line message, and GitHub opens a PR for you.

Already comfortable with git?

Skip the form — open a PR directly

For a new plugin, create:

plugins/<slug>/
├── .claude-plugin/plugin.json
├── rba-meta.json
├── README.md
└── skills/<slug>/SKILL.md

See plugins/research/ for a working example, and the authoring standards and review process for what reviewers look for.

Run npm run dev to preview locally, then open a PR.

Questions?

Not sure where your idea fits, or want a second pair of eyes before submitting? Open the form anyway and add a note — we’d rather help shape a contribution than miss a good one.