Do I need to hardcode tool slugs?

No. Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas before executing any workflow.

What if the Gatherup connection is not ACTIVE?

Check the auth flow from RUBE_MANAGE_CONNECTIONS, complete any required steps, and verify ACTIVE before running tools.

How should I handle sessions?

Reuse session IDs within a single workflow for continuity; generate a new session_id for new workflows and pass it to execution calls.

gatherup-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Gatherup Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/gatherup

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["gatherup"]
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 Gatherup-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `gatherup`
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/gatherup-automation/SKILL.mdView on GitHub

Overview

Automate Gatherup operations through Composio's Gatherup toolkit using Rube MCP. It emphasizes always discovering tool schemas with RUBE_SEARCH_TOOLS before execution and ensuring an active Gatherup connection via RUBE_MANAGE_CONNECTIONS. This tight integration speeds workflows while keeping schemas up to date.

How This Skill Works

You connect an MCP server (rube), verify availability with RUBE_SEARCH_TOOLS, and establish a Gatherup connection with RUBE_MANAGE_CONNECTIONS. The core workflow then discovers available tools for Gatherup, confirms the connection is ACTIVE, and executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including the required memory and session_id. Tool schemas are refreshed on every discovery to prevent hardcoding.

When to Use It

You need to automate recurring Gatherup tasks without hardcoding tool slugs or arguments.
You must verify current tool schemas before running any Gatherup operations.
You perform a multi-step Gatherup workflow and want to reuse a session ID within the workflow.
You need to bulk run Gatherup operations via RUBE_MULTI_EXECUTE_TOOL or related bulk pathways.
You troubleshoot connectivity by confirming ACTIVE status before execution and re-establishing the connection if needed.

Quick Start

Step 1: Configure MCP: add https://rube.app/mcp as an MCP server and run RUBE_SEARCH_TOOLS to confirm available tools.
Step 2: Connect: run RUBE_MANAGE_CONNECTIONS with toolkits: ["gatherup"] and ensure the session shows ACTIVE.
Step 3: Run: discover a tool slug with RUBE_SEARCH_TOOLS, then execute it via RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new ones only for new workflows.

Example Use Cases

Automatically generate a weekly Gatherup status report by discovering the appropriate tool and executing it using a saved session.
Sync the status of tasks across multiple Gatherup projects by first discovering the update_task_status tool and then executing it with current schemas.
Bulk close completed Gatherup tasks with a discovered bulk_close_tasks tool, ensuring memory and session continuity.
Audit or validate Gatherup tasks by discovering an audit_tasks tool and running it with up-to-date schemas.
Recover a failed workflow after a network interruption by re-discovering tools and re-establishing an ACTIVE RUBE_MANAGE_CONNECTIONS session.

Frequently Asked Questions

Add this skill to your agents