browser-plugin

Drives a public web page through an enabled browser plugin and verifies the result.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill browser-plugin-jyeswak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-plugin
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/browser-plugin
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill browser-plugin-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Browser plugins like browser-use, Playwright, or browse may be approved for a Bot but return zero usable tools, so agents often pretend a browser ran when it did not. This Skill forces enumeration of the Bot's actual browser-plugin tools, drives one public page, and quotes a visible observable so the result is provably real. ## Core Features & Use Cases - Tool enumeration and verification: Lists the Bot's browser-plugin tools first; an empty list yields UNVERIFIED instead of a fake pass, with a handoff to plugin-enable-verify. - Single-page driving with proof: Navigates one public URL, captures a snapshot or accessibility tree, and quotes a visible string labeled with the plugin name and PATH PLUGIN. - Hard safety walls: Stops at login, 2FA, CAPTCHA, payment, or identity prompts, never types secrets, and hands off to takeover-2fa. - Use Case: You need to confirm a rendered heading on a JavaScript-heavy public site where a Firecrawl scrape returns the wrong shape; the Skill drives the page via the enabled plugin and writes a receipt under /workspace/gb-proof/. ## Quick Start Ask the agent to open a specific public URL with the browser plugin, quote a visible heading or button label from the page, and report which plugin was used.

Frequently Asked Questions about browser-plugin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a browser plugin actually works on my Bot?

Enumerate the Bot's tools and look for entries matching browser-use, Playwright, browse, or browserbase, then call one and quote a visible string from the page. If the tool list is empty, report UNVERIFIED and attach the plugin to that Bot instead of claiming success.

When should I use a browser plugin instead of Firecrawl scrape?

Use a browser plugin when the page needs a real browser, such as SPAs, rendered headings, or button interactions, and Firecrawl returns missing or wrongly shaped content. If the goal is just getting page markdown and Firecrawl tools exist, prefer Firecrawl.

Can a browser plugin log into sites or pass 2FA?

No. The Skill stops at any password, 2FA, CAPTCHA, payment, or identity wall, takes a screenshot, and hands off to a human takeover flow. It never types passwords, OTPs, or card details.

Why does an approved plugin return zero tools?

Approval in a plugin inventory does not mean the plugin is functional; same-day tool census can return zero tools for browser-use, Playwright, and browse. The fix is attaching the plugin to the specific Bot and completing any OAuth, then re-enumerating.

Can I use the local machine's Chrome browser for this?

No. The Skill runs only on the cloud computer; localhost on Studio or Brain is unreachable, and the human laptop's Chrome must never be used. The Agent Computer browser is a separate path labeled BROWSER, not PLUGIN.