Submit a bb plugin to the BB Community marketplace. Use whenever a user asks to submit, list, publish, or add a plugin to the BB marketplace, or asks for a marketplace pull request. This skill validates the plugin and release, creates the marketplace entry and icon, and opens the pull request.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add get-bb/bb --skill submit-a-plugin --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Submit A Plugin?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/get-bb-submit-a-plugin)More formats (shields.io, HTML) on the badges page.
---
name: submit-a-plugin
description: Submit a bb plugin to the BB Community marketplace. Use whenever a user asks to submit, list, publish, or add a plugin to the BB marketplace, or asks for a marketplace pull request. This skill validates the plugin and release, creates the marketplace entry and icon, and opens the pull request.
---
# Submit a plugin
Submit a public plugin to the BB Community marketplace. The marketplace stores
plugin metadata. The plugin code stays in its Git repository or npm package.
## Choose the task
If the user asks only for instructions, explain the process without remote
changes.
If the user asks for a submission, prepare and validate everything possible.
Ask only for information that the plugin, Git, npm, GitHub, or marketplace
cannot supply.
A submission request does not approve a release. Before the first Git push, tag,
npm publication, or other release mutation, show the exact account, repository,
commit, package, version, source, and commands. Get approval for that release.
Do not expose credentials, private URLs, or local secrets.
## Read current contracts
The marketplace contract can change independently from BB releases. Read these
files from the default branch of https://github.com/get-bb/marketplace:
- README.md
- schema/marketplace.schema.json
- icons/README.md
- At least two current files in entries/
Treat those files as the contract. Use this skill for workflow and quality
rules.
## Workflow
1. Read repository instructions, package.json, Git state, and release state.
2. Validate the plugin with its package manager and bb plugin build.
3. Select and verify one public release source.
4. Get separate approval before any release mutation.
5. Create one marketplace entry and a vendored icon.
6. Validate the marketplace repository.
7. Commit only the entry and icon.
8. Open a pull request from the submitter account.
Read these references as the task reaches each stage:
- Read references/plugin-release.md before validating or releasing a plugin.
- Read references/marketplace-entry.md before creating the entry or icon.
- Read references/pull-request.md before cloning, validating, or submitting
the marketplace repository.
Use scripts/derive-plugin-id.mjs to calculate the same plugin ID that BB uses:
```sh
node /PATH/TO/THIS/SKILL/scripts/derive-plugin-id.mjs /PATH/TO/PLUGIN/package.json
```
## Completion
Return the pull request URL, released source, and validation results. Do not wait
for a merge unless the user asks.
A compatible release within an existing tracking range usually needs no new
marketplace pull request. Open another pull request when source, branding,
description, ownership, tag, or range changes.

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!