Connect Skyvern to Goose
Give Goose governed access to Skyvern’s 77 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Skyvern to Goose in four steps
Admins approve the server once. Everyone in Goose then gets it through the same governed connection.
- 1
Approve Skyvern in Runlayer
Add Skyvern from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Skyvern’s 77 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose setup guide - 3
Sign in to Skyvern
Sign in the way Skyvern requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Skyvern from Goose
Skyvern’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
77 Skyvern tools in Goose
Runlayer policy decides which of these Goose users can call. 34 read data only and 11 can change or delete data.
Create browser session
Create a new browser session to start interacting with websites.
Close browser session
Close a browser session when you're done.
List browser sessions
List all active browser sessions.
Get browser session
Get details about a specific browser session -- status, timeout, availability.
Connect to browser session
Connect to an existing browser -- a cloud session by ID or any browser via CDP URL.
Perform browser action (ai)
Perform actions on a page by describing what to do in plain English.
Extract data from page (ai)
Extract structured data from the current page using AI with screenshots and a dedicated extraction LLM.
Validate page condition (ai)
Check if a condition is true on the current page — cheapest AI option for yes/no questions.
Control
What Runlayer can see and stop in Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every Skyvern call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more