What is googlesuper-automation?

A workflow pattern to automate Google Super operations using Composio's Rube MCP (Requires RUBE_SEARCH_TOOLS and an ACTIVE googlesuper connection).

What prerequisites are required?

Rube MCP must be connected, RUBE_SEARCH_TOOLS available, and an ACTIVE Google Super connection via RUBE_MANAGE_CONNECTIONS with the toolkit googlesuper.

How do I discover tools and run them?

Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas, then use RUBE_MULTI_EXECUTE_TOOL with the discovered slug and proper memory and session_id.

googlesuper-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/googlesuper-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Google Super Automation via Rube MCP

Automate Google Super operations through Composio's Google Super toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/googlesuper

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["googlesuper"]
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 Google Super-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `googlesuper`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/googlesuper-automation/SKILL.md

View on GitHub

Overview

This skill automates Google Super operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS and requires an active googlesuper connection via RUBE_MANAGE_CONNECTIONS before executing workflows.

How This Skill Works

You connect Rube MCP and always fetch tool schemas first. Then you manage the googlesuper connection to ensure ACTIVE status, and finally execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and the required memory parameter.

When to Use It

On-boarding a new Google Super workflow where tool schemas may change and require fresh discovery
Integrating Google Super tasks into an automated pipeline with session continuity
Validating tool slugs and arguments before running a Google Super operation
Ensuring an ACTIVE Google Super connection before executing tools in a workflow
Processing multiple Google Super operations in sequence, handling pagination and dynamic tool lists

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit googlesuper and confirm ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover a tool slug, then run RUBE_MULTI_EXECUTE_TOOL with that slug and memory, including your session_id

Best Practices

Always search first to fetch current tool schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the tool schemas; avoid hardcoding
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow and refresh only for new workflows

Example Use Cases

Auto-run a Google Super operation by discovering the tool slug via RUBE_SEARCH_TOOLS and executing it with RUBE_MULTI_EXECUTE_TOOL
Set up a daily Google Super workflow that first ensures the googlesuper connection is ACTIVE, then runs a sequence of discovered tools in a single session
Validate a new Google Super task by inspecting its schema after a RUBE_SEARCH_TOOLS lookup and verifying inputs before execution
Handle a paginated response from RUBE_SEARCH_TOOLS to collect all available Google Super tools for a complex workflow
Resume a long-running Google Super operation by reusing a session_id and rechecking ACTIVE status before continuation

Frequently Asked Questions

Add this skill to your agents