Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
grep filtering for text and elements. Use bjs text | grep or bjs elements | grep to filter output. Saves context for smaller models.
What This Skill Does
CLI tool that controls Chrome via the Chrome DevTools Protocol, returning compact indexed lists of interactive page elements. Returns 50-200 tokens per interaction compared to thousands for accessibility tree-based approaches. Supports shadow DOM, file uploads, canvas apps, cross-origin iframes, and raw keyboard input.
Returns a compact numbered element index instead of a full accessibility tree, cutting token usage by 3-10x over multi-step browser flows compared to built-in browser tools.
When to use it
- Filling and submitting web forms on a target site
- Uploading files to Instagram or Twitter without an OS file picker
- Entering and formatting data in Google Sheets via keyboard navigation
- Clicking through cross-origin iframe widgets like captcha checkboxes
- Extracting visible text from React and Vue SPAs that use shadow DOM
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Fill out the contact form at example.com and submit it
- 1Opens the page with `bjs open https://example.com/contact`
- 2Lists interactive elements with `bjs elements` to get an indexed list of inputs and buttons
- 3Types into each field using `bjs type <index> <value>`
- 4Verifies field content with `bjs check <index>` before submitting
- 5Clicks the submit button with `bjs click <index>`
Form submitted; agent confirms by reading updated page text or taking a screenshot
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.