Agent skill

Submit A Plugin

by get-bb in get-bb/bb

Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested.

MITAuto-check passedDevelopment

Install Submit A Plugin

skills CLI
$ npx skills add get-bb/bb --skill submit-a-plugin -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install get-bb/bb submit-a-plugin --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/get-bb/bb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/bb-guide/skills/submit-a-plugin .claude/skills/submit-a-plugin && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
submit-a-plugin
GitHub stars
4.2k
Token cost
~873 tokens
SKILL.md length
465 words
Files
5 (incl. scripts, references)
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested.

  • Works in 10 steps: Read repository instructions,… → Validate the plugin with its package… → Select and verify one public release… → …
  • Development work in your project
  • SKILL.md covers Choose the task, Read current contracts, Workflow and Completion
  • Runs JavaScript scripts from its folder; calls node

What it does

Submit A Plugin is an agent skill from get-bb/bb. Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/marketplace-entry.md`, `references/plugin-release.md` and `references/pull-request.md`).

It sits in Development. It works with npm and Git. The repository describes itself as: The agent IDE that builds itself. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/submit-a-plugin”

Requirements

  • Node.js

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  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 with a vendored icon.
  6. Install the plugin and capture its screenshots.
  7. Copy the plugin PLUGIN_OVERVIEW.md file into the marketplace. The public
  8. Validate the marketplace repository.
  9. Commit only the entry, icon, screenshots, and overview file.
  10. Open a pull request from the submitter account.

What it can do on your machine

Read from SKILL.md and the folder at commit 68a1e8b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Submit A Plugin loads about 873 tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 465 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~873
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from get-bb/bb at commit 68a1e8b, republished under its MIT licence (© get-bb). 465 words, ~873 tokens.

Download SKILL.mdSave it as .claude/skills/submit-a-plugin/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
submit-a-plugin
description
Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested.

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-v2.schema.json
  • marketplace.base.json, for the current category IDs
  • icons/README.md
  • At least two current files in entries/

An entry file uses the version 2 entry fields. Read schema/marketplace-v2.schema.json for those fields. The older schema/marketplace.schema.json file describes the frozen version 1 output document. Do not use it as the entry contract.

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 with a vendored icon.
  6. Install the plugin and capture its screenshots.
  7. Copy the plugin PLUGIN_OVERVIEW.md file into the marketplace. The public marketplace requires an overview file on every entry.
  8. Validate the marketplace repository.
  9. Commit only the entry, icon, screenshots, and overview file.
  10. Open a pull request from the submitter account.
Show full SKILL.md (167 more words)Show less

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 you create the entry, icon, screenshots, or overview file. It states what a good entry and description hold, how to capture screenshots with a harness browser or computer automation tool, what to ask the user for when the harness has no such tool, which markdown the long-form description can use, and what to do when the plugin has no PLUGIN_OVERVIEW.md yet. It ends with a quality check to run before the pull request.
  • 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, long-form description, category, screenshots, ownership, tag, or range changes.

© get-bb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in plugins/bb-guide/skills/submit-a-plugin of get-bb/bb.

  • SKILL.md
  • references/marketplace-entry.md
  • references/plugin-release.md
  • references/pull-request.md
  • scripts/derive-plugin-id.mjs

Open the folder on GitHubat commit 68a1e8b

Compare with similar skills

Submit A Plugin next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Submit A Plugin compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Submit A Plugin this skillget-bb/bb4.2k—~873Automated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0
Open Code Review Delegatealibaba/open-code-review44k—~2kAutomated safety check: PassApache-2.0
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Hunk Release Workflowmodem-dev/hunk9.5k—~3.8kAutomated safety check: PassMIT

Similar skills

  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Open Code Review Delegate

    alibaba/open-code-review

    Has the host agent do the code review itself while the ocr CLI handles file selection and rule lookup, covering workspace changes, branch ranges or single commits.

    44k GitHub stars~2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Hunk Release Workflow

    modem-dev/hunk

    Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.

    9.5k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review

    yaklang/yakit

    对 Yakit 仓库的代码改动做规范化 code review:按代码逻辑、TS 定义、UI 引用与 Props、CSS 样式、依赖版本、配置项六个维度审查,检查测试用例缺失,强制执行 tsc 类型检查与 vitest 测试验证,输出「结果汇总 / 明细解释 / 合并结论」三块报告,经用户确认后写入文件。当用户要求 review、审查、评审代码改动,或在提交、合并、提 PR…

    7.8k GitHub stars~1.4k tokensUpdated 7 days ago
    DevelopmentAuto-check: notes

More from get-bb/bb

All 33 skills in this repo
  • Bb CLI

    get-bb/bb

    Inspect or manage BB state with the bb CLI; use for BB commands and configuration.

    4.2k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Skill Creator

    get-bb/bb

    Create or improve BB skills, including their triggers, instructions, and supporting resources.

    4.2k GitHub stars~702 tokensUpdated today
    Auto-check passed
  • Workflows

    get-bb/bb

    Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.

    4.2k GitHub stars~890 tokensUpdated today
    Auto-check passed
  • Verify Bb

    get-bb/bb

    Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI.

    4.2k GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Create or edit BB color themes and inspect them in the Theme Preview panel.

    4.2k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Tasks

    get-bb/bb

    Work on or manage records in BB Tasks, including task keys such as ABC-12.

    4.2k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Submit A Plugin

What does Submit A Plugin do?

Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested. Submit A Plugin is an agent skill from get-bb/bb. Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested.

When should I use Submit A Plugin?

Submit A Plugin fits situations like: development work in your project.

How do I install Submit A Plugin in Claude Code?

Run `npx skills add get-bb/bb --skill submit-a-plugin -a claude-code`. Or copy the skill folder (plugins/bb-guide/skills/submit-a-plugin in get-bb/bb) into .claude/skills/submit-a-plugin in your project. Claude Code loads it when a task matches its description.

How do I install Submit A Plugin in Codex?

Run `npx skills add get-bb/bb --skill submit-a-plugin -a codex`. Or copy the skill folder (plugins/bb-guide/skills/submit-a-plugin in get-bb/bb) into .agents/skills/submit-a-plugin in your project. Codex loads it when a task matches its description.

Can I use Submit A Plugin in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add get-bb/bb --skill submit-a-plugin -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/submit-a-plugin, .gemini/skills/submit-a-plugin, .github/skills/submit-a-plugin and .opencode/skills/submit-a-plugin in your project.

What does Submit A Plugin need to run?

Going by SKILL.md and its folder, Submit A Plugin needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Submit A Plugin access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Submit A Plugin safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Submit A Plugin use?

Submit A Plugin is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Submit A Plugin use?

About 873 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.6k tokens, read only when the agent opens those files.

What are the alternatives to Submit A Plugin?

Skills that share tags, products or a category with Submit A Plugin: Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars), Open Code Review CLI (alibaba/open-code-review, 44k stars), Open Code Review Delegate (alibaba/open-code-review, 44k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Submit A Plugin?

get-bb (a GitHub organization) maintains it in get-bb/bb, which has 4,155 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

Source: get-bb/bb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.