submit-a-plugin

# Submit a plugin Submit a public plugin to the BB Community marketplace through a pull request. The marketplace lists plugin data only. The plugin code stays in its Git repository or npm package. ## Start with current contracts The marketplace contract can change independently from bb releases. 1. Open the plugin repository and read all applicable instruction files. 2. Inspect the plugin manifest and its current Git state. 3. Read the current marketplace files before you make an entry. Use this source repository: ```text https://github.com/get-bb/marketplace ``` Read these files from its default branch: - `README.md` - `schema/marketplace.schema.json` - `icons/README.md` - Two or more current files in `entries/` Treat those files as the source of truth. Use this skill for the workflow and quality checks. ## Determine the user request If the user asks only for instructions, give instructions without external changes. If the user asks for submission, prepare the release and pull request. Ask only for information that you cannot obtain from the plugin, Git, npm, or GitHub. Stop before each release mutation until the user approves the exact release. Do not expose tokens, npm credentials, private URLs, or local secrets. ## Check the plugin Find the plugin package before you prepare a release. 1. Read its `package.json`. 2. Find the package `name`, `version`, `engines`, and `bb` fields. 3. Confirm that `bb.name`, `bb.description`, and `bb.branding` describe the ...