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

SKILL

anchor-browser-automation

Name: anchor-browser-automation
Author: Composio

Automate Anchor Browser actions and web workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily a usage guide/prompt wrapper for Rube MCP/Composio rather than standalone executable code. It does not declare its own API keys or local code execution, but it explicitly depends on a remote MCP endpoint and runtime-discovered external tools, so the overall posture is caution rather than high risk.

CredentialsCaution

The material says 'No API keys needed' but also requires establishing an ACTIVE `anchor_browser` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link. This suggests the skill itself does not ask for static secrets, yet it may trigger external account authorization flows; the scope of those tokens is not disclosed here.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and using Composio/Rube to discover and execute tools. User task descriptions, session IDs, tool arguments, and possibly browser-operation data may be sent to that declared remote endpoint. The egress target is identified rather than unknown, but normal remote data transmission is involved.

Code executionLow risk

Based on the provided material, this is a prompt-only skill with no installation script, executable payload, or requirement to spawn local processes; it mainly instructs the user to call existing MCP tools. The material does not show this skill itself having local code-execution privileges.

Data accessCaution

The skill aims to 'Automate Anchor Browser operations' and can invoke runtime-discovered browser-related tools via `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`. The README does not specify exactly which local files or browser data are accessed, but browser automation may naturally interact with page content, session state, or connected account data; the material lacks clear least-privilege or data-scope details.

Supply chainLow risk

The source is a GitHub open-source repository, and the system marks it as prompt-only, open-source, with strong community trust (64.7k). These are strong risk-reducing signals. Although the license is undeclared, maintenance status is unknown, and the README depends on external Composio/Rube services, the skill text itself is reasonably auditable and shows no obvious malicious or prompt-injection red flags.

Recommendations

Only connect `https://rube.app/mcp` in a trusted environment, and verify its privacy policy, data handling, and operator identity.
Before completing `anchor_browser` authorization, review the exact permission scope requested and avoid granting unnecessary account access.
Inspect the runtime-discovered tool schemas before execution and allow only the minimum operations required for the task.
Do not input highly sensitive information into this workflow; for sensitive pages, prefer isolated accounts or test data.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Anchor Browser Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/anchor_browser

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["anchor_browser"]
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 Anchor Browser-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `anchor_browser`
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 browser tasks, web flows, and scraping with Browserless tooling.

ComposioGet→

$ loading_