Browser
GitHub通过Anybox浏览器扩展控制Chrome。建议先检查状态，新建标签页获取tabId，操作前快照元素，导航后等待。复杂流程或需JS/CDP时，使用Node REPL初始化runtime并调用底层API。
Trigger Scenarios
Install
npx skills add fanfan-de/anybox --skill Browser -g -y
SKILL.md
Frontmatter
{
"name": "Browser",
"description": "Use when the Browser plugin is enabled and the user asks to inspect or control Chrome through the Anybox browser connector or Node REPL browser runtime."
}
Browser
Use the Browser MCP tools and Node REPL browser runtime from this plugin to inspect and control Chrome through the Anybox browser extension.
Start with browser_status when connection state is unclear. Prefer browser_open_tab for new work and carry the returned tabId into later calls. Use browser_interactive_snapshot before element-level actions, then pass the returned elementId to browser_click_element or browser_fill. Use browser_wait_for after navigation or actions that change the page.
For multi-step browser workflows, page inspection that needs JavaScript, or raw CDP access, use node_repl_js and initialize the browser runtime:
await setupBrowserRuntime({ globals: globalThis })
globalThis.browser = await agent.browsers.get("extension")
After initialization, use browser.tabs.list(), browser.tabs.open(url), browser.tabs.get(tabId), tab.snapshot(), tab.screenshot(), tab.click(), tab.fill(), tab.evaluate(), tab.cdp.send(), and tab.playwright.*. Use raw evaluate and CDP only when the normal browser_* tools are not sufficient.
Version History
- 08dc189 Current 2026-07-05 18:54
