bb-plugins
/bb-plugins
Build, install, and debug bb plugins. Use when the user wants a bb plugin, a sidebar panel, a bb CLI subcommand, an agent tool, a theme, a provider, or to extend bb itself. For running threads and the core bb CLI, use bb-cli instead.
- Author
- davidondrej ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Build, install, and debug bb plugins. Use when the user wants a bb plugin, a sidebar panel, a bb CLI subcommand, an agent tool, a theme, a provider, or to extend bb itself. For running threads and the core bb CLI, use bb-cli instead.
Original author description
Build, install, and debug bb plugins. Use when the user wants a bb plugin, a sidebar panel, a bb CLI subcommand, an agent tool, a theme, a provider, or to extend bb itself. For running threads and the core bb CLI, use bb-cli instead.
How it works
- Trust
- This skill vs others
- Scaffold
- What a plugin can add
- Install and ship
- Check the work
SKILL.md preview
--- name: bb-plugins description: 'Build, install, and debug bb plugins. Use when the user wants a bb plugin, a sidebar panel, a bb CLI subcommand, an agent tool, a theme, a provider, or to extend bb itself. For running threads and the core bb CLI, use bb-cli instead.' --- # bb plugins bb plugins are TypeScript packages that run inside bb. They are how bb extends itself. Many first-party features are plugins: GitHub, Docs, Memory, Tasks, Connect, Automations, Secrets, Keep Awake, and the coding-agent providers. ## Trust Plugins are full-trust. Server code runs in-process. App UI is same-origin page code, not a sandbox. Host workers run as Node on enrolled machines. Review source before installing third-party plugins. Keep credentials in `secret: true` settings. ## This skill vs others - Use this skill to create, install, or change a plugin. - Use `bb-cli` to operate bb (threads, projects, environments). - For exact API signatures, read the `bb-plugin-authoring` skill if it is available, then run `bb guide plugins`. In the plugin directory, run `bb plugin types` before trusting local SDK types. Do not guess from minified `dist/` files. ## Scaffold ```sh bb plugin new hello # add --app for a React UI cd bb-plugin-hello bb plugin install . --yes bb plugin dev # rebuild + reload on save ``` The manifest is the `bb` object in `package.json`. Required: `bb.name`, `bb.description`, `bb.branding.icon`, `bb.server`. Optional: `bb.app`, `bb.host`, `bb.skills`, `bb.themes`. Plugin id is the last package-name segment with a `bb-plugin-` prefix stripped. `bb-plugin-hello` and `@acme/bb-plugin-hello` both become `hello`. Put runtime imports in `dependencies`. Leave types and tooling in `devDependencies`. Git installs run `npm install --omit=dev`. ## What a plugin can add A default-export factory in `server.ts` receives `BbPluginApi` and registers surfaces: - settings, kv + SQLite storage, HTTP, RPC, realtime - background services and cron - one top-level `bb <name> …` command - agent tools, `skills/` folders, extra instructions - mention providers - optional host workers and experimental agent providers `app.tsx` default-exports `definePluginApp` and can add pages, thread-panel actions, composer controls, file openers, and a replacement sidebar. Do not copy the full API into this skill. Read `bb-plugin-authoring` when implementing a surface. ## Install and ship ```sh bb plugin install . # local path bb plugin install github # bundled official plugin bb plugin install npm:bb-plugin-notes@^1.0.0 bb plugin install git:https://github.com/acme/bb-plugin-notes.git@^1.2.0 bb plugin list bb plugin reload <id> bb plugin logs <id> -f ``` Installs prompt because the code is full-trust. Pass `--yes` to skip. A failed managed update rolls back. Catalog refresh never installs code. Community listings live at https://getbb.app/marketplace/v1/marketplace.json. Submit via a PR to https://github.com/get-bb/marketplace. Use the `submit-a-plugin` skill for that workflow. ## Check the work 1. `bb plugin list` shows the plugin `running`. 2. If it added a CLI, `bb <command> --help` works. 3. If it added UI, open the page or panel in bb and confirm it loads. 4. If the factory throws, the plugin is `error`. Read `bb plugin logs <id>` and fix, then `bb plugin reload <id>`.
Versions
The database has no other skills named bb-plugins.
Database snapshot: 13.11.2026 · package version 437c7044f3e1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90Codex CLI Plugins
This skill should be used when the user asks to "create a Codex plugin", "build a plugin for Codex CLI", "package a Codex skill", "set up a Codex marketplace", "publish a Codex plugin", "configure plugin.json manifest", "add MCP to a Codex plugin", "install a local plugin in… - 100plugins-management
Create, publish, delete, and submit plugins for coding agents (Claude Code, OpenCode, Devin CLI/Desktop). Use when user wants to (1) create a new plugin with proper structure, (2) create or configure a plugin marketplace, (3) publish plugins to GitHub/GitLab/npm, (4)… - 100a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI. - 100claude-plugin-converter
Use when converting Claude Code plugins into self-contained Hermes plugins — discovery analysis then full conversion. - 100dev-swarm-install-ai-code-agent
Install AI code agent CLI tools including claude-code, gemini-cli, codex, and github copilot-cli. Use when setting up AI coding assistants or when the user asks to install an AI code agent. - 100retaxonomize-plugins
Use when skills must move between plugins, or plugins be created, merged, or retired. Not for reordering a listing, use reorder. Not for retiring a code path, use deprecate-and-migrate.