submit-a-plugin

# 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 ...