browser-fallback

Routes tasks between connected plugins and the Bot's browser based on probe results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bots silently fail in two directions: scraping a site through a browser while a working connector sits installed, or claiming a connector exists and returning fabricated output when nothing was connected. This Skill enforces a probe-first routing decision so every task uses a verified path. ## Core Features & Use Cases - Probe-based routing: Enumerate enabled plugins, run the smallest read to prove one works, then choose plugin, browser fallback, or refusal. - Reachability guardrails: Refuse localhost or private-LAN targets immediately, since the cloud computer cannot reach a human's local machine. - Labeled output: Every result states the path taken (plugin, browser, or refused) with the probe result quoted, so fallback data is never mistaken for connector-grade data. - Use Case: A task needs yesterday's Gmail threads but the Gmail connector errors on auth; the Skill probes the connector, falls back to read-only browser access, and labels the output as browser-derived with URL and fetch time. ## Quick Start Ask the Bot to check whether the required plugin is connected and working for this task, and to fall back to its browser with a labeled result if the plugin probe fails.

Frequently Asked Questions about browser-fallback

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

FAQPage Schema
How do I choose between a plugin and a browser for a Bot task?▼

Enumerate the plugins enabled for the Bot, then run the smallest read probe against the candidate connector. Use the plugin if the probe succeeds; otherwise use the browser for read-only public content, or refuse if neither path can reach the target.

How do I verify a connector is actually working before using it?▼

Run a minimal read probe such as fetching one record, one message, or one file listing. Installed, enabled, and working are three different states, and only a successful probe proves the third; the settings screen alone is not evidence.

Can a cloud Bot access localhost on my machine?▼

No. The Bot's cloud computer cannot reach a server running on your localhost or private LAN, so localhost:3000 on your laptop does not exist from the Bot's machine. Tasks requiring it are refused with that reason rather than attempted.

When should browser fallback not be used?▼

Do not use the browser to bypass a login wall, paywall, or site terms after a plugin refused, and never use it for acts outside chat like sending, posting, or purchasing. A policy refusal is not a routing problem, and fallback is read-only.

Why does a Bot claim a plugin worked when nothing was connected?▼

That failure happens when the Bot assumes connector state from its charter instead of probing. This Skill requires quoting the probe result in the output and forbids claiming a plugin was used unless both its probe and its call succeeded.