$ ~/registry/skill/composiohq-composio-skills-browser-tool-automation

SKILL

browser-tool-automation

Name: browser-tool-automation
Author: Composio

Automate browser tool tasks via Rube MCP with schema lookup first.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is essentially an open-source prompt/workflow document, but it is intended to connect to a remote Rube MCP service and drive Browser Tool workflows, so the overall posture is a typical integration-level caution. No local API keys or obvious overreach red flags are stated; however, actual data egress and execution boundaries depend on the connected remote tools and authorization flow.

CredentialsCaution

The material says no API keys are needed, but the README explicitly requires establishing an ACTIVE `browser_tool` connection via `RUBE_MANAGE_CONNECTIONS`, potentially completing authorization through an auth link. So while no local environment secret is required, third-party account linking and token-based authorization may still be involved, creating normal credential exposure considerations.

Network egressCaution

The README instructs users to configure `https://rube.app/mcp` as an MCP server and use Composio/Rube remote interfaces for tool discovery, connection management, and execution; workflow requests, session IDs, arguments, and possibly browser-operation-related data would be sent to the stated external service. The endpoint is explicit rather than unknown, but network egress is clearly present.

Code executionCaution

This skill itself is classified as prompt-only and does not directly provide local executable code; however, it instructs use of remote execution capabilities such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, which means triggering external automation through MCP. No concrete red flags indicate local system-level privilege requests or hidden execution behavior.

Data accessCaution

The document does not state direct local file read/write access or broad host-data permissions; however, as an entry point for Browser Tool automation, it may process user inputs, session data, and browser-side resources/content, with the actual access scope depending on the post-connection tool schemas and granted authorization. No obvious excessive permission request is shown, but the boundary is not fully visible from the material.

Supply chainLow risk

The source is a GitHub open-source repository, the system marks it as open-source, and community adoption is very high (64.7k stars), all of which are strong positive indicators. What is presented here is a skill description rather than a closed-source binary; although the license and maintenance status are not explicit, the supply-chain risk appears relatively low.

Recommendations

Only add `https://rube.app/mcp` after confirming you trust the Rube/Composio service and its privacy terms.
Before connecting `browser_tool`, review the scopes requested on the authorization page and avoid granting unnecessary access.
Inspect the actual schema returned by `RUBE_SEARCH_TOOLS` before use, and avoid sending sensitive data as remote tool arguments.
Prefer testing in a low-sensitivity environment or with a test account, and log session/connection activity for auditability.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "browser-tool-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/browser-tool-automation/SKILL.md
2. Save it as ~/.claude/skills/browser-tool-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Browser Tool Automation via Rube MCP

Automate Browser Tool operations through Composio's Browser Tool toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/browser_tool

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Browser Tool connection via RUBE_MANAGE_CONNECTIONS with toolkit browser_tool
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit browser_tool
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Browser Tool operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Browser Tool task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["browser_tool"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Browser Tool-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `browser_tool`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Hyperbrowser workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_