Automate Browserhub browser tasks via Rube MCP using current tool schemas.
This skill appears to be an open-source prompt-style instruction asset with no declared local code execution, file access, or direct API key requirement, so its inherent risk is relatively low. However, it is designed to drive remote interactions with Rube MCP/Composio and Browserhub tools, so actual use involves network egress and third-party connections that should be verified.
The material states 'No API keys needed,' but it also requires an ACTIVE Browserhub connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link. This suggests credentials may be handled through an external OAuth/connection flow rather than not existing at all. No explicit credential theft or misuse is stated, but the real authorization scope should be verified during connection.
The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing tools through Composio/Browserhub; user queries, session IDs, arguments, and potentially business data would be sent to declared third-party services. The endpoint is specified rather than unknown, but this is still a standard third-party network egress scenario.
Based on the provided material, this is a prompt-only operational guide with no executable scripts, install commands, or instructions to spawn local processes. Its core function is to guide calls to external MCP tools rather than execute code locally.
The skill text itself does not declare direct local file read/write access, but it guides users to submit task parameters, session data, and potentially Browserhub operation data to remote tools. The actual accessible data scope depends on the Browserhub tool schemas and the granted connection scope. No clearly excessive local data access is stated in the material.
The source is a GitHub open-source repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk. What is shown here is auditable README/prompt content rather than a closed-source binary. Still, the repository license is not declared and maintenance status is unknown, so upstream changes should be monitored.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "browserhub-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/browserhub-automation/SKILL.md 2. Save it as ~/.claude/skills/browserhub-automation/SKILL.md 3. Reload skills and tell me it's ready
Automate Browserhub operations through Composio's Browserhub toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/browserhub
RUBE_MANAGE_CONNECTIONS with toolkit browserhubRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit browserhubAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Browserhub operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Browserhub task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["browserhub"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Browserhub-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit browserhub |
| 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 Diffbot tasks via Rube MCP using current tool schemas.
Automate DigiCert certificate tasks via Rube MCP with schema-first tool discovery.
Automate Discord bot tasks and workflow actions through Rube MCP.
Automate DNSFilter administration and security operations through Rube MCP.
Automate Dock certificate tasks through Rube MCP for faster security operations.
Automate Front inbox conversations, contacts, and team workflows via Rube MCP.
Automate Browserbase tasks via Rube MCP and check latest tool schemas first.
Automate browser tool tasks via Rube MCP with schema lookup first.
Automate Hyperbrowser workflows via Rube MCP using current tool schemas first.
Automate Anchor Browser actions and web workflows through Rube MCP.
Automate browser tasks, web flows, and scraping with Browserless tooling.
Automate Parsehub tasks through Rube MCP for faster web data extraction.