Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →get-bb/share-server-links
Share a local HTTP server with the user over bb connect.
Passed 18 of 21 test cases with the skill, and 7 of 21 without it.
and 12 more in the full report
12 fixed8 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
When `bb connect expose 8000` is run outside an active thread session without a `--host` argument, which machine hosts the share by default?
| Checked | Without skill | With skill |
|---|---|---|
| States that sharing defaults to the machine running the bb server. | Missed | Passed |
The instructions your model reads when the skill loads.
When you start an HTTP server the user should open, give them a connect share URL — not a localhost URL. Shares work from threads running on any enrolled host, and the command resolves the thread's host automatically.
bb connect status --json. If not paired / not
connected, give the localhost URL and mention that bb connect enables
remote URLs once paired from the getbb.app dashboard.bb connect expose <port>. It prints that host's share URL. Use --host <name-or-id> only
when you intentionally need another enrolled host; outside a thread,
sharing defaults to the machine running the bb server.bb connect unexpose <port> from the same
thread (or with the same --host) so the share is cleaned up. Use
bb connect shares [--host <name-or-id>] to inspect that host's shares.bb connect --help and bb connect <command> --help print the commands and
their flags and exit 0. Unknown commands and flags fail with a suggestion —
bb connect list points at bb connect shares — and with --json a failure
prints {"ok":false,"error":{"code":…,"message":…}} on stdout while the same
message stays on stderr.
Server-host shares use https://<server-label>--<port>.<base-domain> through
the server tunnel. Other enrolled hosts use
https://<machine-label>--<port>.<base-domain> through their daemon. If a
machine was not enrolled through Connect, expose fails with instructions to
remove and re-add it under Settings > Machines.
Settings → Installed plugins → Connect has a "Tell agents about remote access"
toggle, enabled by default. Use
bb plugin config connect set sendRemoteInstructions false to suppress the
remote-access message, or true to restore it. This controls only the message;
sharing still works. The message otherwise requires active or recent remote
usage. Changes apply when session instructions are next assembled.
test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.