googlesuper-automation

通过 Rube MCP 自动执行 Google Super 相关任务与跨工具流程。

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "googlesuper-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/googlesuper-automation/SKILL.md
2. 保存为 ~/.claude/skills/googlesuper-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

自动化 Google 工作流

输入

先搜索可用工具及最新 schema，然后帮我用 Rube MCP 自动化一个 Google 工作流：从 Gmail 获取带有“发票”标签的邮件附件，保存到 Google Drive 的“财务/发票”文件夹，并把文件链接整理到 Google Sheets 表格中。

预期产出

返回基于当前工具 schema 的自动化步骤、所需参数和可执行流程说明。

批量同步日历与表格

输入

先搜索工具定义和最新 schema，再创建一个自动化流程：每天读取我 Google Calendar 明天的会议，提取时间、主题和参会人，追加到 Google Sheets 的“明日会议”工作表。

预期产出

输出适用于当前接口的自动化配置方案，以及字段映射与触发逻辑。

邮件触发文档创建

输入

先搜索当前可用工具和 schema，然后设计一个流程：当 Gmail 收到主题包含“项目周报”的邮件时，自动在 Google Docs 新建周报文档，填入邮件正文，并将文档链接回发给发件人。

预期产出

给出完整的自动化流程设计，包括触发条件、文档创建参数和回邮动作。

// 文档

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`