bb-plugins

My personal bb plugins, distributed as a custom marketplace.

Use the marketplace

Go to Settings → Plugins marketplace and add:

git:https://github.com/charpeni/bb-plugins@main

All charpeni's plugins are then available directly from Extensions → Browse plugins.

Or from the CLI

bb marketplace add git:github.com/charpeni/bb-plugins@main
bb plugin install system-monitor@charpeni

Plugins

Plugin	Description
Dependabot	Review GitHub Dependabot alerts by dependency and send grouped fixes to BB agents.
Disk Usage	See what's taking up disk space on the bb server host, with drill-down.
Skills.sh	Install skills.sh skills globally for every AI agent bb runs, with drift updates.
System Monitor	Live CPU, memory, disk, load, and uptime statistics for the bb server host.

Each plugin can also be installed directly, without the marketplace:

bb plugin install git:https://github.com/charpeni/bb-plugins.git@^0.1.0 --tag-prefix system-monitor/ --plugin system-monitor

Repository layout

• plugins/<id>/ — one self-contained plugin per directory. No workspace:/catalog: dependencies: bb installs git plugins with plain npm install --omit=dev, so every manifest must resolve standalone.
• .bb/plugins.json — the collection index that makes bb plugin install git:… --plugin <name> work.
• marketplace.json — the marketplace catalog bb reads (with icons/ for any file-based entry icons). Entries use git tag ranges, so releases reach users without catalog changes.
• schema/ + scripts/validate-manifests.mjs — vendored BB schemas and the validation CI runs on every push.

Develop

pnpm install
pnpm run validate   # manifests against BB's schemas + cross-checks
pnpm run typecheck
pnpm run test
pnpm run build      # bb plugin build, via the bb-app devDependency

For a live loop against a running bb, register a plugin directory as a path install once, then let bb plugin dev rebuild and reload on save:

bb plugin install ./plugins/system-monitor
bb plugin dev plugins/system-monitor

Release a plugin

Bump the plugin's package.json version, then tag <id>/v<version>:

git tag system-monitor/v0.1.1
git push origin system-monitor/v0.1.1

bb resolves each marketplace entry's semver range over its tagPrefix tags (system-monitor/vX.Y.Z), records the tag and commit it installed, and refuses a tag that later moves — publish a fix as a new version, never retag.