|
| 1 | +# @browserbasehq/openclaw-browserbase |
| 2 | + |
| 3 | +Browserbase plugin for OpenClaw (with legacy ClawdBot compatibility). |
| 4 | + |
| 5 | +It provides: |
| 6 | + |
| 7 | +- interactive Browserbase credential setup, |
| 8 | +- config status/env helpers, |
| 9 | +- dynamic skill sync from `github:browserbase/skills`. |
| 10 | + |
| 11 | +## Install |
| 12 | + |
| 13 | +```bash |
| 14 | +openclaw plugins install @browserbasehq/openclaw-browserbase |
| 15 | +``` |
| 16 | + |
| 17 | +For local development: |
| 18 | + |
| 19 | +```bash |
| 20 | +openclaw plugins install -l . |
| 21 | +``` |
| 22 | + |
| 23 | +## Setup |
| 24 | + |
| 25 | +```bash |
| 26 | +openclaw browserbase setup |
| 27 | +``` |
| 28 | + |
| 29 | +By default setup will also sync Browserbase skills from `browserbase/skills` into |
| 30 | +`~/.openclaw/skills`. |
| 31 | + |
| 32 | +You can manage skill sync directly: |
| 33 | + |
| 34 | +```bash |
| 35 | +openclaw browserbase skills status |
| 36 | +openclaw browserbase skills sync |
| 37 | +openclaw browserbase skills sync --ref main |
| 38 | +openclaw browserbase skills sync --dir ~/.openclaw/skills |
| 39 | +``` |
| 40 | + |
| 41 | +## Commands |
| 42 | + |
| 43 | +```bash |
| 44 | +openclaw browserbase setup # prompt for API key + project ID |
| 45 | +openclaw browserbase status # show configuration status |
| 46 | +openclaw browserbase status --json # machine-readable status |
| 47 | +openclaw browserbase env --format shell # export commands |
| 48 | +openclaw browserbase env --format dotenv # dotenv output |
| 49 | +openclaw browserbase env --format json # JSON output |
| 50 | +openclaw browserbase where # config file path used |
| 51 | +openclaw browserbase skills status # check dynamic skills sync status |
| 52 | +openclaw browserbase skills sync # download/update skills from browserbase/skills |
| 53 | +``` |
| 54 | + |
| 55 | +Legacy CLI alias support remains: |
| 56 | + |
| 57 | +```bash |
| 58 | +clawdbot browserbase setup |
| 59 | +``` |
| 60 | + |
| 61 | +## Dynamic skills behavior |
| 62 | + |
| 63 | +OpenClaw installs plugins with lifecycle scripts disabled, so plugin install hooks are not a reliable place to fetch remote skill files. |
| 64 | + |
| 65 | +This plugin instead syncs skills during setup and (optionally) on startup when missing: |
| 66 | + |
| 67 | +- `browser-automation` |
| 68 | +- `functions` |
| 69 | + |
| 70 | +Source of truth: [https://github.com/browserbase/skills](https://github.com/browserbase/skills) |
| 71 | + |
| 72 | +## Development |
| 73 | + |
| 74 | +```bash |
| 75 | +pnpm install |
| 76 | +pnpm run check-types |
| 77 | +pnpm test |
| 78 | +``` |
| 79 | + |
| 80 | +## References |
| 81 | + |
| 82 | +- OpenClaw Skills: https://docs.openclaw.ai/tools/skills |
| 83 | +- OpenClaw Skills Config: https://docs.openclaw.ai/tools/skills-config |
| 84 | +- OpenClaw Plugin System: https://docs.openclaw.ai/tools/plugin |
| 85 | +- OpenClaw Plugin Manifest: https://docs.openclaw.ai/plugins/manifest |
| 86 | +- Browserbase skills reference: https://github.com/browserbase/skills |
| 87 | +- Example plugin reference: https://github.com/pepicrft/clawd-plugin-ralph |
0 commit comments