$ ~/registry/skill/composiohq-composio-skills-browseai-automation

SKILL

browseai-automation

Name: browseai-automation
Author: Composio

Automate BrowseAI workflows to extract web data and monitor page changes.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

Overall this is a browser-automation skill built on Rube MCP. The material shows no required secrets or suspicious endpoints, and it is open-source with strong community adoption; the main consideration is normal MCP-style remote tool execution via Rube/Composio, so the overall level is caution.

CredentialsLow risk

No API keys, tokens, or other secrets are declared; the material explicitly says “No API keys needed.” No credential leakage or abuse red flags are evident.

Network egressCaution

No remote endpoint is listed beyond Rube MCP, but it does require connecting to `https://rube.app/mcp` and executing tools through Composio/Rube, which entails normal egress of task data to that declared service.

Code executionCaution

This is a prompt/tool-orchestration skill and does not show arbitrary local code execution; however, it does invoke MCP tools for automation, which is a normal controlled execution capability.

Data accessCaution

Its data access depends on the connected Browseai account and tool permissions, potentially reading or operating on browser-related data or workflow content; the material does not indicate access beyond that scope.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.7k stars), which supports auditability and trust; although the license and maintenance status are not stated, no clear supply-chain red flags are visible.

Recommendations

Connect to Rube MCP only when needed and prefer least-privilege accounts.
Review the exact tools and parameters returned by RUBE_SEARCH_TOOLS before execution; do not blindly trust the README examples.
If sensitive browser data is involved, verify Composio/Rube data retention and access policies first.

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 "browseai-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/browseai-automation/SKILL.md
2. Save it as ~/.claude/skills/browseai-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Browseai Automation via Rube MCP

Automate Browseai operations through Composio's Browseai toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/browseai

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Browseai connection via RUBE_MANAGE_CONNECTIONS with toolkit browseai
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 browseai
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: "Browseai 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 Browseai task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["browseai"]
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 Browseai-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `browseai`
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 Scrapegraph AI tasks via Rube MCP with schema-first tool discovery.

ComposioGet→

$ loading_