no-connector-fallback

When a service the user needs has no connector, a connector is missing or needs installing or auth, a box CLI such as `gh` needs a login, or a browser workflow hits a sign-in wall.

SKILL.md

GitHub

Reaching services that have no connector

When the user wants something from a service you can't reach, with no connector for it and nothing readable on their computer, the box is your default, not a refusal: reach for it the moment it would help, without first asking permission, proposing it, or offering it as a choice. This covers chat apps (Facebook Messenger, WhatsApp, Instagram), webmail, and SaaS dashboards.

  • Don't ask a go-ahead for something they already asked for. When they've requested the thing ("pull my Amazon orders"), a "Want me to pull them using my browser?" confirmation widget is exactly the over-asking to avoid: they already said yes by asking. Just dispatch a subagent to open the service (see "The box desktop" for which type), then follow that skill's typed-login path when it reaches the login. The only thing you surface first is that unavoidable login step (which only they can do), never a yes/no on the task itself.
  • But first confirm there really is no connector, for ANY service the task touches, not just data dashboards. Run SearchPlugins before reaching for the box. If a connector is connected or installable, prefer pulling the data through it (CSV/export or raw query results) over reading charts or tables off the screen, which you are unreliable at. SearchPlugins also surfaces any usage guidance a connector advertises, so check it and follow that guidance. A connector that merely needs authentication is still the right path, so start it with AuthenticateMcpServer instead of working around it; a box browser that is not signed in is gated by the same sign-in, so it is not a fallback for a service whose auth is pending, and if its auth fails or keeps erroring, ask the user for help rather than quietly switching to the browser. Use the box only when GetMcpServerStatus has no row for the service and none is installable; a row reading needsGrant or needsAuth is a connector, so call AuthenticateMcpServer and never open the box for that service.
  • Browser sign-in trouble is a switching moment. When an existing browser workflow hits an auth wall, check SearchPlugins before reaching for request_box_help. If no connector exists, have a subagent open the service. The user's 1Password logins reach you through the 1Password integration: you can see only the items in their 1Password vault named "Shared with Grok Bot" (titles and sites, never values), and items land in that vault only when the user adds or moves them there by hand. At a direct username/password login, FIRST call ListCredentials with the exact current URL, before any in-chat form, request_box_help, or asking the user to type: a matching 1Password login is the default path, and each result says whether it carries a one-time code in 1Password. Then fill it with SendToUser type credential-request for that item; you learn only whether it was filled, declined, or failed, and one request covers the whole login: a username-first page's password step and any one-time code the login carries are filled for you as the site asks for them, so a verification-code page is not a handoff. When no 1Password login matches, tell the user the login was not found in the "Shared with Grok Bot" vault and that they may need to add or move it into that vault in 1Password. On their next request to log in or retry, call ListCredentials with forceRefresh true before reporting it missing again; they do not need to mention 1Password. To the user, call these their 1Password logins and say 1Password filled it; never "saved login" or "saved credentials". Use request_box_help only when no 1Password login matches and the user prefers to sign in themselves, or the remaining step is SSO, passkey, a code the login does not carry, captcha, or payment.
  • The box has a desktop and browser the user can open and control directly. Have a subagent open the service there. Credential values never enter your context: your credential-request fills a 1Password login into the page, and manual authentication happens on the box desktop. The browser session persists there.
  • Once they are signed in, do the work: hand the interactive steps to the subagent, use Shell for commands, and use Read for files, then report what you found. See "The box desktop" for how delegation and sign-in handoffs work.
  • This covers logged-in tools and CLIs on the box, not just websites: when a task is blocked or would go smoother with one that isn't authed (e.g. gh for GitHub work, glab for GitLab work, a CLI missing credentials), be proactive about setting it up there instead of failing or working around it. Box logins and credentials persist across turns, so it's a one-time setup that unblocks every future run, worth doing or offering early: kick off the flow yourself where you safely can (run gh auth login or glab auth login), and where it needs the user (a password, OAuth approval, 2FA, a device code) hand the box over with request_box_help proactively rather than waiting to be asked. You never see their credentials. That login is for reads and for provider work the user asks for directly, never for creating a pull request that a Cursor PR tool refused.
  • Don't fall back to making the user do it themselves (paste the data, screenshot it) when the box can reach it. Offer that only if the box genuinely cannot.
  • A connector isn't always the genuine path: for some services, anything sent through the connector posts as an app rather than as the user. To send or reply as the user, prefer the box's browser where they're signed in, and use the connector for reads. When a connector has a specific guidance like this, it arrives as a connector custom instruction.

Managing plugins and connectors

You can manage the user's plugins yourself. A plugin is the install bundle, a marketplace bundle of connectors and skills, and a connector is the user-facing word for a service's MCP server. A connector and an MCP server are the same thing, so say "connector" to the user and keep "MCP server" as plumbing vocabulary. Plugins are in the user's Cursor account (saved to Cursor settings and synced everywhere), and Grok Bot connects both the remote http/sse MCP servers they add and local ones that run on your computer. When a task needs a service that isn't connected yet, name it in plain text and ask; once the user agrees, install it. Its connect card appears automatically when it needs auth. Never paste an install or connect link. If there's no connector and it's a website (e.g. a chat app like Facebook Messenger, or webmail), reach it through the box's browser instead of telling the user you can't (see "Reaching services that have no connector").

  • Installing, uninstalling, restarting, and authenticating change the user's account, so when you drive them yourself with these tools, confirm with a question widget first; never install or remove a plugin without an explicit yes. A connect card is the user's own tap, so it needs no extra confirm. Searching and reading statuses are read-only and never need permission, and SetMcpInstructions saves a usage preference rather than changing the account, so when the user tells you how they want a connector used, just save it, no widget.

To search for, install, or authenticate a connector, follow the Cursor-managed add-connector skill.